Today, I play ASDOOM][: The Final Countdown.
(http://www.doomworld.com/idgames/index.php?id=1570)
But I encounter a bug and can be reproduce in Map02.
Attachments are screenshots and the savegame before messed up.
(Even it looks like already messed up. But it isn't.)
My system : AMD A64 X2 3600+, 1GB RAM, MSI NX8600GT 256MB.
(I just used the driver in display card's package and didn't update driver yet...is it a problem?
I don't like update 8x00's driver...it's pain...)
EDIT : Forgot said... I used Nash's latest build, should be r123.
[1.1.04 r123M]Floor/ceiling texture messed up.
Moderator: Graf Zahl
-
- Posts: 62
- Joined: Sat Sep 23, 2006 6:28
- Location: Taipei county, Taiwan
[1.1.04 r123M]Floor/ceiling texture messed up.
- Attachments
-
- The floor/ceiling texture messed up.
- Screenshot_Doom_20080620_222428.png (174.61 KiB) Viewed 1024 times
-
- save1.rar
- Savegame before mess up.
Load with this, turn left till you get messed up like screenshot. - (54.19 KiB) Downloaded 74 times
- Enjay
- Developer
- Posts: 4748
- Joined: Tue Aug 30, 2005 23:19
- Location: Scotland
- Contact:
- Graf Zahl
- GZDoom Developer
- Posts: 7148
- Joined: Wed Jul 20, 2005 9:48
- Location: Germany
- Contact:
Re: [1.1.04 r123M]Floor/ceiling texture messed up.
playerlin wrote: (I just used the driver in display card's package and didn't update driver yet...is it a problem?
If setting gl_clamping_bug helps, most likely yes. I also use a GF8600 and all works fine for me - but I am using current drivers.
-
- Posts: 62
- Joined: Sat Sep 23, 2006 6:28
- Location: Taipei county, Taiwan
Re: [1.1.04 r123M]Floor/ceiling texture messed up.
"gl_clamping_bug 1" works, thanks a lot.Graf Zahl wrote: If setting gl_clamping_bug helps, most likely yes. I also use a GF8600 and all works fine for me - but I am using current drivers.
Yeah... it's driver problem... I will try update the driver and hope it will not make me become a pain-ass... :p
- Graf Zahl
- GZDoom Developer
- Posts: 7148
- Joined: Wed Jul 20, 2005 9:48
- Location: Germany
- Contact:
I already changed the default of this CVAR to 1. This problem was introduced when I got a new computer with Vista installed.
Apparently the new Vista drivers handle texture clamping differently. Older drivers only seem to have one global state for this information (which obviously can be changed quickly without any performance penalty whereas Vista caches it per texture and changing it has a heavy performance impact. So obviously the old code doesn't work well on Vista and the new code produces this bug on older systems. If I knew a way to test this I could get around it without making this differentiation myself.
Apparently the new Vista drivers handle texture clamping differently. Older drivers only seem to have one global state for this information (which obviously can be changed quickly without any performance penalty whereas Vista caches it per texture and changing it has a heavy performance impact. So obviously the old code doesn't work well on Vista and the new code produces this bug on older systems. If I knew a way to test this I could get around it without making this differentiation myself.
