Problem - Returning player crashing with ISBoxer and MQ2

[Kallieboxer]

Hello all, I'm returning after a few years break. I used to play 6 toons with ISBoxer for windows layout.

When I try to log in via ISBoxer (MQ2 already running) my game crashes after the server select screen, but the toons are all logged into the character select screen.

If I log in with one toon only via EQ launchpad (MQ2 already running) everything works fine.
If I log in via ISBoxer (without MQ2 running) all six toons log in fine.
If I log in two characters via launchpad (MQ2 already running) everything works fine. alt tab works fine

If I log in via ISBoxer without MQ2 running, and the load MQ2 after all 6 toons are in the game, everything crashes.

I did some searches and found these things helped others and tried them. but no luck.

updated graphics driver (GeForce RTX 3060)
disabled Nahimic
removed $ IgnoreFreeLibrary<mq2nav.dll> from layers registry.
EQ, redguides and ISBoxer are all not running as admin
Uninstalled and reinstalled ISBoxer and Red Guides.

The only changes from when I used to play and now are a larger monitor and newer graphics card. I have not uninstalled/reinstalled EQ.

EQ, Red Guides and ISBoxer are all on the same SSD drive.

Does anybody have any recommendations?

Thank you

 

[Kallieboxer]

i logged in via isb, all 6 toons were fine.

then i used redguides launcher to launch mq2. each screen just went away, no error message.

attached is the mq debug console

(added eq dbg.txt)

 

[brainiac]

i logged in via isb, all 6 toons were fine.

then i used redguides launcher to launch mq2. each screen just went away, no error message.

attached is the mq debug console

(added eq dbg.txt)

Did you load 6 of them or just one? Just test it with one…

Did you check for error dumps in mq logs/errors folder?

What cpu are you using?

I’m in Las Vegas this weekend, going to a show soon so I won’t be responding for much longer.

 

[Kallieboxer]

Did you load 6 of them or just one? Just test it with one…

Did you check for error dumps in mq logs/errors folder?

What cpu are you using?

I’m in Las Vegas this weekend, going to a show soon so I won’t be responding for much longer.

Enjoy your time in Vegas! It’s midnight here so I’ll do some more testing in the morning.

But for real, enjoy Vegas!

 

[B_I_G__D_A_D_D_Y]

I guess I never got the memo about running everything non-Elevated. I do the opposite, I run everything as Admin. (Bad security I know!)

I also run ISBoxer with 6 clients. I never, ever, run the EQ patcher except on patch day and only when both ISB and MQ are NOT running. Later I'll patch MQ using Redfetch, but never when any EQ clients are running in memory. I no longer use the Redguides launcher for anything. I quit out of Redfetch when it's done patching and updating.

After EQ and VV are patched I run ISB and log my team into the game fully. I mean with all 6 characters actually in the world. Then and only then, I use the Windows key and right-click on my MQ icon and run it as Admin. It will then load and inject just fine. (To get the icon in your Start Menu you navigate to the MQ folder and right-click on the obfuscated MQ executable name and choose to add a shortcut to the Start Menu.)

From what I'm reading I'm doing it wrong! but everything works fine for me. I'm running my teams in 1920x1080 mode with all 6 characters stacked on one monitor on a Win11 machine with an Intel i7 CPU and discrete AMD graphics. I have been seeing some of the Device Reset errors but again, from what I'm reading, that is some conflict from EQ's August patch and recent AMD drivers in conjunction with ISBoxer usage. I've read that it seems to have more impact on full screen usage but ISBoxer is set to use emulated full screen so the game should see it as Windowed. That's beyond my pay grade but I hope they work it out soon!

Temporarily until they fix the Device Reset I no longer use Quit from the Character Select screen. Instead I'll use /camp desktop so it skips Character and Server Select.

One bit of advice is to totally disable frame limiting in both ISBoxer and also in-game and use the VV MQ limiter. The VV one is way superior to either game or ISB. Another thing I'd try is to uninstall and then reinstall ISBoxer. Save your XML config file for later, but create a new ISBoxer configuration from scratch just for testing purposes. You can copy your saved XML back into ISBoxer later and just switch back to it and reload the configuration to InnerSpace. This would just be to potentially eliminate some old artifact in ISBoxer that is causing a conflict.