How does creo view files proces effectivity

[JH_13978772]

Hello.

I'm new to the software so i'm having a hard time finding this answer.

Having some issues with generating creo view files. Actualy wondering how it is processed. 

1- model generated in 2015, generates relatively small file(s) 50mb

2- same model now in 2025 generated with a lott of files/size 700mb

Does the generator first process all changes from 2015 till 2025, then work backwards towards effectivity date? any documentation how this is processed.  And are there methods of limmiting prpcessing time and files?

Thanks,

john. 

[avillanueva]

Publishing is based on the configuration chosen and the wvs settings at the time. For example, you can choose to publish latest vs as stored. This can obviously be different and result in different sizes. Even if you publish as-stored, if iterations have been purged, that as-stored base line cannot be honored. Next would be the WVS settings. Are you publishing as a position assembly or all models under a single PVZ of all components. Then there is the publishing adapter version and the level of detail settings in the recipe file. You would think that over time, file size would get smaller and more compact but that is not a guarantee. 

In your example, if its a single model, its likely the recipe file and adapter version that are different. You might be publishing annotations, layers, and features.

[JH_13978772]

Thanks for the reply.

> As stored, this would be a baseline/snapshot version at the given time 2015, a separate file/version

this would be different from both the 2015 and 2025 version, since its based on a fixed time/date.

>purged items, yes. What's purged can't be added. 

>publishing adapter version and the level of detail settings 

Yes, high likelihood since its been 10 years. And with new versions most likely new settings/config. 

> File size

I was expecting a larger file due to recorded changes, revisions etc 🙂 

Any documentation on that i can read, processing with a effectivity date? Still looking myself.

maybe a better question would be:

Would a publish with the same settings etc but run with effectivity date result in a different file size/longer load time?

This due to the processing steps, first running to current date , then ''removing'' the effectivity date changes backwards. 

[avillanueva]

In your case, did you see a difference with a single part model or was it an assembly?

[JH_13978772]

assembly

[avillanueva]

Ok, that could open up lots of differences. When assemblies are published, the settings tell it whether to publish all components are part of the assembly each time and store that with the representation. The amount of data can get large and lots of files. As a result, the total size of all the stuff can vary as we discussed above over time. Those change to the size of an individual files get compounded. There are settings to have it store as a single PVZ which zips up and compresssed the resulting data. 1 file get stored but when you ask to view the represenation, you have to retreive a large zip and uncompress. Creo view is meant to allow openning very large assemblies but stream data in as necessary. Trade offs there. 

Your original post said it went from 50 to 700 MB which is quite a difference. Can you see if there was a lot of detail added in the structure below that is now getting published that was not years ago? For example, we used to create simplified version of circuit cards at one point. Blank boards or boxey models for components. Now we have very detailed component models. If I published that assembly with the cards today, they would be a lot bigger.

[JH_13978772 · Accepted solution]

Thanks for the feedback, I think I get the picture.