Community Tip - Learn all about the Community Ranking System, a fun gamification element of the PTC Community. X
I'm in the middle of creating new start part/assy and revamping our config.pro. I'm currently running into a problem with the def_layer config option.
The new start part/assy have rules based layers established in them. Everything is working great in that regard.
The old config.pro had a bunch of def_layer lines in it.
The new config.pro has all the def_layer lines removed.
When a new part or assembly is created using the new start part with the new config loaded from <loadpoint>\text, the old layers created via the now removed def_layer config options pop into existence when the appropriate feature is created. Create a datum point, and the point appears on the proper layer due to the rules established in the new start part, plus it appears on the old layer for points defined in the now defunct config.pro.
I've double and triple checked for the old config.pro lurking somewhere causing this issue and I can't find it anywhere. Obviously I'm missing something. Or ProE has some ghost in the machine capable of remembering old configs even when they're no longer explicitly used.
Any clues?
Through a combination of Chris's answer and a private email... problem solved.
The .bat file I'm using to launch ProE is currently stored on a network drive. In that location is an old version of the config.pro. When I created the shortcut onto my desktop from that .bat, it set the 'start in' to that location. I had checked all over on my local drives (where ProE is loaded), rather than branching out to the network.
Thanks!