Continue to Site

Welcome to MCAD Central

Join our MCAD Central community forums, the largest resource for MCAD (Mechanical Computer-Aided Design) professionals, including files, forums, jobs, articles, calendar, and more.

When WIldfire saves files

soboyle

New member
We are a small office that is not using intralink (yet), our projects are small enough that in the past we usually have just 1-2 people working on each project, so that file overwrites were rare. Since upgrading to Wildfire 2 we have been experiencing more file overwrites, and it seems that pro now saves files even if you havent changed them. For example open a assembly, change a curve in the top level assembly, save, and a number of part and assemblyfiles get saved that were not affected by the curve in any way. This has been causing us problems when working with 2 people on a project, for no apparent reason the other person is overwriting changes. Any idea what I going on here? any fixes, is there a config.pro option that we need to change? Or is this PTC's subtle way of vacuuming up ushold outs.
 
Make sure that the settings are correct when Pro/E is running. It is possible they are getting changed by another config.pro file. Start Pro/E up and go to tools/options and change the "Showing" tab to current session. It will also show you which file made the last setting. You could put them in config.sup so thye cannot be overwritten.

Also, make sure your users are not using the file/backup command! That will always write every dependant object to disk.
Edited by: dr_gallup
 
Thanks


Those config settings are correct in the current session.No backups are being made. I'm fairly familiar with typical problems that might occur, have been using pro since release 12! Wasnt sure if PTC had made some new config options that I wasnt aware of.


It used to be that 2 people could work on the same assembly without fear of overwriting each other as long as they didnt work on the same part or sub-assembly, now that seems to be out the window.
 
Try this:

CREATE_DRAWING_DIMS_ONLY YES

If you are creating dimensions in drawings without this setting, they get saved with the model and therefore the model gets saved when the drawing is saved.

If your users are changing layer settings and saving the layer status, that will also flag components as changed for saving.

WF2 should work same as previous releases as far as saving.
Edited by: dr_gallup
 
That is a handy config option, but doesnt apply in this case, since we were not detailing at the time of our problems.
 
dr_gallup was on the right config options but I've been having the same problem as soboyle. I ran a test scenario and found that the config option


save_modified_draw_models_only should be NO instead of YES.


In my test I had a simple assembly with 2 parts.I opened the assembly on my computer and edited one part's placement. On my buddy's computer I had him change a dimension in the part. We both saved our changes, mine being on the assembly and his being on the part. With the above option set to YES on my machine, my session overwrote my buddy's changes. With the option set to NO, both our changes were preserved and the test assembly opened with my part placement correct and my buddy's part-level change correct. This means that when a change is made, you must explicitly save the changed part or assembly in order for your changes to be saved but initial testing shows that you won't unintentionally overwrite someone else's work this way.
 

Sponsor

Back
Top