Clearing the cache?
by Washington St. Uni. CS (#0002) · in Torque Game Engine · 02/10/2008 (4:06 pm) · 5 replies
Hi. I've recently switched my development environment from a laptop using Ubuntu Edgy to anther machine running Feisty. The game I've been working on (which works under Edgy) freezes Feisty, requiring that I switch to a virtual terminal to kill the process. The example scripts (tutorial.base and such) work just fine.
I didn't have anything substantial done yet so starting from scratch isn't a big woop. The problem I'm currently puzzled over is apparently some funky caching issues. If I set the $defaultGame in main.cs to any anything that's previously frozen then it will always freeze. To clarify, if I:
1. Call the problematic game 'foo'.
2. Set $defaultGame to 'foo'.
3. Run 'runtorque.sh' or 'torqueDemo.bin', freeze the system, and kill the process.
4. Make a copy of tutorial.base to replace 'foo'.
5. Try running again- it freezes again.
However, if I make the tutorial copy called 'bar' and run that instead then it works just fine. This issue persists so I currently have a dozen game names that'll freeze the system. Any idea where Torque is caching whatever is being problematic? Any help would be appreciated! -Damian
PS. Not to confuse the issue but whatever is freezing Feisty just started within the last couple months. Does anyone have a clue if any of the recent updates are problematic with Torque? I'm currently running Torque version 1.5.0.
I didn't have anything substantial done yet so starting from scratch isn't a big woop. The problem I'm currently puzzled over is apparently some funky caching issues. If I set the $defaultGame in main.cs to any anything that's previously frozen then it will always freeze. To clarify, if I:
1. Call the problematic game 'foo'.
2. Set $defaultGame to 'foo'.
3. Run 'runtorque.sh' or 'torqueDemo.bin', freeze the system, and kill the process.
4. Make a copy of tutorial.base to replace 'foo'.
5. Try running again- it freezes again.
However, if I make the tutorial copy called 'bar' and run that instead then it works just fine. This issue persists so I currently have a dozen game names that'll freeze the system. Any idea where Torque is caching whatever is being problematic? Any help would be appreciated! -Damian
PS. Not to confuse the issue but whatever is freezing Feisty just started within the last couple months. Does anyone have a clue if any of the recent updates are problematic with Torque? I'm currently running Torque version 1.5.0.
#2
02/25/2008 (12:29 pm)
Sweet, worked perfectly. It's a tad funky that the cache would default to an external directory but cest la vi. Thanks! -Damian
#3
Because on linux, a user usually won't have write access to the directory the game is installed in.
Gary (-;
02/25/2008 (1:45 pm)
Quote:It's a tad funky that the cache would default to an external directory but cest la vi
Because on linux, a user usually won't have write access to the directory the game is installed in.
Gary (-;
#4
02/27/2008 (12:41 pm)
If you want to avoid this issues launch torque.bin with the parameters -nohomedir 
Torque Owner Todd "zaz" Koeckeritz
One option would be to run:
This will clean up all cached compiled scripts.
Another option is to run with the -nohomedir option when you run your game. This will cause all generated scripts to be stored in the game directory, rather than under ~/.garagegames.