Skip to main content
J
jkopp4153-Newcomer
3-Newcomer
May 29, 2023
Question

Trail files not saving to config.pro "trail_dir" location

  • May 29, 2023
  • 2 replies
  • 2105 views

After going through the different options in config.pro, the one option that keeps giving me issues is the "trail_dir" setting. I have tried setting it to $TEMP, AppData/Local/Temp, as well as other (non-read-write protected) directories, and no matter what directory I try it always keeps saving the trail files in the current working directory. I have tried this setting in both the config.pro file in Program Files/PTC/Creo/Common Files/text as well as my user directory, and neither of those seem to work either.

 

This issue is has been a big headache for my team as we're trying to prevent our CAD directories from getting clogged up with these trail files, and it would be really nice to have them automatically created somewhere else. For reference, I'm using Creo version 9.0.0.0. Thanks!

 

2 replies

KenFarley
KenFarley21-Topaz II
21-Topaz II
May 30, 2023

The method I've used to put all those trail files in one place is as follows:

(1) I have a directory that I can write to, C:\ptc\TrailFiles.

(2) I have my config.pro located in C:\ptc.

(3) The shortcut I use to start Creo, on my desktop, has "Start in:" set to C:\ptc

(4) In my config.pro I have trail_dir set to "C:\ptc\TrailFiles"

 

The only time I get any renegade trail files is when I inadvertantly double click on a Creo-related file. In those instances a trail file is started in the directory whose file I clicked. All other trail files are stored in a big pile in the specified directory. Periodically I'll clean them out.

B
23-Emerald III
BenLoosli23-Emerald III
23-Emerald III
May 30, 2023

Mine works same as Ken's.

Only difference is my 'top' folder is c:\PTC_User\%username% instead of c:\ptc. 

M
MartinHanak24-Ruby III
24-Ruby III
May 30, 2023

Hi,

sometimes it happens that in File Explorer known file extensions are hidden. Then it is common for the configuration file to be named config.pro.txt instead of config.pro, and Creo therefore ignores it. Please check it out.

 

    Terms & ConditionsAccessibility statement