Valkyre on 9/3/2005 at 19:59
When I hit "Play map", the editor begins to load the map, and goes all the way into the actual loading screen with the thief background and such, then it halts with an error message. I can't see what the error message is because Thief won't minimize, it won't even respond to Alt+F4 or control-alt-delete commands. However it DOES go back to the desktop if I hit enter on the keyboard (this closes the error box which I can not see)
I folllowed the installation of the editor as per the (
http://www.ttlg.com/wiki/wikka.php?wakka=Installation) FleshWorks instructions.
I have a P4 3.0GHz processor, 1GB RAM, GeForce 6800, 160GB hard drive w/ 80GB backup drive, and Audigy 2 sound card. Nothing is overclocked at the moment.
Any idea on what's going on? I really want to play my levels. :(
David on 9/3/2005 at 20:28
Are you positive that you have renamed T3MainOptVersion.exe to T3Main.exe?
Eshaktaar on 9/3/2005 at 20:37
I had to copy the .gmp files (in the Maps folder) from the game installation to the editor installation before I could play any maps. Maybe it's worth a try?
Krypt on 9/3/2005 at 20:40
I had this same problem recently. At a certain point I just couldn't run my map from the editor anymore, it would just crash after loading for a while. I looked in the t3main.log and the last line was something about the static vertex pool. If I recall correctly, the static vertex pool is a max number of vertices for static objects that a map can contain, or something along those lines. This would mean my map had too many vertices, which is odd because my map is nowhere near the complexity of the average T-DS map. I don't think I ever ran into this limit at ISA, even when our maps were huge sprawling goliaths at least 3x the size of the ones in the shipping game. I was able to turn up the static vertex pool in my default.ini, but the game chugged when running my map after that. That works as a quick-fix, but it would be pretty lame to make people edit their ini files in order to play a map when it's released.
Rosd on 9/3/2005 at 20:54
Levels three times the size of what shipped with the game? The pure awesome potential of the editor being released could become quite clear to the Thief: DS naysayers. Makes me wonder if anyone ever decided to burn any of those to a disk somewhere.
Valkyre on 9/3/2005 at 21:04
Ok, after copying the .gmp files to my maps directory in the Thief 3 Editor directory, my map loads now. However, it seems pretty sluggish. Not entirely bad, but worse than the normal game.
SubJeff on 9/3/2005 at 21:06
Valkyre - I had exactly the same problem. Turning off ZoneAlarm fixes it for me.
David on 9/3/2005 at 21:08
It will peform more sluggishly as it has 2MB of debug code in it, check out your Thief - Deadly Shadows directory in My Documents after running a mission from the editor.
OrbWeaver on 9/3/2005 at 21:38
Quote Posted by Krypt
I had this same problem recently. At a certain point I just couldn't run my map from the editor anymore, it would just crash after loading for a while. I looked in the t3main.log and the last line was something about the static vertex pool. If I recall correctly, the static vertex pool is a max number of vertices for static objects that a map can contain, or something along those lines. This would mean my map had too many vertices, which is odd because my map is nowhere near the complexity of the average T-DS map. I don't think I ever ran into this limit at ISA, even when our maps were huge sprawling goliaths at least 3x the size of the ones in the shipping game. I was able to turn up the static vertex pool in my default.ini, but the game chugged when running my map after that. That works as a quick-fix, but it would be pretty lame to make people edit their ini files in order to play a map when it's released.
Sounds like a memory leak.
How many times had you tested the map before the problem began? Did you try rebooting?
Krypt on 9/3/2005 at 21:52
Quote Posted by OrbWeaver
Sounds like a memory leak.
How many times had you tested the map before the problem began? Did you try rebooting?
I had tested the map at least 5 or 6 times that night while working on it, and plenty of times in days before that while I was building it. It was strange, I had tested it just a minute or two before it stopped loading and only made a couple minor additions which seemed to push it over the edge. To test, I went back and deleted all the stuff I added, but it still wouldn't run.
