ATI Driver update or...

[WinstonSmith6079]

Yeah, okay. But where can I find drivers like the ones on that link of mine above, except they're v10.1? ???

[Sp00kyFox]

found an interesting thread about this issue in the amd game forums.
don't know why but packing the gzdoom executable with upx seems to resolve the problem.
just tried it and now gzdoom works again in opengl mode wit catalyst 10.3

http://forums.amd.com/game/messageview. ... did=128067
http://upx.sourceforge.net/

[magmus]

found an interesting thread about this issue in the amd game forums.
don't know why but packing the gzdoom executable with upx seems to resolve the problem.
just tried it and now gzdoom works again in opengl mode wit catalyst 10.3

http://forums.amd.com/game/messageview. ... did=128067
http://upx.sourceforge.net/

That works flawlessely, you should post a seperate thread about this fix!

[Edward-san]

Executables compressed with UPX cannot use shared memory for common code. For DLL's, this means that code and data which would be using shared global memory normally would instead be using exclusive memory local to the process that loaded the library.

So one possible interpretation is that there's a bug that causes overruns in the DLL in a certain section, which, with shared memory, would try to write to memory not owned by the calling process, thereby throwing the exception. With the whole DLL loaded into the owning processes's address space, the same overrun would likely affect only memory owned by the process, which prevents the access violation. If that's the case, then there could easily be other side effects - corruption somewhere in the program, which may or may not manifest itself during gameplay.

What does it mean?

[Sp00kyFox]

well it seems to be a nasty trick cuz it obviously destroys the possibility to load custom wads.
at least the software mode is working on amd cpus

[Gez]

well it seems to be a nasty trick cuz it obviously destroys the possibility to load custom wads.

Obviously?

[Sp00kyFox]

sry for the confusion I meant "apparently"
if packed with upx gzdoom seems to ignore every additional custom wad given by the commandline

[Gez]

Weird.

ZDoom does not use different mechanisms to load the IWAD vs. other files, so the only explanation I see is that the command line parameters are simply lost when it's packed with UPX. This could actually make sense from a technical standpoint, since these parameters would actually be received by the unpacking process which may fail to transmit them correctly to the process of the packed executable.

[Rachael]

And also, that seems to be a mere work-around to the problem than an actual solution.

If you pack the executable with UPX, then your crash reports become completely useless because after loading, the executable addresses are different from what they were at compile time.

[magmus]

well it seems to be a nasty trick cuz it obviously destroys the possibility to load custom wads.
at least the software mode is working on amd cpus

What on earth? I am using the latest GZdoom with AEoD v5 and it works flawlessely, even loads everything and every feature is working smooth.

EDIT:

Oh, and to add to that i am using .pk3 files and 1024cla2.wad file.

And all i did is pack the gzdoom.exe with UPX like you spotted out.

[Sp00kyFox]

ooops.. yeah you're right, my directories were messed up.
so yup... rly seems to be a solution for all the ati users who couldn't use gzdoom any more with the new catalyst drivers.
good luck with that to all the other ati users and happy fragging

[magmus]

ooops.. yeah you're right, my directories were messed up.
so yup... rly seems to be a solution for all the ati users who couldn't use gzdoom any more with the new catalyst drivers.
good luck with that to all the other ati users and happy fragging

Yeah thanks for the fix anyways!

[Rachael]

Just remember if you crash through other means the crash reports will be useless... there won't be anything we can do about them.

[WinstonSmith6079]

found an interesting thread about this issue in the amd game forums.
don't know why but packing the gzdoom executable with upx seems to resolve the problem.
just tried it and now gzdoom works again in opengl mode wit catalyst 10.3

http://forums.amd.com/game/messageview. ... did=128067
http://upx.sourceforge.net/

Thank you very, very much! Nice work-around--GZDoom works in full again, even with PWADs, no problemo!

Take note, though, that previously saved games won't work with the UPX-packed GZDoom. It will, however, create new saved games that can be loaded without issue as normal.

Thanks again! You rule!

[Sp00kyFox]

Thank you very, very much! Nice work-around--GZDoom works in full again, even with PWADs, no problemo!
Take note, though, that previously saved games won't work with the UPX-packed GZDoom. It will, however, create new saved games that can be loaded without issue as normal.
Thanks again! You rule!

well no problem I just did a little research in the amd forums, so no big deal ^^
maybe we should do an extra thread for all the ati users.
or a moderator could rename the thread so anybody can see that it includes a solution to the problem.