Chunk loader give an exit code 1

[Coralz]

when trying to launch the game I get and exit code one and I can't find any sort of crash report for it.

[Luis_ST]

Please post debug.log from the logs folder.

If you using CurseForge you need to enable the debug.log in the settings.

[Coralz]

Here you go

https://www.dropbox.com/s/3jkfqq8b2anmh8u/2022-08-14-1.log?dl=0

[Luis_ST]

This error is often an indication that the max fps are set to 0, edit the options.txt file in your game directory and change the maxFps value.

[warjort]

  Quote

[00:01:23] [Render thread/ERROR]: ########## GL ERROR ##########

[00:01:23] [Render thread/ERROR]: @ Render [00:01:23]

[Render thread/ERROR]: 65539: Invalid key -1

Expand  

Actually that GL ERROR seems to be a problem with misconfiguring key binds.

e.g. see this similar issue reported for quark https://github.com/VazkiiMods/Quark/issues/3793

Of course, it doesn't mean the current problem is caused by Quark, only that it points to badly configured key bindings (either by a mod or the user).

 

One thing to try would be backup your options.txt then delete it.

This will allow the key bindings to revert to their default configuration.

But it will do the same for all your other minecraft option settings as well.

[Coralz]

This didn't work it was already at 260 and I changed it to 550 same error

[Coralz]

  On 8/14/2022 at 7:37 PM, warjort said:

Actually that GL ERROR seems to be a problem with misconfiguring key binds.

e.g. see this similar issue reported for quark https://github.com/VazkiiMods/Quark/issues/3793

Of course, it doesn't mean the current problem is caused by Quark, only that it points to badly configured key bindings (either by a mod or the user).

 

One thing to try would be backup your options.txt then delete it.

This will allow the key bindings to revert to their default configuration.

But it will do the same for all your other minecraft option settings as well.

Expand  

Also tried this gave me the same error

[warjort]

Don't know then.

The log you posted isn't the logs/debug.log that was asked for.

And it doesn't contain any other error.

We don't even know if the GL ERROR is gone because you don't show an updated log.

[warjort]

You can also try posting the installer.log.txt to see if the minecraft launcher has recorded an error that is not shown in the log you posted?