Community Tip - Want the oppurtunity to discuss enhancements to PTC products? Join a working group! X
We recently solved an on-going performance issue w/ some remote workers that was traced to a config.sup setting (trail_dir) which was dumping trail files onto a network drive. This was a nogo suggestion from PTC dating back years.
We got to wondering if trail files are even utilized to the extent they were when hardware/software was not as mature as it is today. I've not needed to re-run a trail file in many years so I'm wondering how it would act w/ the interactions Creo has w/ Windchill these days.
Thanks.
Solved! Go to Solution.
It becomes way more difficult to make it work with Windchill. I successfully ran one maybe a year or 2 ago, but overall it might have taken more time to get it to work than it would have to just redo the work. I remember 20+ years, (yikes), running trail files 1-2 times a year, but I honestly can't say that I've run more than 1 or 2 times in the past 10 years.
It becomes way more difficult to make it work with Windchill. I successfully ran one maybe a year or 2 ago, but overall it might have taken more time to get it to work than it would have to just redo the work. I remember 20+ years, (yikes), running trail files 1-2 times a year, but I honestly can't say that I've run more than 1 or 2 times in the past 10 years.
They can still be useful. I have copied snippets out to rerun for things that mapkeys can't do. This mostly involves mouse movements and clicks.
I recently had a user write a python script that finds the last 6 commands in the trail file and adds them to a mapkey so that the most recently used commands in Creo can be re-used. Some other CAD packages have this feature.
Something you can do with the trail file capability, if you're perhaps a bit more computer savvy than most seem to be these days, is to use them to automate tedious tasks. Here's a previous discussion with some ideas:
community.ptc.com/t5/System-Administration/PTC-Creo-Distributed-Batch/td-p/596053