Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] HD Textures using incorrect skyboxes and switches with 4.14 #2899

Open
1 task done
BlackOpsMarine opened this issue Jan 14, 2025 · 5 comments
Open
1 task done

Comments

@BlackOpsMarine
Copy link

GZDoom version

GZDoom 4.14

Which game are you running with GZDoom?

Doom 2

What Operating System are you using?

Windows 10

Please describe your specific OS version

No response

Relevant hardware info

No response

Have you checked that no other similar issue already exists?

  • I have searched and not found similar issues.

A clear and concise description of what the bug is.

For some reason GZDoom 4.14 uses the incorrect skybox for the main doom wads as well as some of the switches and other textures compared to older versions. Is there a possible fix for this? (Screenshotted below are some comparison pictures between what the textures are supposed to look like using GZDoom 4.11.3 and what they look like now when using 4.14, using the HD texture mod only).
Screenshot_Doom_20250114_020258
Screenshot_Doom_20250114_020315
Screenshot_Doom_20250114_020535
Screenshot_Doom_20250114_020615
Screenshot_Doom_20250114_020620

Steps to reproduce the behaviour.

Explain how to reproduce

  1. Load ZDoom HD Textures from https://github.com/KuriKai/dhtp/wiki
    2.Compare skybox and switches and any other texture using any older version of GZDoom to 4.14

Your configuration

No response

Provide a Log

No response

@RicardoLuis0
Copy link
Collaborator

can you confirm if this did break on 4.14 or in some other version between 4.11.3 and 4.14?

@BlackOpsMarine
Copy link
Author

I think 4.13 also had the same issue iirc but I haven't used it much

@BlackOpsMarine
Copy link
Author

I think 4.13 also had the same issue iirc but I haven't used it much

Can confirm that this issue started and persists with GZDoom 4.12 and 4.13 after testing

@BlackOpsMarine
Copy link
Author

Is there anyway to fix this issue or no?

@RicardoLuis0
Copy link
Collaborator

it still needs for someone to look into it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants