-
Notifications
You must be signed in to change notification settings - Fork 10
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
[1.18.2] Waypoint OpenGL Error 1282 #412
Comments
Optifine is causing tons of issues, but this will be fixed (probably, I still get OpenGL Error 1282 but not related to JM) in next release as Mysticdrew had found the potential issue. |
if you are able, come into our discord so I can give you a test version to see if it resolves your issues. |
This is a bug with optifine |
Pinning this issue. |
the bug seems related with the beacons they are stange in 1.18.2 |
I can confirm I am seeing this exact same issue. The moment I interact with any waypoints, I get glitching textures and opengl errors. I am also running JM and optifine 1.18.2 H7 |
I am having this too. OpenGL 1282 errors randomly pop out after I teleport through waypoints for a few times. |
Drop forge and optifine for fabric and an alternative like iris. Problem solved. |
This will be fixed in 5.9.0, I think I have the new texture engine issues resolved. |
JourneyMap Version:
journeymap-1.18.2-5.8.1beta2.jar
Forge Version:
forge-1.18.2-40.0.23
Describe the problem in repeatable steps:
Whenever I make, edit, or interact with any waypoints, I get tons of OpenGL Error 1282 in the chat, and usually after, it makes my textures glitch. This only happens when playing with Optifine (1.18.2 HD U H6 and 1.18.2 HD U H7 pre3). I did try multiple worlds and it kept happening, even with just Optifine and JourneyMap installed. The error itself doesn't happen when Optifine isn't installed.
The error only fixes itself once restarting Minecraft, closing and reopening a world doesn't fix it.
Relevant errors from .minecraft/journeymap/[journeymap.log]
The error from latest.log, repeated a ton of times;
latest.log
journeymap.log
The text was updated successfully, but these errors were encountered: