Hello, when trying to generate a 3D PDF of a bridge beam I get the error shown in the subject line and the PDF file is blank. Is there a limit on how many elements that can be included in a 3D PDF? Here is an image of what I'm trying to produce....
You can upload the file here by selecting ' Reply ' and then select the 'Advanced Reply Editor '
Select the tool shown above, and upload the file from your computer
Carl, here is the CAD file with the geometry.
Labyrinth Technology | dev.notes() | cad.point
pdf.pltcfgLike Jan, I too was unable to reproduce using both MicroStation 08.11.09.357 and 08.11.09.459
I attach the pdfplt.cfg file delivered with my *.357 build which I had running on win 7 PLATFORM for you to test / compare against.
KKnepper said:but Microstation still crashed each time while generating the plot.
It's weird. I am surprised because of the error message you mentioned (Engineering contents of active model could not be loaded.), there are only normal graphic elements in the design file, so I am not sure where the message comes from. I think the reasons can be:
KKnepper said:My computer only has 4GB of ram, could that be an issue?
In my opinion not. Mine has 6 GB and it's not so big difference. Moreover MicroStation is 32bit application, so it doesn't utilize all memory anyway.
KKnepper said:Our Microstation is a custom install with a lot of the components residing on the server.
This is very important information, not discussed yet during this lengthy discussion. And it was reason why I recommend to test to create PDF in untitled / untitled workspace to minimize threat the prinitng process is influenced by any not MicroStation code. By default in untitled / untitled workspace nothing is loaded, but if it's the custom installation, anything can be installed at site or higher level.
KKnepper said:My guess is that this is where the issue is, especially if you guys can plot it without issue.
Yes, you are probably right. If there is any custom code adding data on the fly or hooking plotting process, it's hard to investigate where the problem can be :-(