Community Tip - You can subscribe to a forum, label or individual post and receive email notifications when someone posts a new topic or reply. Learn more! X
I have been having issues with long regeneration times when I regenerate an assembly window or try to make changes/suppress. This occurs even when all parts/subassemblies are locked, I have auto_regen_views off and enable_auto_regen off. My coworker does not have this issue when working in the same assembly.
Are both computers identical in terms of processor, memory and graphics cards?
Yes they are the exact same.
Internal
Do you used Windchill? Sometimes workspaces can get too many objects and cause issues.
Do you have multiple models/drawings open or in memory?
So many potential possibilities.
You may want to check your video card. Updates to windows sometimes causes compatibilty issues. May try updating drivers (there is some risk in updateing video drivers)
I have tried clearing my workspace and it didn’t work.
I think the main issue is that it is still regenerating locked assemblies even though I have the regenerate_read_only_objects as no. Is there something else I can do to stop it from regenerating untouched subassemblies?
Internal
For items not subject to change you can save them as set to read only. I use this approach for library components as SOP, this will ensure that they will not regenerate no matter what the environment settings are for Creo.
I have them all as locked in the top assembly- is that what you mean?
No.
If you have recently upgraded, say creo 4 to creo 7. That can be detrimental to performance. But I would expect your coworked to have similar performance.
Copy your coworkers config.pro files to your system to see if he has something different.
Clearing a workspace does not have the same result as deleting the workspace and creating a new one. I would say that's my preferred method. If you have uploaded all your work or checked in all your work, delete your .wf folder to really clean up your workspaces. WARNING, unchecked in work or work that is not uploaded to the server side will be lost, don't do this if you are not sure. It is not recoverable!
Clearing your windchill cache may also help. I have also been told in the past to delete old trail files though I have never seen that make a noticeable difference.
Locking files in workspace looks like this: