Community Tip - You can Bookmark boards, posts or articles that you'd like to access again easily! X
Hi,
I am having problems with a reasonably complex flexible model (cable trunking with patterns and variable length - relations running pattern length). I can get the model to a stage where it is stable and use it throughout designs but this causes a 10 min regen of every trunking component (120000+ features of a mediun sized model) upon model opening or regen. Is it possible to prevent this regen or somehow lock out these flex models once they are in place.
Thanks
Dave
Not knowing the particulars of your environment and process, here are some general strategies that may help.
Once the flexible model is configured as you wish to use it in a design you are working on you should be able to set the features to "Read Only" so they are not regenerated. I have not done this with flexible models but have employed it to "lock" for lack of a better term 100s of parts in an assembly that I know are not going to change in the design cycle. Just be thoughtful about saving the models with "Read Only" features as it can cause confusion if retrieved in the future.
If the flexible model can be used to "spin off" derivative models that are design configuration specific then it can be more straight forward to save the unique derivative models as read only. You would have a master flexible model that you use to configure design specific derivative versions that you can save with the features set to "Read Only". You can always clear the "Read Only" setting if you need to regenerate the derivative based on a change to the master model.
Hi Thomas,
Thanks for the quick reply. I tried setting the entire workspace to Read only and option "regen_read_only_insts" to No. But I am still forced to sit through a regen of various parts - the flexible trunking taking up the most time. I have stripped the trunking model back to a basic box to minimise the regen but it is still time consuming.
Any further thoughts would be great.
edit : also true when regenerate_read_only_objects no, did see some improvement though - still looking at 8000 feature regens)
Sounds like you are working inside a Windchill environment. I am not an expert on Windchill handling of Creo data structures but I have seen/heard of unexpected results inside Wchill with regen and saving of family tables, flexible models, etc. It is possible that it is Wchill forcing the regens. If so you will probably have to conifgure Wchill to deal with this problem if it is even possible to manage in Wchill.
Can you try using read only approach outside of Wchill? I am not normally working in Wchill environment so my experience is based on running Pro or Creo outside of Wchill.
I understand you are setting the entire workspace to read only but I am not familiar with that functionality in Wchill. I would look to the documentation to understand what it means to set a Workspace to read only, maybe not what you would think or has caveats for flexible models, family tables and the like.
If you can explore the references of the long regen model(s) using the ref viewer then that may provide some insight into which models you need to set to regen only although I think you already know this from your comments.
Yes, I am running a Windchill setup and the lock / read only options are the same thing. I've run a few trials and am still seeing this happen on a standalone (no Windchill) session. It looks to be how Creo handles flexible models. I have simplified the model and have set read only models not to regen (but the flex models still do), this has inproved things but I would prefer to use the more complex flexible model if anyone knows of a better method or a setting I am missing?
Another option may be to save the flexible model you want to reference during the design as a Creo neutral format and then open that neutral file in Creo and it should be a single feature in the model tree (other than your start template features), you should be able to set that to read only and Creo/Wchill will likely not force the regen with this approach. It is obviously not driven by your flexible design data model but if you just need to avoid the unnecessary regens while you are working it is worth a try.