Skip to main content
Inoram14-Alexandrite
14-Alexandrite
September 23, 2013
Solved

file size wf3 vs creo2

  • September 23, 2013
  • 5 replies
  • 1934 views

Why is a part model that is about 5meg in WF3 close to 200meg in Creo2?


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.
Best answer by TomD.inPDX

Your graphics accuracy settings affects the file size. The files have embedded the shaded graphics and LOD data and with high setting in your config, it will safe a lot of facet data. You can get around this by changing the config.pro option: save_model_display wireframe

You can also reduce your graphics quality options before saving but I find the setting above to be more consistent.

5 replies

Inoram14-AlexandriteAuthor
14-Alexandrite
September 23, 2013

Sorry meant to say imported geometry file size.

Dale_Rosema
Dale_Rosema23-Emerald IV
23-Emerald IV
September 23, 2013

Could it be that default accuracies are different? Not sure - just a guess.

TomD.inPDX17-PeridotAnswer
17-Peridot
September 23, 2013

Your graphics accuracy settings affects the file size. The files have embedded the shaded graphics and LOD data and with high setting in your config, it will safe a lot of facet data. You can get around this by changing the config.pro option: save_model_display wireframe

You can also reduce your graphics quality options before saving but I find the setting above to be more consistent.

Inoram14-AlexandriteAuthor
14-Alexandrite
September 23, 2013

yup, that did it.. you're the man.

173 meg now 3 meg file. As long as it doesn't lose any actually model data, which I don't see why it would.

TomD.inPDX17-Peridot
17-Peridot
September 23, 2013

No loss of data. I suspect it is built-in JT data for some of the advanced modeling extensions for faster loads. I only learned about this when I was making glamour shots (screen-caps) with high graphics quality setting and not resetting it back to normal. File size went through the roof! With the config.pro setting as wireframe, I didn't have to worry about where I left the graphics settings during any of my saves.

Terms & ConditionsAccessibility statement