All the evidence so far points to Revit generating very complex and copious calls to the PostScript driver.
Adobe pdf printer driver free pdf#
I don't know who “Don” is, but on behalf of Adobe, I certainly feel your frustration and yes, it certainly is a “most stupid of issues.”īut if you read through this thread, you will notice that this performance issue occurs even when simply printing to a real printer, not just to the Adobe PDF printer driver instance that happens to use the same, base Microsoft PostScript driver. I would appreciate any suggestions to solve this problem! May this suggest that a memory limit in the printjob handeling is set too small? If you want to make sure the PDF is created, avoid several complex views in the same sheet, and print sheets to PDF separate, one at a time. To avoid the 100% chance of problems, remove ambient shadows before printing. I have found that the graphic display menu in Revit might cause part of this problem: When "ambient shadows" are added to a hidden line view, the print process bar will always stop just in the beginning, and no information is available to solve the problem, or even to follow the process, has it stopped or is it just slow? This is simply not good enough, not even form a freeware program standard, at least a time out warning or failure popup should show? Worldwide leading companies, each in their field, too big to actually care? It is rather frustrating that nobody at Adobe or Autodesk seems to have taken proper action to fix this issue. When I try to print several sheets combined in one PDF file, just as I normally send a print job to a Xerox, it would often stop in the process without notice. Problems when creating PDF from the printmenu in Revit. Thanks for addressing a problem that has been known to be common among architects and others creating PDF from Revit If you can try this, let us know the results!!! If the creation still takes a very long time, or hangs, or otherwise fails, the problem has nothing whatsoever to do with Adobe Acrobat. This will cause the driver to simply produce PostScript and not go onto the Acrobat Distiller conversion of PostScript to PDF. PS: One thing you can do to help troubleshoot the problem is to try changing the Adobe PDF PostScript printer driver to temporarily point to port FILE: instead of port Adobe PDF. Maybe you and other Revit customers can convince Autodesk to reach out to us? This is not just “a critical issue for Adobe” but rather, a critical issue for Autodesk that we would like to assist our mutual customers overcome. Again the problem could be in Revit in terms of how it interacts with the print driver, Microsoft in terms of how the PostScript driver is converting the print stream from Revit to PostScript, or less likely, some internal limitation or problem within Distiller.
Adobe pdf printer driver free software#
We would need Autodesk's active assistance in terms of providing software and sample problematic files for anyone at Adobe to be able to even begin helping Autodesk to resolve the issue. (5) We have no idea where the issue is since as far as I know, Autodesk has not reached out to Adobe to assist in troubleshooting the issue. (4) Autocad itself acknowledges that the problem occurs with at least one other third party PDF driver / creator. In the description of the problem Autodesk's article specifically points to model complexity as a major factor in the symptoms occurring or being alleviated. For complex models, the output is just that much more in size and complexity. (3) CAD software typically produces very verbose output, exceptional numbers of line segments and itsy-bitsy filled polygons which in turn produces even more complex PostScript and PDF, even for simple models. It is in either the creation of the PostScript or in the Distiller. (2) Revit creates PDF with Acrobat via printing to the Adobe PDF PostScript printer driver instance in which content provided by Revit is converted to PostScript with the driver itself (a Microsoft component) which is then fed into Acrobat Distiller (a component of Adobe Acrobat) which converts the PostScript to PDF. The variable here appears to be Autodesk Revit, not Adobe Acrobat. (1) Clearly the problem started with recent versions of Autodesk Revit beginning in 2016 and continuing on through at least the current 2017 release. I have looked at the Autodesk article cited as well as the postings on Autodesk's forums.