Resolution bug

#1 Did a bit of poking arund in the code. I know nothing about DX coding at all, but it looks like the problem is in
gfxD3DDevice.cpp

The error is produced when mD3DDevice is false. Looking above that, there is a section that appears to set this reference. It is based on #ifdef TORQUE_MT_HACKS (Arrgh!) :-)

As I say I don't know DX coding, so could anyone tell me if the problem is actually in that section of code and can it be easily fixed?

further poking shows me that that variable is used everywhere. So chances are the problem could be anywhere in that file :-(

(I had a log file error in here but I get that at lower resolutions and TSE still loads, so it is irrelevant to this problem)


Cheers,

Dave.

#2 Hi GG guys,

Left this a couple of days before bumping it. Anybody have an idea what might be causing this?

Thanks,

Dave.

#3 12560 x 1600 x 32 ??

is that a supported mode in directx or did you mean 1280 x 1600??

#4 Yeah... your drivers might have issues that high a res. ;) Or did you mean 1280?

#5 Oops! Sorry 2560 x 1600 x 32, dreaming about that other thousand :-)
It's a WQXGA 30" flat panel. Running on dual 7800 GTX cards with SLI.

Drivers are fine, windows works fine, all apps work fine, and the previous HEAD release of TSE works fine. It's just the latest HEAD that blows up (no jokes about head and blowing please ;). The text in the console is broken up and unreadable in the previous TSE release, but that's just a minor irritation as I can look in the log file. But it starts up OK and the game runs fine. It's only this release that won't start and gives me the error.

#6 Have you tried running with the Debug runtime for DirectX and seeing if you get any useful output in the debugger from it?

#7 Ben, no I haven't as I thought it must be some change in the code as the previous download works fine. As I mentioned before, I know nothing about DX and don't want to, that's why I bought the engine ;-) I'll have a whack at the debug thing if I can figure it out and let you know what gives.

#8 Well, built a debug version and it ran fine. Tried the release version afterwards and it ran fine too!! Rebuilt the release and still OK. So all I can imagine is that some other bit of software was interfering with the display the last few days (unless the debug build did something, but that's grasping at straws). I can't imagine what it was, as I haven't de-installed anything.

Oh well, chalk it up to the mysteries of Windoze. I honestly don't think it was PEBCAK.

BTW the demo looks absolutely sparkling at that resolution and with shaders 3, if you haven't seen it yourselves. In fact flying around from room to room makes my stomach lurch it's so realistic :-)

Cheers,

Dave.

#9 No, no, the DirectX debug runtime - it's a version of DirectX that will tell you if something bad is happening in DirectX, which seems likely to be the case here. You turn it on by going to the control panel, then hitting the DirectX icon there, and selecting "use debug version of Direct3D."

Then you run a version of TSE (debug or release, doesn't matter) under Visual Studio and watch the debug output pane to see if anything important gets said. Will usually have "[ERROR]" in front of it, IIRC.

Since we don't have your setup in the office, it's hard for us to track down the problem, but I'll bet that'll expose the issue. :)

#10 Ah, I see..doh! I did as you suggested but no errors as it seems to working again as I said. But if it happens again I'll run the debug version and see what comes up in the output. Thanks for the pointer.

Dave.