1 Reply Latest reply: Apr 3, 2012 1:31 AM by Mekiman RSS

    Distiller crash when printing from air 3.2

    Mekiman Community Member

      I have a problem with the new air runtime 3.2 when printing to pdf. For some reason when printing an movieclip through the pdf printer. It crashes.

       

      -What i've tried so far.

      Updated the air runtime // dev kit in flash builder. Changed the app xml and recompiled.

      Removed the PDFX4 2008.joboptions (Suggested in some forums)

      Tried to set the transparancy option to none (somewhere in the joboptions file).

       

      What is odd, it works perfectly with the old air runtime engine 3.1. But after updating to air 3.2 it crashes.

       

      This was the error message, it probably has something to do with text/embedded fonts (pure graphics seem to wordk). But i'm not sure. The error from the log file :

      Acrobat Distiller 9.5

      Started: maandag 2 april 2012 at 7:54:13

       

      Adobe PostScript software version: 3018.101

      CID support library initialization completed.

      Adobe PDF Settings file read error in PDFX4 2008.joboptions:

      /CheckCompliance out of range

      Acrobat Distiller 9.5

      Started: maandag 2 april 2012 at 7:57:32

       

      Adobe PostScript software version: 3018.101

      CID support library initialization completed.

      Adobe PDF Settings file read error in PDFX4 2008.joboptions:

      /CheckCompliance out of range

       

      I tried it with acrobat 8 (also worked with air 3.1)

      %%[ ProductName: Distiller ]%%

      %%[ Error: syntaxerror; OffendingCommand: --nostringval-- ]%%

      Stack:

      /GraphInit

        %%[ Flushing: rest of job (to end-of-file) will be ignored ]%%

      %%[ Warning: PostScript error. No PDF file produced. ] %%

        • 1. Re: Distiller crash when printing from air 3.2
          Mekiman Community Member

          I seem to have solved my own problem (will need some further testing but for now it is working). For some reason the display object that has to be printed needs to visible on the stage. So constructing an (sprite/movieclip with classic textfields) in memory and sending it directly as a printjob resolves into a crash. But if you attach it to the display/stage before sending the printjob, the problem seems to be resolved. Maybe this is the same reason why a printed sprite/movieclip gets corrupted after printing.