GGLoader - Major Control Loss Bug

[nightwish812]

GGLoader - Major Control Loss Bug

I see GGLoader being recommended pretty often on these forums but I think its critical to point out a major bug with it that has existed for years and without any update on being fixed. I'm hoping that the Bot devs see this post and prioritize fixing it since a lot of users are having the issue.

The Issue

A bug where the player loses control of their character for approximately 5-10 seconds. This happens about once every dungeon and in about every second raid pull. During these episodes, the character moves aimlessly, and no player inputs are possible.

This means that the character can simply walk into fire, off a cliff and die which is really detrimental to higher end content.

Hope this post is able to raise awareness of this issue in hopes of finding a resolution or update from the developers.

[0x41^4]

This is being fixed, but it doesn't happen as often as you say it does, nor has it happened for years.

Unless you're either an AMD user or you don't have the appropriate loader settings set, it should only happen once every few hours.

The best response to combat the bug is to simply stop trying to cast and move when it happens. Continuing to try and move or cast creates essentially a back-sequence that puts too much load on the loader and extends the freeze.

[nightwish812]

Originally Posted by 0x41^4

This is being fixed, but it doesn't happen as often as you say it does, nor has it happened for years.

Unless you're either an AMD user or you don't have the appropriate loader settings set, it should only happen once every few hours.

The best response to combat the bug is to simply stop trying to cast and move when it happens. Continuing to try and move or cast creates essentially a back-sequence that puts too much load on the loader and extends the freeze.

I've had it personally happen with the above frequency and I'm not on AMD. If you browse the GGL Discord (And CR Dev discords) you'll find several users that have mentioned the above bug as well.

Some posts on GGL Discord from browsing for 2 minutes:



What are the loader settings you're using to mitigate the issue?

[bohalk]

Originally Posted by 0x41^4

This is being fixed, but it doesn't happen as often as you say it does, nor has it happened for years.

Unless you're either an AMD user or you don't have the appropriate loader settings set, it should only happen once every few hours.

The best response to combat the bug is to simply stop trying to cast and move when it happens. Continuing to try and move or cast creates essentially a back-sequence that puts too much load on the loader and extends the freeze.

ggl is a shitshow and needs an urgent rewrite.