I just got Creo2 installed and have most things setup, but I have a few questions.
In my config I have (datum_point_tag_display yes) and it doesn't load the tags when I start up. I tried turning them on manually and saving out the config and restarting, still doesn't work. Anyone else see this issue?
I get a std.out Allowing Crash: set_master_handler()
I get a std.err pm_is_portmapper_port_busy: bind failed, error = 10013 pm_is_portmapper_port_busy: bind failed, error = 10013
Anyone know how to resolve these?
I'm not using a config.win file, it doesn't seem to be applicable with all the changes, so I just didn't use it.
Ryan Crisp | Senior Mechanical Engineer
Priority Designs 501 Morrison Rd. Columbus, OH 43230 (614) 337-9979 www.prioritydesigns.com This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.
Config.win is obsolete, Creo uses *.ui files that are loaded only from your user profile in Windows. I still haven't figured out what to do with that company wide.
Another issue is each software mode (part, assembly, drawing, etc) has different ribbons. So, changing the model tab in assembly mode will not make a change in part mode. Someone found 26 different 'modes' in Creo. Makes UI tweaking frustrating.
I get the same errors in my install every time. They don't seem to cause any issues, but we've just recently started more heavy use of Creo so I'd too be curious of a solution.
The message in the std.out file can be suppressed, but PTC doesn't recommend it. It indicates that Creo will create a traceback.log file when it crashes. You can turn it off with the config option auto_traceback never. See CS59617
I don't get the pm_is_portmapper errors. You should contact PTC about that.
* Refresh Data <">https://www.ptc.com/appserver/cs/view/solution.jsp?n=CS49331> * Subscribe to this Document <https://www.ptc.com/appserver/cs/view/subscribe.jsp?type=solution&refre sh=yes&callnum=CS49331>
* Related to ModelCHECK - TPI 114115 <">https://www.ptc.com/appserver/cs/view/solution.jsp?n=/114115.html> * Environment variable PRO_COMM_MSG_EXE not set correctly * Multiple versions of Simlab software installed * System issue
* Example, out-of-date or incompatible OS library causing low level communications to be dropped by operating system
So first off, that message about 26 different modes isn't correct. You don't need to customize the ribbon in that many modes. Once for each of the major modes will do it. Part, Assy, Drawing, Sheet metal, & Simulate. It doesn't matter if you bring up a Part from an assembly or from the open file menu, the ribbon for part mode it the same. (All I'm doing is defining a new tab and putting our custom mapkeys in that tab.)
Secondly, what I decided to do was not place a .ui file in the loadpoint. It makes it difficult if I want to make changes to it.
My startup script copies the .ui file down to the users cache location, and the config.pro also sets load_ui_customization_run_dir to yes This allows the user to have their own customizations in the run dir, while I put the standard in their cache location.
The advantage of this is I can create a special startup script that only uses the .ui in the run dir, so that I can modify our "standard" .ui.
I added these line to my startup script:
1. del "%USERPROFILE%\pro\Creo_2_home\cache\no_pdm_cache\PTC\ProENGINEER\.Settings\creo_parametric_customization.ui"