Skip to main content
A
AJ_TROGLIO14-Alexandrite
14-Alexandrite
August 9, 2024
Solved

Generation of temp files during assembly retrieve

  • August 9, 2024
  • 1 reply
  • 1000 views

I'm working remotely today trying to retrieve a rather large assembly.  My Creo home directory is a mapped server drive sitting at HQ.  Not recommended I believe but that is our current configuration.

 

When I retrieve this assembly it looks like randomly named temp files are being written to my home directory, causing this retrieval to take a long time.  See circled in the attached. 

 

Knowing this setup is not the best, why are these files being written and what can be done until we can convince our IT people to put our home directories local to our laptops?

 

Creo 8.0.0.0,  Windchill 12.

 

Thanks..

Best answer by Chris3

There is another thread about this in this community somewhere. I couldn't find it quickly. Maybe someone else remembers it.

 

Those files are temporary files that Creo creates to handle things like background family tables that you never see. For instance if you have an assembly level cut Creo makes internal family tables that you never see. If you watch your working directory during Creo operations you will see that Creo writes out lots of little text files for various things and then deletes them. These are helper files for things it needs to do.

1 reply

Chris3
Chris321-Topaz IAnswer
21-Topaz I
September 11, 2024

There is another thread about this in this community somewhere. I couldn't find it quickly. Maybe someone else remembers it.

 

Those files are temporary files that Creo creates to handle things like background family tables that you never see. For instance if you have an assembly level cut Creo makes internal family tables that you never see. If you watch your working directory during Creo operations you will see that Creo writes out lots of little text files for various things and then deletes them. These are helper files for things it needs to do.

    Terms & ConditionsCookie settingsAccessibility statement