After I ran TransData to unpack the game I get an error on loading the normal unpacked version-
Unable to initialize Debug file.
I have TranscedenceSource in the same folder, and copied down the exe and music file to play it unpacked. If I start the game using the unpacked version it works fine, and then it allows me to start a game back in the original folder.
Sometimes the debug file won't allow itself to be deleted. The error is intermittent.
Debug unable to be initialized!
- Periculi
- Fleet Officer
- Posts: 1282
- Joined: Sat Oct 13, 2007 7:48 pm
- Location: Necroposting in a forum near you
I am getting this same error with 099b. The debug file can't be accessed and windows says it's in use by another application. Transcendence says unable to initialize and won't load the game.
- Periculi
- Fleet Officer
- Posts: 1282
- Joined: Sat Oct 13, 2007 7:48 pm
- Location: Necroposting in a forum near you
I have to start a Transcendence game in a different folder altogether to get the debug file to be freed up.
It seems to get locked up somehow, then if I start transcendence from a different folder (even a different version) the first transcendence will start up again.
I just tried to start 099b, for the second time, and got the error. No other games or programs running.
Then I went into 099a folder and started that Transcendence.exe. Exited that and went back to the 099b folder and started Transcendence.exe there just fine again.
I encountered this error in 099a first after unpacking the game. Now it happened without having unpacked 099b. Only it seems to be happening MUCH more often (like every other time I go to start the game)
It seems to get locked up somehow, then if I start transcendence from a different folder (even a different version) the first transcendence will start up again.
I just tried to start 099b, for the second time, and got the error. No other games or programs running.
Then I went into 099a folder and started that Transcendence.exe. Exited that and went back to the 099b folder and started Transcendence.exe there just fine again.
I encountered this error in 099a first after unpacking the game. Now it happened without having unpacked 099b. Only it seems to be happening MUCH more often (like every other time I go to start the game)