Community Tip - Did you get called away in the middle of writing a post? Don't worry you can find your unfinished post later in the Drafts section of your profile page. X
We are facing a issue of hanging or low performance of computer during creating or saving a new file. We have made a system that all Creo users will use single Config.pro file which is kept on server. It is accessible to all users but can't modify it to prevent changing of Configuration settings. It can be modify by Administrator only. All CAD users are instructed, not to create multiple copies of a part in different folders to avoid mistakes (like updated model or drawing). If Users need to add search path for Assy. model to retrieve different folders child parts they request to Administrator to add search path in Config.pro file, Administrator adds it in Config.pro file. But after adding so many search path in Config.pro file Computers started hanging or low performance during creating or saving new files. When we try to find the solution from PTC technical support, they asked to reduce search paths from Config.pro file. They explain that when we create or save a new file, at that time Creo searches for duplicacy of model or part name in all folders those are specified in config.pro file.
So as per my suggestion, To retrieve a part or assembly in Creo Assembly, Search paths should not be added in Config.pro file & there should be different option to add search paths which should be separate from Creo settings file (Config.pro, drawing.dtl, etc.) which will solve below purposes:
1. All users in one organization may use same setting files (like Config.pro or Drawing.dtl file, symbols etc.) those are kept at safe location to standardize the drafting settings.
2. Design Engineers will not need to request to Administrator to add search path in Config.pro File.
3. Computer performance will not be affected during creating or saving new files due to search paths in config.pro.
We can also take example of MS Excel where we use hyperlinks those are separate from other settings. So Creo should also have a option to link parts with assembly without adding search path in Config.pro file.
It is possible today to have a shared company config.pro (and/or config.sup) as well as a local config.pro. Put the user's specific search paths in each user's local config.pro.
If you hardcode in the path's of the sub-components, that makes any changes to your network structure impossible. We all know that IT structure needs to be constantly improved.
I think you need to improve your processes internally to improve the performance issue caused by too many search paths. Project specific search paths would be a good start.
If we use local config.pro, there is a chance of changing configuration settings by user, those may be not match with organization's standard.
True, but ANY (non-gui) change or customization is going to require a local config.pro anyway. I can't imagine not letting users choose how they want the interface to look/act (datum display, system colors, etc.) as well as be able to build personal mapkeys.
Any user can create a config.pro file and load it after the session is started. All options not placed in a config.sup are changeable in each session individually and with a custom config file. If you really want to lock down every configuration option, you MUST have every option explicitly listed in your config.sup.
If you really want to lock down every configuration option, you MUST have every option explicitly listed in your config.sup.
...which of course is not possible for mapkeys (since the config.sup doesn't allow command duplication).
You can take your search_paths out of the config.pro and put them in search.pro file with a config.pro option pointing to that file.
Do not restrict your users from creating their own local config.pro. The local one is very beneficial for customization and user preference settings.
It's awesome that way. You can't turn the datum display on or off either, it's whatever is preset in the config.sup. Makes for a great joke, when you don't have other things to do.
We have save drawing.dtl & other files related to drawing setting on server & these are locked but we have kept config.pro in local machine. In config.pro, we have added search_path for search.pro (in which user can add search_paths). But if there are lot parts & search paths (due to wide range of products) in config.pro or search.pro file, Creo searching time increases which may hang Creo also. So As per my opinion, there should be a Link alongwith part or model location in Creo Assembly for model retrieval to avoid hanging of Creo or reducing creating and saving time for new file.