Lately, the projects I have been printing to pdf are very slow. They are slow to open, slow to scan through pages and basically do anything. Its not so bad on smaller projects (<50 pages), but on larger projects, performance seems to be suffering badly.
I am guessing this is more of an Adobe issue that an FDOT/Microstation issue, but since many of us here deal with printing our projects to pdf, I thought I would ask.
Has anyone else been experiencing this? Anyone found a solution?
Do you have a large cross section file?
Its about 25 sheets worth, nothing too crazy. Ive had much larger XS files and no problems. Seems to be a more recent issue. I have had projects with 100+ pages of XS sheets in the past and never had any problems quickly flipping through the pages. Some of my more recent pdfs have been just horribly slow.
I even have a project with no cross sections (we are just doing signing, signals and its) that is only 40 pages and flipping through that is noticeably slow.
These two project pdfs have been created recently, after the SS2 update, using print organizer. Not really sure what to do about it.
Thanks
Zachary Billings, P.E.
Senior Roadway Engineer (Licensed in FL and MI)
CONSOR Engineers, LLC
System Info:
Windows 11 | Intel Core i7-13700k | Nvidia RTX 3080 FTW3 Ultra | 32 GB of RAM | 2 TB Western Digital Black SN850x NVME
ORD Version 10.12.02.004 | FDOT Connect Version 10.12.01.00
YouTube Page for ORD: https://tinyurl.com/BillingsCADD
Downloading now, Ill give it a try here in a sec and let you know
That looks to have done it. The new pdf I just created is responding normally again. Ill send it around to everyone at my office.
Thanks for your help Jimmie.
You can just replace the the one in the \FDOTSS2\resource\plot directory on the server.
Jimmie, what are the specific enhancements that are turned off?
I also noticed that the new FDOTPDF driver has a bunch of lines of code that did not exist in the previous version...
<DefaultDesignScriptFileName xmlns:xsi="www.w3.org/.../XMLSchema-instance" xsi:nil="true" />
<PrintStyleName xmlns:xsi="www.w3.org/.../XMLSchema-instance" xsi:nil="true" />
<PDFPrecision xmlns:xsi="www.w3.org/.../XMLSchema-instance" xsi:nil="true" />
<PDFBookMarkHierarchy xmlns:xsi="www.w3.org/.../XMLSchema-instance" xsi:nil="true" />
<PDFEnableOptionalContent xmlns:xsi="www.w3.org/.../XMLSchema-instance" xsi:nil="true" />
<PDFPrintOptionalContent xmlns:xsi="www.w3.org/.../XMLSchema-instance" xsi:nil="true" />
<PDFEnableMeasuring xmlns:xsi="www.w3.org/.../XMLSchema-instance" xsi:nil="true" />
<PDFEnableGeoreferencing xmlns:xsi="www.w3.org/.../XMLSchema-instance" xsi:nil="true" />
<PDFLevelLabel xmlns:xsi="www.w3.org/.../XMLSchema-instance" xsi:nil="true" />
<PDFAllowChanges xmlns:xsi="www.w3.org/.../XMLSchema-instance" xsi:nil="true" />
<PDFAllowPrinting xmlns:xsi="www.w3.org/.../XMLSchema-instance" xsi:nil="true" />
<PDFPageMode xmlns:xsi="www.w3.org/.../XMLSchema-instance" xsi:nil="true" />
<PDFEnablePlotTo3D xmlns:xsi="www.w3.org/.../XMLSchema-instance" xsi:nil="true" />
<PDFEnableProvenance xmlns:xsi="www.w3.org/.../XMLSchema-instance" xsi:nil="true" />
<PDFSetPageFromPlotSize xmlns:xsi="www.w3.org/.../XMLSchema-instance" xsi:nil="true" />
<PDFDocTitle xmlns:xsi="www.w3.org/.../XMLSchema-instance" xsi:nil="true" />
<PDFAuthor xmlns:xsi="www.w3.org/.../XMLSchema-instance" xsi:nil="true" />
<PDFOwnerPassword xmlns:xsi="www.w3.org/.../XMLSchema-instance" xsi:nil="true" />
<PDFUserPassword xmlns:xsi="www.w3.org/.../XMLSchema-instance" xsi:nil="true" />
<DefaultPrintFileName xmlns:xsi="www.w3.org/.../XMLSchema-instance" xsi:nil="true" />
<BorderComment xmlns:xsi="www.w3.org/.../XMLSchema-instance" xsi:nil="true" />
<RasterizedParametersQuality xmlns:xsi="www.w3.org/.../XMLSchema-instance" xsi:nil="true" />
<MergeBackgroundRasters xmlns:xsi="www.w3.org/.../XMLSchema-instance" xsi:nil="true" />
Is this part of the problem?
Also, will the new FDOTPDF file be released as part of the upcoming MR?
Thanks!
CJ Youmans, PE
Transportation Engineer
RS&H
You can turn off the optional content similar to the way it was set in FDOT2010.The screen shot below shows an example of the way it will be set when FDOTSS2 MR1 is released.