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

Isengard tower graphics bug #25

Closed
Helliaca opened this issue Sep 17, 2022 · 5 comments
Closed

Isengard tower graphics bug #25

Helliaca opened this issue Sep 17, 2022 · 5 comments
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@Helliaca
Copy link
Collaborator

Several users have reported the isengard tower messing up their screen when zooming in on it.

So far I have failed to replicate this issue.

@Helliaca Helliaca added bug Something isn't working help wanted Extra attention is needed labels Sep 17, 2022
@Helliaca
Copy link
Collaborator Author

UPDATE:

One of the people this bug happens to has given us the following info:

  • They use a Mac M1 GPU
  • This is what it looks like if you zoom out too far:
    image
  • This is at half zoom:
    image
  • This is when you draw a battle-plan:
    image
  • The regular ambient object models AND unit mdoels do not appear AT ALL:
    image
  • Changing graphics settings has no effect.

@Helliaca
Copy link
Collaborator Author

Deductions:

  • The first picture shows Mt. Doom with the pink color, which implies that our custom pdxmesh shader is not being used. Either way, it does not seem to be a shader-problem in the first place, as we ONLY change the fragment shader.
  • Our Barad-dur and Mt. Doom ambient objects have no scale defined, could this be the problem? Idk, as all three images above appear to show Orthanc, which DOES have a scale defined.
  • Unit models also not being shown, implies that there is some issue with our models in general when used on Mac M1's.

@Helliaca
Copy link
Collaborator Author

Helliaca commented Oct 30, 2022

Next step:

One possible fix would be to normalize the scale of the models to (1,1,1). This should be easy enough for the ambient objects, but not so much for the unit models.

I will go ahead with this and see if the problems persist.

Another option:
Try and set the scale of the ambient objects to 1 and see if we get similar images to those sent to us.

We should avoid adding more custom models until this issue is resolved.

@Helliaca Helliaca pinned this issue Oct 30, 2022
@Helliaca
Copy link
Collaborator Author

Another idea: Try changing the renderers in the launcher settings (opengl, directx...)

@Helliaca
Copy link
Collaborator Author

UPDATE: This may or may not have been fixed as of here

Marking this as fixed, if it comes up again I'll bring it back

@Helliaca Helliaca unpinned this issue Dec 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant