Never a problem -- now Dom2 crashes to desktop

PDF · #1 September 20th, 2004, 01:25 PM

Tinkthank
Re windowed mode : I divine you have a ATI card

, so instead trying to go through "preferences" just edit your Dom2 shortcut and put a -w flag in the command line.
(I myself experienced grahics problem when going into/out of windowed mode ..)

Re crash after taskman : just delete the dom16882 folder each time you crash it

Hope it helps

Alneyan · #2 September 20th, 2004, 01:40 PM

Hitting the F12 key (if it is the one that results in the windowed mode) also seems to work to activate it. At least, it does for me and my ATI card. It tends to take quite some time to work, but it should eventually work.

tinkthank · #3 September 22nd, 2004, 06:23 AM

Wow, thanks so very much! That helped, the game can run now. Thanks to all!
PDF, you have amazing divination skills! Yes, I truly have an ATI card, how did you know? This "command line" is what is in the shortcut window, right? I put a space and then -w (so: "... dom2.exe -w") and that worked perfectly, and deleting that file did too. Thanks so much!

PDF · #4 September 22nd, 2004, 10:23 AM

Quote:

tinkthank said:
Wow, thanks so very much! That helped, the game can run now. Thanks to all!
PDF, you have amazing divination skills! Yes, I truly have an ATI card, how did you know? This "command line" is what is in the shortcut window, right? I put a space and then -w (so: "... dom2.exe -w") and that worked perfectly, and deleting that file did too. Thanks so much!

Thanks ! Ya know, I'm an Astral-3 guy ...

For the ATI card, I happen to have one since I've changed my rig on Last Xmas - before I had a GF2, 0 problem with Dom2, and with the ATI I've had to use the -w switch to prevent a systematic graphic "crash" when trying to minimize/alt-tab the game ... And several peoples complained of issues with the ATI drivers ,also.

And yes I was referring to the shortcut command line

Glad to help

.

Arryn · #5 September 22nd, 2004, 10:34 AM

Quote:

PDF said:
For the ATI card, I happen to have one since I've changed my rig on Last Xmas - before I had a GF2, 0 problem with Dom2, and with the ATI I've had to use the -w switch to prevent a systematic graphic "crash" when trying to minimize/alt-tab the game ... And several peoples complained of issues with the ATI drivers ,also.

Aha! Thanks. I was wondering what the deal was with the ALT-TAB bugginess, since I never had the problem with my old GF4 4400 prior to upgrading Last month to a Radeon 9600XT. I, too, had resorted to the -w without having read about others having similar problems. Has anyone reported the Dom 2 problems to ATI so that they might (wishful thinking, I know) provide a fix in some upcoming Catalyst release?

Arralen · #6 September 22nd, 2004, 11:37 AM

Quote:

Arryn said:Has anyone reported the Dom 2 problems to ATI so that they might (wishful thinking, I know) provide a fix in some upcoming Catalyst release?

It's still not quite clear, if it's a DOM2 problem, or a problem with the SDL library, or with OpenGL on ATI cards in general. Maybe it's related to the perfomance problems with those cards, maybe not. But the devs never gave any comment, so it wouldn't make sense to tell ATI about it.

After all, maybe it's just broken code in Dom2 which the devs cannot correct because they don't know better

On the other hand, ATIs OpenGl support sucks ... but they promised to work on it as .. what was it .. Doom3(?) runs with OpenGl as well

Arryn · #7 September 22nd, 2004, 12:14 PM

Arralen: Good points you've made. Having recently tried Doom 3 on my allegedly inferior-performing ATI card, I can say that it's OGL performance is more than acceptable. I get great graphics and decent frame rates (and that's with all the bells & whistles turned to max). So I'm left to ponder why Dom 2 (and only Dom 2) sucks on ATI? You just may be right in your hypothesis regarding bad code ...