I keep getting spammed like crazy with this Opel GL message:
OpenGL debug message, id=1280, source=API, type=ERROR, severity=HIGH, message=Error has been generated. GL error GL_INVALID_ENUM in (null): (ID: 173538523) Generic error
And this is causing quite a headache. In MC versions 1.14 and above, when it's just about to load the main menu, the "Minecraft Game Output" gets barraged with that error. And IDK why it's doing it, and how to fix it. I uninstalled and reinstalled the game several times, I updated my graphics drivers last night, and I've run Malware scans. It all worked as a temporary fix, but it's back to spam again after a while. Java is up to date. I removed my resource packs. It still gave the error. Not to mention, this blows my CPU up to max, cause it spams it every frame in-game, and quite often, just by being in the main menu, discord ends up losing connection/crashes altogether. And it doesn't matter if I have Optifine or not. This issue started out of the blue on the 23rd. I think there's something wrong, but IDK. Because all the help I've gotten only fixes it temporarily. I hope someone helps me get a permanent fix to this.
Attachments
Comments 19
Doesn't quite match. Similar, but not an exact match. Only the **OpenGL debug message, id=1280, source=API, type=ERROR, severity=HIGH, message part matches, then mine has an extra set of words before the GL_INVALID_ENUM part.
I was running Pure unmodified Vanilla 1.14 through 1.17, the latest versions of each, and while In the main menu, I saw the log spam.
Update:
I think it's been fixed as It was a JAVA error somehow causing it.
I'll keep looking out for a bit if this comes back.
Can concur, OpenGL spam is happening due to the Overwolf client, likely due to a bug in the FTBA/Curseforge Overwolf app.
I'm having this in 1.20.1 with Fabric loader, so... This is not related directly to Overwolf. Got Intel Arc GA and their current official drivers.
@brezik.ad is it still an issue in 1.20.6 vanilla? 1.20.1 has been released almost a year ago so some things might have been changed since then.
Hm, same error as MC-228532, does that match your issue?