Question - Toons Frozen after Locking on MQ, but not when MQ is not loaded

[mb4xy3]

I had a lock on my toons / PC, so i rebooted with them all logged in. I've been trying to log my toons back in and am freezing up every single time they try to get to the actual zone they are camped in. They oad up like normal, boot out the existing toon in the world, show my toon on char select screen, but freeze when trying to load the zone. My toons are spread across a couple different zones now, so it is not a zone issue.

I have rebooted several times, updated redguides, etc.

I can log in on a toon using EQ's launchpad just fine, but the moment I start MQ2 and it injects into the session, the toon freezes. And, my fans start screaming on my PC and never stop. I'm trying to get one toon of my 36 logged in for testing now, and am experiencing the issue on all of them.

What are some troubleshooting steps i can do?

 

[Sic]

I would start by ensuring you aren't running extra 3rd party overlays - nahimic, afterburner, overwolf, nvidia overlay, xbox overlay, discord overlay, etc.

then i could go in my macroquest.ini and turn all my plugins to =0 (you'll want autologin if you plan on using that right away) and under the developer console and turn them all to =0 as well intent is to narrow it down in case you have a conflict that can be pinpointed so you can avoid it while you

 

[mb4xy3]

Thanks Sic - i'll start with the macroquest.ini file. The other overlays I don't have / disable pretty much everything on boot.

 

[Sic]

Thanks Sic - i'll start with the macroquest.ini file. The other overlays I don't have / disable pretty much everything on boot.

i definitely believe that - just consider checking. too often folks that are "100% sure they don't have conflicts" end up having conflicts and unsure how they got turned on

 

[mb4xy3]

Oh that wonderful mq2react file was the cause. I didn't have a tab in the correct place and was causing a crash, ugh. Thanks, all good now.

 

[Sic]

Oh that wonderful mq2react file was the cause. I didn't have a tab in the correct place and was causing a crash, ugh. Thanks, all good now.

woot! glad you got it sorted.

fwiw there are some problems with react and i (and many others) would strongly recommend using LEM, or individual Lua scripts instead of reacts