Thread

TS 7.51. Program termination at start

About Truespace Archives

These pages are a copy of the official truespace forums prior to their removal somewhere around 2011.

They are retained here for archive purposes only.

TS 7.51. Program termination at start // Bugs

1  |  

Post by Tiles // Sep 25, 2007, 2:03am

Tiles
Total Posts: 1037
pic
Nice one. The curse of a non existant feature. You cannot turn off autoload. And so, when you have a somehow corrupt file loaded, you are in trouble. Luckily i was able to fix this one by holding CTRL and load TS 7.51 with default settings then. Was close to reinstall it ...

Here the crash report

http://reinerstileset.4players.de/ext/tscrashreport4.zip

Post by Jack Edwards // Sep 25, 2007, 2:10am

Jack Edwards
Total Posts: 4062
pic
Holding down CTRL will let you start to default context.

Post by splinters // Sep 25, 2007, 2:18am

splinters
Total Posts: 4148
pic
Did you try deleting the Default.ctx before reinstalling?


I didn't even realise you couldn't turn autoload off...:o

Post by Tiles // Sep 25, 2007, 2:50am

Tiles
Total Posts: 1037
pic
Heh, you guys are faster with reading than i with modifying my initial posting :D


I have solved it for now by holding down CTRL and reset to default settings then. Has still loaded the odd scene, but it loaded at least without a further crash after that. So i haven't reinstalled TS 7.51 yet as i wanted it to do before i have modified my posting. But may nevertheless have to because of the other problem with the LUUV plugin, described in the other thread below ... :)

Post by brotherx // Sep 25, 2007, 11:05pm

brotherx
Total Posts: 538
pic
I've had that too on startup - I always find it to be caused by trying to do too much at once...you know, running visual studio, paint shop pro, outlook, word, excel, opera, a dozen IE instances...5 or six explorer folders open...


Always seems to work the second time round - dlls must be still in memory or something.

Post by scarroll // Feb 16, 2008, 9:17pm

scarroll
Total Posts: 19
pic
I too have had this problem. Wish I knew about holding Cntrl on previous occurances.


I suggest that for all users, once you get TS7.51 the way you like it, archive the entire folder to a ZIP or RAR file and label it backup. That way, you can just recover trueSpace by deleting the folder and unzipping it.


So far, ts7.51 hasn't created any 'hidden' (i.e. registry, registered objects outside of ts7 folder) issues that prevent a successful recovery for me.


As a long time Poser user, I've found doing this with Poser's Runtime folder is also essential.


Thats just my 2 cents!

Post by stan // Feb 17, 2008, 4:55pm

stan
Total Posts: 1240
pic
the only thing you really need to backup is default.ctx..just make a copy of it when you like what you have..when problems arise I just delete the original, recopy the latest one you kept... I keep many versions..:)
remember to save layouts after changes too..

Post by Burnart // Feb 17, 2008, 5:20pm

Burnart
Total Posts: 839
pic
There is an assumption built into forced autoload about how I use the software - which is annoying. On the modelside you can still apparently select between autoload or not autoload on startup - unfortunately it doesn't work.


I've found that with 7.5 modelside when I start its best to load my current scene manually - even if it has theoretically loaded automatically. Particularly when trying to use bones or a plugin associated with that scene. The startup "version" sometimes develops errors - not always sufficient to crash the scene but enough to ruin it. I've been trying to get into the habit of saving my scene then loading a blank new scene before exiting (but I simply forget to do it most of the time.)

Post by Tiles // Feb 17, 2008, 9:55pm

Tiles
Total Posts: 1037
pic
It's a known issue that autoload cannot be turned off. Known since years.

Post by scarroll // Feb 18, 2008, 9:05pm

scarroll
Total Posts: 19
pic
One trick is to get your ts7.51 folder the way you like it. Then setting the ts7.51 folder to read only by right-clicking the program folder->properties and uncheck/check 'Read Only'. Apply the changes to all sub folders.


I prefer just a basic cube or no objects in my scene at startup, the benefit being a faster start up rather then loading the last scene, which for all intents and purposes, may have moved and shouldn't bother loading anyways. The drawback is that your window settings won't be preserved, so get them the way you like before proceeding. You can always undo the readonly attribute later.


I discovered this recently as I've been having a frustratingly terrible time with a scene in a given directory on my system that won't save textures correctly. It just loses them! I suspect it may be an issue with the folder path name being too long. As when I use the archive features it preserves the information correctly. The above 'Read Only' trick won't affect the archive functionality as new folders are added dynamically, and it will help your start up time.


The read only trick may also resolve trueSpace's consistent known corruption of its own program folder, however I would also suggest you simply backup your ts7.51 folder for a quick delete and copy to restore it when ts does muck things up (and it will).


*EDITED*

Stan's suggestion of just backing up your default.ctx is probably enough. Although I haven't tried, it maybe worth just setting this file to read-only to lock your window preferences and startup scene.

Post by kena // Feb 19, 2008, 5:37pm

kena
Total Posts: 2321
pic
just the ctx file will probably be enough, but I did a search of all files that got modified when you use Truespace, and came up with the following for my backup folder:
default.ctx
trueSpace.tsp
truespace.cfg
truespace.cfl
truespace.prl
truespace.key


My thought being that if those files get modified by Truespace each time you open the program, any one of them could corrupt. Now I have them backed up and have used them to replace the ones in the ts directory whenever I have a problem.
If I change the open libraries in my TS, I create a dated backup folder in backup and move them there. then I re-copy all 6 into my main backup from the ts folder.

OK - I admit it. I'm a super cautious person.
Being super cautious has allowed me to recover from some pretty messed up things including 3 corrupt personal library folders and a corrupt \PythonScripts folder.

Post by Mitch // Apr 20, 2008, 10:32am

Mitch
Total Posts: 70
This thread is a gold mine of excellent tips.

It should be a sticky.


Kena I love your idea of setting up trueSpace as you like, including a blank scene, (this should be done on a fresh install).

Then exit trueSpace and write protect the trueSpace directory and all sub files.

Then you can move your scenes back that you will want to change and save.


It is amazing how stable trueSpace 751e has become since I have done this.

No more corruption of trueSpace and my scenes.


The help I have gotten from this forum in the last couple of weeks is amazing.

I have achieved more in two weeks than I have in two years.
Awportals.com is a privately held community resource website dedicated to Active Worlds.
Copyright (c) Mark Randall 2006 - 2024. All Rights Reserved.
Awportals.com   ·   ProLibraries Live   ·   Twitter   ·   LinkedIn