Skip to main content
E
ehill1-Visitor
1-Visitor
January 26, 2011
Question

Wildfire 4 Stable Build Survey

  • January 26, 2011
  • 1 reply
  • 586 views

We have just done an upgrade from Wildfire 2 to Wildfire 4 M170. We are seeing performance issues retrieving and saving PDFs for certain drawings. They are not very large drawings, which stinks of a bug.

I am slogging through checking performance with previous builds. If you are using WF4 and are happy with your current build, if you could let me know which one you are using that would help me focus my efforts.

Thanks in advance,

Eric Hill
Staff Engineer
ASM America
(T) 602.470.2720
(F) 602.470.0747




This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

1 reply

E
ehill1-VisitorAuthor
1-Visitor
January 27, 2011

I had only a few replies, most were from people actively using M170 with no trouble. Some had moved to M170 specifically to fix a problem with M160 and printing BOM balloons. One other had mentioned problems wtih PDF creation being slow, but didn't have a build that fixed it, just using the old ghostscript method.

PTC tech support helped me get started by figuring out it was a config.pro option that we had set that was causing the problem. I was able to narrow it down to a combination of using our drawing setup file and the enable_hlr_hashing option (set to yes). OOTB drawing setup works fine with this option set to yes. I haven't had the time or inclination to explore what part of the .dtl file is causing the problem; I just set enable_hlr_hashing to no and everything works fine.

This fixed problems with drawings crashing, taking a very long time to open, and taking a very long time to save as PDF.

Thanks for the feedback!

Terms & ConditionsAccessibility statement