Page 1 of 1
Crash on widescreen computer
Posted: 22 Dec 2004 20:16
by krtaylor
I tried to use the new resolution-setting feature on a fancy new widescreen laptop my brother has. It crashes. I can play the game just fine in windowed mode, but when I do it fullscreen, it won't, even though I'm setting the resolution to be the same as the resolution Windows says the screen uses. Here's the crashlog:
Posted: 23 Dec 2004 08:54
by eis_os
What I need:
Graphic Card Type, OS Type.
Under Windows Video Settings, if you can select 256 Colors.
tt-config.exe settings (what mode you use, if you have the safe checkbox enabled)
If you can select 256 colors, start tt-config and select mode 4, press the run the game button so tt-config will safe it. Then use ttdpatchw and see what happen. (If it works then, please say me how you made the settings the first time)
Next try: Switching the safe checkbox in the tt-config.exe, let it safe the settings as before...
Then you could try to start a game with TTDPatch 2.0.1 alpha 40c at
http://www.tt-forums.net/viewtopic.php?t=12075
Posted: 23 Dec 2004 15:07
by krtaylor
It's a Toshiba widescreen laptop, running XP. I'll do the tests you describe later today, and post the results.
BTW, can you play multiplayer TTD with the resolutions set differently on the two computers? I'd think so, but normally the CFG file has to be the same.
Posted: 23 Dec 2004 15:34
by eis_os
to be honest I don't know, but because the mouse isn't transmitted only the actions it should work, but before bug reporting try only the minimum of features in TTDPatch
Posted: 23 Dec 2004 15:52
by krtaylor
Well, if I get this resolution working in local mode, the next thing I will try is multiplayer with a different resolution, and I'll let you know. Of course I could always use the same resolution on both sides, that I'm pretty sure will work, as a smaller-than-fullscreen resolution works fine on the laptop; it's just when I try to do fullscreen that I have problems.
Posted: 23 Dec 2004 16:11
by krtaylor
The computer is a Toshiba Satellite P35-S609. Since it's a laptop, I can't look at the chip, but Windows XP Pro reports it to be an ATI Mobility Radeon 9000 IGP.
The driver lets me choose between 16 bit and 32 bit color, it's set on 32 bit. It does NOT let me select 256 colors.
When I crashed it, I wasn't using safe mode. I'm about to try that.
Posted: 23 Dec 2004 16:17
by krtaylor
OK, I tried it in safe mode, and it worked... sort of.
1. It didn't crash.
2. The sound worked fine, and the game seemed to work fine.
3. The graphic refresh wasn't working. I mean, when it came up, most o the screen was black; the graphics were displayed only as I moved the mouse around. (I was using game mouse.)
4. When I started a game, the screen again didn't refresh. When I moved the window around, only the LEFT half of the screen moved and refreshed; the right half stayed the same and didn't refresh until I ran the mouse over it. Annoying and somewhat unusable.
5. For some odd reason, there was a vertical bar of maybe 50 pixels at the extreme right edge of the screen, that stayed black at all times. Maybe the Patch didn't like the odd aspect ratio? Am I the first person to try it on a widescreen display?
I'm going to try it with the Windows cursor now.
Posted: 23 Dec 2004 16:20
by krtaylor
Fullscreen with Windows mouse worked about the same, only it was even worse at refreshing.
Fullscreen with Windows mouse, NOT safe mode, crashed.
I'll see what happens with a40c later today.
Posted: 23 Dec 2004 16:22
by eis_os
If you can't use 256 colors native, TTDPatch will likely crash because it has a 0 screenmode...
What screenresolution do you have.
Posted: 23 Dec 2004 18:52
by krtaylor
Native resolution, according to the driver, is 1440x800.
So you are saying that TTD is 256 only and can't run if the driver won't do that? But it works OK in a window, how does that work? I don't suppose there's a way to get it to interpolate in a virtual high-color mode?
Posted: 23 Dec 2004 19:28
by eis_os
Because ATI cards made the init code overflowing Josef limited to modes with 256 colors, now with your laptop we have the problem you don't have a 256 color mode, thats why I asked you to use a alpha 40c and try it:
a) it crashes because you have to many other modes.
b) it crashes because you have some other problems.
Did you tried the toggleing the savemode checkbox in tt-config?
Ohh, in window mode the 256 color will be always converted while TTD copies it into the window via a GDI call...
Posted: 23 Dec 2004 20:24
by krtaylor
eis_os wrote: thats why I asked you to use a alpha 40c and try it:
I will, just haven't yet.
eis_os wrote:a) it crashes because you have to many other modes.
What do you mean?
eis_os wrote:b) it crashes because you have some other problems.
Doubt it, because it works fine in windowed mode.
eis_os wrote:Did you tried the toggleing the savemode checkbox in tt-config?
Yes, as reported above. It worked and didn't crash, but the refresh wasn't working so the game was rather awkward to play.
Posted: 23 Dec 2004 23:37
by krtaylor
OK, I tried it with a40c. It complained about the new switches that it doesn't recognize, but I had it continue anyway - extra switches don't hurt, do they? It also complained about needing mkpttxt.exe, but the a40c file didn't come with one, so I ignored that also. And it didn't work either, it crashed just the same. It seems to me that the problem is as you described - my driver doesn't do 256 colors, since that's obsolete, and the ATI buffer problem that you solved conflicts with that. Any ideas as to a solution?
Posted: 24 Dec 2004 08:47
by eis_os
May I ask, does it work without resolution switch in 640x480 or will crash aswell? I am sorry but I guess you have to stick to window mode...
Posted: 24 Dec 2004 14:43
by krtaylor
eis_os wrote:May I ask, does it work without resolution switch in 640x480 or will crash aswell?
I don't understand the question. If you mean, will it work in full screen at any other resoultion than the native, no. It does the requested resolution, but stays in a window even though it's "supposed" to be full screen. (Works fine though). I guess the driver knows it's the wrong resolution and won't even try to run it that way.
eis_os wrote: I am sorry but I guess you have to stick to window mode...
That's OK, but I wanted to report the bug anyway.

Thanks for the help.