[1.8.0] Small texture placement problem

Bugs that have been resolved.

Moderator: Graf Zahl

Locked
Alexis
Posts: 18
Joined: Sun Jun 09, 2013 10:49

[1.8.0] Small texture placement problem

Post by Alexis »

Hello there,

I found a bug using ACTION2.WAD in Gzdoom. This bug didn't appears in Zdoom, here is a comparison :

Image
Mirrorman95
Posts: 2
Joined: Sat Jun 08, 2013 9:38

Re: [1.8.0] Small texture placement problem

Post by Mirrorman95 »

I'm also getting that problem on my iMac. The cab looks fine in ZDoom, but in GZDoom, the texture is shifted halfway down.
User avatar
NeuralStunner
Posts: 253
Joined: Tue Dec 29, 2009 3:46
Location: IN SPACE
Contact:

Re: [1.8.0] Small texture placement problem

Post by NeuralStunner »

Does your video card support non-power-of-two textures? (I'm not sure but that might cause these sorts of issues.)
Dean Koontz wrote:Human beings can always be relied upon to exert, with vigor, their God-given right to be stupid.
Spoiler: System Specs
Alexis
Posts: 18
Joined: Sun Jun 09, 2013 10:49

Re: [1.8.0] Small texture placement problem

Post by Alexis »

I tested on a 32-bits system equiped with a Geforce 8800 GTX and on a 64-bits system with an I5 processor graphics. The same bug on the two different systems.
User avatar
Enjay
Developer
Developer
Posts: 4748
Joined: Tue Aug 30, 2005 23:19
Location: Scotland
Contact:

Re: [1.8.0] Small texture placement problem

Post by Enjay »

Yeah, I'm seeing the bug too on Win7 64 bit with a GeForce GTX 285.
_mental_
Developer
Developer
Posts: 259
Joined: Sun Aug 07, 2011 13:36

Re: [1.8.0] Small texture placement problem

Post by _mental_ »

It was broken in r1460 but at the moment I have no idea how to fix it without reverting gl_walls.cpp to previous revision.
User avatar
Graf Zahl
GZDoom Developer
GZDoom Developer
Posts: 7148
Joined: Wed Jul 20, 2005 9:48
Location: Germany
Contact:

Re: [1.8.0] Small texture placement problem

Post by Graf Zahl »

Fixed

I knew it that the patch would cause some problems. I didn't apply it and unfortunately I never had the time to properly check it.
What it did wrong is simple: Instead of the scaling factor coming from the map data it used the composite scaling factor of both map data and texture definition which effectively applied the texture based part twice.

This is why I am very careful with user-submitted patches that change sensitive code. This should never have been added without a full review of the effects.
Locked

Return to “Closed Bugs”