mudi on 14/10/2009 at 22:25
Works beautifully here. Played through the training mission in glorious 1080p, was able to exit the mission without the crash.
Great work! :thumb: This probably deserves a thread in the thief forum.
Hadley on 15/10/2009 at 06:19
Quote Posted by mudi
Great work! :thumb: This probably deserves a thread in the thief forum.
Thanks for the heads up, didn't realize I wasn't in the Thief forum :P Went ahead and made a post there about it as well.
JDelwynn on 15/10/2009 at 10:27
Quote Posted by Hadley
Hmm... I wrote it for 1.1, although I'm not sure if the 1.1 patch changes T3main.exe at all. Though, the patch should only apply itself if it recognizes the code that causes the freeze. Do the crashes still occur if you revert all in my patcher?
I reverted everything, and no crashes. That is not news in any way, because it does not crash without widescreen anyway.
Hadley on 15/10/2009 at 22:17
Hmm... the code the patch modifies should only be run when you click on a mission to load, or get to the "end mission now?" screen... I'm not sure why you'd get the no signal issue, unless Thief 3's trying to set some refresh rates your monitor doesn't like. What happens when the patch is applied but you leave the built-in resolutions alone? The quickest way to test the patch is to just attempt to load a saved game and see if it lets you.
JDelwynn on 16/10/2009 at 11:06
Quote Posted by Hadley
Hmm... the code the patch modifies should only be run when you click on a mission to load, or get to the "end mission now?" screen... I'm not sure why you'd get the no signal issue, unless Thief 3's trying to set some refresh rates your monitor doesn't like. What happens when the patch is applied but you leave the built-in resolutions alone? The quickest way to test the patch is to just attempt to load a saved game and see if it lets you.
Yeah, the out of sync issue was my fault (I set the wrong resolution). Still the game crashes everytime I try to load or finish the mission.
mudi on 16/10/2009 at 12:55
Double-check that you toggled the fix for that in the patch, I guess...
Hadley on 18/10/2009 at 20:07
Quote Posted by JDelwynn
Yeah, the out of sync issue was my fault (I set the wrong resolution). Still the game crashes everytime I try to load or finish the mission.
Hmm... What OS and resolution are you running? I'm running a 64-bit version of Windows here, and to be fair the patch I did was essentially "okay, I don't really understand this code... Let's see if THIS fixes it!" and preventing an infinite loop from continuing. If I could get the crash to occur here, it'd make it a lot easier to find out what's going on, but I'll still take a closer look at what I'm doing and why it might crash.
JDelwynn on 19/10/2009 at 01:32
Quote Posted by Hadley
Hmm... What OS and resolution are you running? I'm running a 64-bit version of Windows here, and to be fair the patch I did was essentially "okay, I don't really understand this code... Let's see if THIS fixes it!" and preventing an infinite loop from continuing. If I could get the crash to occur here, it'd make it a lot easier to find out what's going on, but I'll still take a closer look at what I'm doing and why it might crash.
I have Windows XP pro SP3 and the resolution is 1360x768. I think my problem somehow relates to that Visual C++ 2005 debugger. After googling a bit I found other people who had the same problem, although with different programs, where after removing the debugger, the program just crashes.
Hadley on 19/10/2009 at 01:39
Quote Posted by JDelwynn
I have Windows XP pro SP3 and the resolution is 1360x768. I think my problem somehow relates to that Visual C++ 2005 debugger. After googling a bit I found other people who had the same problem, although with different programs, where after removing the debugger, the program just crashes.
Nah, the VC++ debugger only comes up after a program has crashed, it wouldn't cause the crash at all. It looks like the 1360x768 resolution runs here fine, but I made a second version of the patcher that tries patching somewhere else. Try giving it a run and see how it works? (
http://www.foxular.net/asdf/t3_widescreen.exe)
JDelwynn on 19/10/2009 at 02:49
Quote Posted by Hadley
Nah, the VC++ debugger only comes up after a program has crashed, it wouldn't cause the crash at all. It looks like the 1360x768 resolution runs here fine, but I made a second version of the patcher that tries patching somewhere else. Try giving it a run and see how it works? (
http://www.foxular.net/asdf/t3_widescreen.exe)
Still crashing... I was about to blame the gremlins when I realised something! Does it make any difference, that my version of T3 is bought from Steam?
