Bugged Texture?
Moderator: GZDoom Developers
Forum rules
Before asking on how to use a ZDoom feature, read the ZDoom wiki first. If you still don't understand how to use a feature, then ask here.
Before asking on how to use a ZDoom feature, read the ZDoom wiki first. If you still don't understand how to use a feature, then ask here.
- Kappes Buur
-
- Posts: 4120
- Joined: Thu Jul 17, 2003 12:19 am
- Graphics Processor: nVidia (Legacy GZDoom)
- Location: British Columbia, Canada
- Contact:
Re: Bugged Texture?
I don't know how or what you did to get this result.
I made a new texture with the combination of WOLF9 and the head from RW26_2
in editor
I made a new texture with the combination of WOLF9 and the head from RW26_2
in editor
Spoiler:in game
Spoiler:which works for me, unless I misunderstood your post.
-
- Posts: 35
- Joined: Tue Jun 09, 2020 7:16 am
- Graphics Processor: nVidia (Modern GZDoom)
- Location: North Korea
Re: Bugged Texture?
interesting. I have another texture which I merged the button too, and that works like normal.Kappes Buur wrote:I don't know how or what you did to get this result.
I made a new texture with the combination of WOLF9 and the head from RW26_2
in editorSpoiler:in gameSpoiler:which works for me, unless I misunderstood your post.
Also, I tried deleting and re-adding the texture, but it doesn't work either.
All I did is combining SW4S0 and ZZWOLF9 with an image editing program.
Re: Bugged Texture?
If you can upload the problem files, it will be a lot easier for people to check.
-
- Posts: 35
- Joined: Tue Jun 09, 2020 7:16 am
- Graphics Processor: nVidia (Modern GZDoom)
- Location: North Korea
Re: Bugged Texture?
Enjay wrote:If you can upload the problem files, it will be a lot easier for people to check.
https://drive.google.com/file/d/1aE01FT ... sp=sharing
There we go. I deleted most of the assets and codes not to spoil my project, so there are some missing textures.
Re: Bugged Texture?
OK, I *think* I know what is going on here. You have your texture between F_* markers. That puts them in the flats namespace and GZDoom has special handling for graphics in that namespace that are multiples of 64x64 (it scales them).
Whether that's the exact cause or not, I can't be sure but, certainly, changing F_START and F_END to TX_START and TX_END (texture namespace markers) fixes the problem.
As for why GZDoom and UDB show the texture differently - my guess is that UDB isn't using the special handling and GZDoom is.
Whether that's the exact cause or not, I can't be sure but, certainly, changing F_START and F_END to TX_START and TX_END (texture namespace markers) fixes the problem.
As for why GZDoom and UDB show the texture differently - my guess is that UDB isn't using the special handling and GZDoom is.
-
- Posts: 35
- Joined: Tue Jun 09, 2020 7:16 am
- Graphics Processor: nVidia (Modern GZDoom)
- Location: North Korea
Re: Bugged Texture?
I think you fixed my problem. Thanks.Enjay wrote:OK, I *think* I know what is going on here. You have your texture between F_* markers. That puts them in the flats namespace and GZDoom has special handling for graphics in that namespace that are multiples of 64x64 (it scales them).
Whether that's the exact cause or not, I can't be sure but, certainly, changing F_START and F_END to TX_START and TX_END (texture namespace markers) fixes the problem.
As for why GZDoom and UDB show the texture differently - my guess is that UDB isn't using the special handling and GZDoom is.
Re: Bugged Texture?
No problem.
Just in case it is something that UDB doesn't support and there is a need/will to add it, I have flagged it up here.
viewtopic.php?f=232&t=66745&p=1207924#p1207924
[edit]
While I was digging into your file I noticed that the problem wall was constructed in a weird way.
Is there a reason that you went for this:
instead of this:
Just in case it is something that UDB doesn't support and there is a need/will to add it, I have flagged it up here.
viewtopic.php?f=232&t=66745&p=1207924#p1207924
[edit]
While I was digging into your file I noticed that the problem wall was constructed in a weird way.
Is there a reason that you went for this:
instead of this: