home.social

#preflight — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #preflight, aggregated by home.social.

  1. is a new open source slicer by oozeBot based on but with deep rework of its internal code.
    - Truely 64bit
    - GCode processing in memory
    - Athena perimeter generator improving over Arachne
    - Interlocking perimeters similar to brick layers
    - Deeper integration
    - . . .

    GitHub: github.com/oozebot/preFlight

    Feature list:
    github.com/oozebot/preFlight?t

    Feature Showcase:
    github.com/oozebot/preFlight/d

    ---

    Source via @fabbaloo : fabbaloo.com/news/oozebot-laun

  2. #preFlight is a new open source slicer by oozeBot based on #PrusaSlicer but with deep rework of its internal code.
    - Truely 64bit
    - GCode processing in memory
    - Athena perimeter generator improving over Arachne
    - Interlocking perimeters similar to brick layers
    - Deeper #RRF integration
    - . . .

    GitHub: github.com/oozebot/preFlight

    Feature list:
    github.com/oozebot/preFlight?t

    Feature Showcase:
    github.com/oozebot/preFlight/d

    ---

    Source via @fabbaloo : fabbaloo.com/news/oozebot-laun

    #3dprinting #slicer

  3. #preFlight is a new open source slicer by oozeBot based on #PrusaSlicer but with deep rework of its internal code.
    - Truely 64bit
    - GCode processing in memory
    - Athena perimeter generator improving over Arachne
    - Interlocking perimeters similar to brick layers
    - Deeper #RRF integration
    - . . .

    GitHub: github.com/oozebot/preFlight

    Feature list:
    github.com/oozebot/preFlight?t

    Feature Showcase:
    github.com/oozebot/preFlight/d

    ---

    Source via @fabbaloo : fabbaloo.com/news/oozebot-laun

    #3dprinting #slicer

  4. #preFlight is a new open source slicer by oozeBot based on #PrusaSlicer but with deep rework of its internal code.
    - Truely 64bit
    - GCode processing in memory
    - Athena perimeter generator improving over Arachne
    - Interlocking perimeters similar to brick layers
    - Deeper #RRF integration
    - . . .

    GitHub: github.com/oozebot/preFlight

    Feature list:
    github.com/oozebot/preFlight?t

    Feature Showcase:
    github.com/oozebot/preFlight/d

    ---

    Source via @fabbaloo : fabbaloo.com/news/oozebot-laun

    #3dprinting #slicer

  5. #preFlight is a new open source slicer by oozeBot based on #PrusaSlicer but with deep rework of its internal code.
    - Truely 64bit
    - GCode processing in memory
    - Athena perimeter generator improving over Arachne
    - Interlocking perimeters similar to brick layers
    - Deeper #RRF integration
    - . . .

    GitHub: github.com/oozebot/preFlight

    Feature list:
    github.com/oozebot/preFlight?t

    Feature Showcase:
    github.com/oozebot/preFlight/d

    ---

    Source via @fabbaloo : fabbaloo.com/news/oozebot-laun

    #3dprinting #slicer

  6. #JustWondering Is there a reason, other than pre-digital printing workflows, for #Adobe to put so many, often fairly centrally important, parts of #Acrobat functionality into #Preflight?

    I always find it most counterintuitive and disruptive, a kind of failed non-visual skeuomorphism. Why aren't these components just regular parts of preferences or normal menu items?

    #Disclaimer I no longer use Acrobat myself.

  7. #JustWondering Is there a reason, other than pre-digital printing workflows, for #Adobe to put so many, often fairly centrally important, parts of #Acrobat functionality into #Preflight?

    I always find it most counterintuitive and disruptive, a kind of failed non-visual skeuomorphism. Why aren't these components just regular parts of preferences or normal menu items?

    #Disclaimer I no longer use Acrobat myself.

  8. #JustWondering Is there a reason, other than pre-digital printing workflows, for #Adobe to put so many, often fairly centrally important, parts of #Acrobat functionality into #Preflight?

    I always find it most counterintuitive and disruptive, a kind of failed non-visual skeuomorphism. Why aren't these components just regular parts of preferences or normal menu items?

    #Disclaimer I no longer use Acrobat myself.

  9. #JustWondering Is there a reason, other than pre-digital printing workflows, for #Adobe to put so many, often fairly centrally important, parts of #Acrobat functionality into #Preflight?

    I always find it most counterintuitive and disruptive, a kind of failed non-visual skeuomorphism. Why aren't these components just regular parts of preferences or normal menu items?

    #Disclaimer I no longer use Acrobat myself.

  10. #JustWondering Is there a reason, other than pre-digital printing workflows, for #Adobe to put so many, often fairly centrally important, parts of #Acrobat functionality into #Preflight?

    I always find it most counterintuitive and disruptive, a kind of failed non-visual skeuomorphism. Why aren't these components just regular parts of preferences or normal menu items?

    #Disclaimer I no longer use Acrobat myself.

  11. Why-oh-why? Warum meckert mir der Preflight (#PDFXready) oft – aber nicht immer – ein angeblich unbekanntes Profil an, wenn es das wirklich nicht unbekannte "ISO Coated v2 300% (ECI)" ist. In manch anderen Dokumenten mit demselben Output Intent findet das Preflight-Profil alles dufte, in vielen aber diese Warnung. Dürfte im Endeffekt nichts ausmachen, nervt aber.

    Hat da jemand Ideen?
    #Preflight #PDF #Acrobat #InDesign

  12. Why-oh-why? Warum meckert mir der Preflight (#PDFXready) oft – aber nicht immer – ein angeblich unbekanntes Profil an, wenn es das wirklich nicht unbekannte "ISO Coated v2 300% (ECI)" ist. In manch anderen Dokumenten mit demselben Output Intent findet das Preflight-Profil alles dufte, in vielen aber diese Warnung. Dürfte im Endeffekt nichts ausmachen, nervt aber.

    Hat da jemand Ideen?
    #Preflight #PDF #Acrobat #InDesign

  13. Why-oh-why? Warum meckert mir der Preflight (#PDFXready) oft – aber nicht immer – ein angeblich unbekanntes Profil an, wenn es das wirklich nicht unbekannte "ISO Coated v2 300% (ECI)" ist. In manch anderen Dokumenten mit demselben Output Intent findet das Preflight-Profil alles dufte, in vielen aber diese Warnung. Dürfte im Endeffekt nichts ausmachen, nervt aber.

    Hat da jemand Ideen?
    #Preflight #PDF #Acrobat #InDesign

  14. Immer wieder meckert mir der #Acrobat #Preflight (PDFXready Profil) ein unbekanntes #Ausgabeprofil an. Ist aber immer dasselbe (und korrekte) "ISO Coated v2 300%" von der ECI. Mal erkennt der Preflight das an, mal nicht. Muss ich das verstehen?

  15. Immer wieder meckert mir der #Acrobat #Preflight (PDFXready Profil) ein unbekanntes #Ausgabeprofil an. Ist aber immer dasselbe (und korrekte) "ISO Coated v2 300%" von der ECI. Mal erkennt der Preflight das an, mal nicht. Muss ich das verstehen?

  16. Immer wieder meckert mir der #Acrobat #Preflight (PDFXready Profil) ein unbekanntes #Ausgabeprofil an. Ist aber immer dasselbe (und korrekte) "ISO Coated v2 300%" von der ECI. Mal erkennt der Preflight das an, mal nicht. Muss ich das verstehen?