Scaling specific texture with a neative value disappears

[Enjay]

I also noticed that the texture was scaled in the X direction (5. something if I recall). I can't check it right now but does changing/removing the X scale factor change anything?

[Tormentor667]

I also noticed that the texture was scaled in the X direction (5. something if I recall). I can't check it right now but does changing/removing the X scale factor change anything?

I didn't try 5 but 4.0, 1.1, -2.0 and -0.1. It disappeared if it was a negative value, it appeared when positive or the "wrap" flag was active.

[Enjay]

OK, a little more information. The translucency of the texture is part of the problem. If I resave the image as fully opaque,

original versus edit

it works (this is in an unedited map).

I noticed that the line also has translucency so I tried switching that off instead of changing the texture. The texture did not appear as visible in the map. i.e. the fault persisted.


And just to be clear, the -1 Y scaling is still part of the equation too because if I edit the lines to remove that, the texture is visible.

That is the map edited so that those lines have a y scale of 1 instead of -1. No other changes (to the map or the texture) were made.

I didn't try 5 but 4.0, 1.1, -2.0 and -0.1. It disappeared if it was a negative value, it appeared when positive or the "wrap" flag was active.

I think that maybe you picked me up wrongly? I meant that in your map, the textures in question also have an x-scale value of 5-point-something (5.57 or 5.65) and I was wondering it that would have any impact. I tried setting it to 1. This had no impact on the problem. (i.e. the problem was still there.)

[Tormentor667]

OK, a little more information. The translucency of the texture is part of the problem. If I resave the image as fully opaque, original versus edit

We are getting closer But this is obviously an engine bug. I tend to save images for these kind of special effects with an alpha channel to avoid being forced to use additive translucency when having an opaque image. That way you can also do other crazy things that wouldn't be possible with a black background.

[Enjay]

Oh yes, absolutely, I wasn't trying to say that it isn't an engine bug. I was merely mentioning something that I'd found that might help track down where the problem lies.

[Tormentor667]

Sorry for bumping this but has this already been resolved somehow?

[Graf Zahl]

Have you seen this thread being moved to 'closed bugs'?

[Tormentor667]

Sorry for asking A „no, we haven’t investigated this any further“ would have been ok as well

[Graf Zahl]

I'M afraid but with this map I cannot investigate this. Please post something smaller where I a) do not have to search the map for the problem spot and b) only contains a single wall that's causing the glitch.

[Tormentor667]

All I can currently do is this description for where to find the right spot, I hope that helps for the investigation.

Link: https://www.realm667.com/index.php/en/d ... -austerity
Map: MAP02
Coordinates: X 930 | Y 350
Example line: 1041
Texture in question: GLOW_W.PNG

[Graf Zahl]

fixed. This fell victim to an optimization to reduce empty space in mid textures. The code for that was written for unmirrored textures only.

[Tormentor667]

Thanks kindly for the fix Graf Zahl!