Problem - Returning player crashing with ISBoxer and MQ2 (1 Viewer)

[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

 

[Setra]

This is probably a terrible recommendation but stop using IsBoxer. It’s totally not needed. The CWTN plugins are much more advanced and can run your 6 man team smoothly. You can even use FrameRate limiter to cut back on CPU usage.

 

[Algar]

This is probably a terrible recommendation but stop using IsBoxer. It’s totally not needed. The CWTN plugins are much more advanced and can run your 6 man team smoothly. You can even use FrameRate limiter to cut back on CPU usage.

If he quit EQ he also wouldn't be having any of these issues.
He could also stop using MQ.

 

[Algar]

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 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

I hope that when you say "launchpad" you mean MQ autologin... security/detection tinfoil hat theories aside, using eq launchpad by default is asking for pain later (when you autopatch and mq isn't updated yet, and all of a sudden you can't use MQ because you installed an optional EQ patch.)

You say that nothing is running as admin, but I would absolutely check that in your process manager, and/or use the MQ debug console to help verify that (mq icon > right click > advanced). It wouldn't be the first time I've seen processes elevated where people believed they were not.

Some other thoughts:
I would turn ensure the new UI is turned off in EQ (causes many random issues, not likely related, but possible).
I gave Setra some flack, jokingly, but ensuring your frame limiter is set up in EQ is always sound advice.

When you say you can log in two accounts fine, is that via ISB, or not? If so, I would steer away from a conflict between the two, personally.

 

[Kallieboxer]

I hope that when you say "launchpad" you mean MQ autologin... security/detection tinfoil hat theories aside, using eq launchpad by default is asking for pain later (when you autopatch and mq isn't updated yet, and all of a sudden you can't use MQ because you installed an optional EQ patch.)

You say that nothing is running as admin, but I would absolutely check that in your process manager, and/or use the MQ debug console to help verify that (mq icon > right click > advanced). It wouldn't be the first time I've seen processes elevated where people believed they were not.

Some other thoughts:
I would turn ensure the new UI is turned off in EQ (causes many random issues, not likely related, but possible).
I gave Setra some flack, jokingly, but ensuring your frame limiter is set up in EQ is always sound advice.

When you say you can log in two accounts fine, is that via ISB, or not? If so, I would steer away from a conflict between the two, personally.

Thank you for your response.

I typically only use the EQ launchpad when I'm playing independently of MQ.

I ran the debug console and it does say Starting MacroQuest Loader (elevated).

Ive check ISB toolkit, Innerspace. RG launcher and EQgame.exe and all have run as admin not selected. (right click, properties, compatability tab)

I set up the frame limiter on the one account that i can log into separately, should i log into all 6 separately to set up limiter since i can't log in all at once?
I did turn off the new UI on each account and logged out/relogged in to verify it is deselected, no change.

Looking at the debug console, my crashes started after New Process detected: 1204

Thank you

 

[Algar]

Thank you for your response.

I typically only use the EQ launchpad when I'm playing independently of MQ.

I ran the debug console and it does say Starting MacroQuest Loader (elevated).

Ive check ISB toolkit, Innerspace. RG launcher and EQgame.exe and all have run as admin not selected. (right click, properties, compatability tab)

I set up the frame limiter on the one account that i can log into separately, should i log into all 6 separately to set up limiter since i can't log in all at once?
I did turn off the new UI on each account and logged out/relogged in to verify it is deselected, no change.

Looking at the debug console, my crashes started after New Process detected: 1204

Thank you

If its started elevated, thats that, its running as admin... and other things may not be. Very easily a source of conflict.

I would try running the mq exe directly (The funny named exe/letter string exe in the MQ folder is what you want, I think edit: guess this doesn't matter.), instead of launching via RG launcher, as I have seen situations in which that launcher was elevating MQ... as the launcher itself was running as admin and MQ inherited it (or somesuch).

You could also look into using redfetch instead of RG launcher, it should not have the same issue.

Overall once you get them all running as not-admin/elevated, hopefully you'll have no more issue.

Basically the whole elevated/not-elevated thing boils down to... do you want a program that is actively scanning for the cheating that you are doing to have even more potential access to your system information? It just isn't a good practice, anywhere at all, but especially here.

 

[Kallieboxer]

If its started elevated, thats that, its running as admin... and other things may not be. Very easily a source of conflict.

I would try running the mq exe directly (The funny named exe/letter string exe in the MQ folder is what you want, I think), instead of launching via RG launcher, as I have seen situations in which that launcher was elevating MQ... as the launcher itself was running as admin and MQ inherited it (or somesuch).

You could also look into using redfetch instead of RG launcher, it should not have the same issue.

Overall once you get them all running as not-admin/elevated, hopefully you'll have no more issue.

Basically the whole elevated/not-elevated thing boils down to... do you want a program that is actively scanning for the cheating that you are doing to have even more potential access to your system information? It just isn't a good practice, anywhere at all, but especially here.

Who ever made the commands for red fetch is awesome. The dos prompt rpg style is great.

Both red fetch and vu5lubxC.exe give me this error when trying to run EQ through ISB (regular red Guides launcher didn't give me that error in debug console)

[2025-09-20 18:06:58.367] [MQ] [debug] [ProcessList.cpp:913] Injecting MQ into eqgame.exe: pid=44544
[2025-09-20 18:06:58.367] [MQ] [error] [ProcessList.cpp:923] Failed to open eqgame.exe with pid 44544: Access is denied.
[2025-09-20 18:06:58.367] [MQ] [error] [ProcessList.cpp:927] Failed to inject: Access Denied. This usually means that EQ is being launched as Administrator

However I only get that error when trying to run MQ and ISBoxer together.

ISBoxer loads 6 toons fine without MQ loaded (any option of loading)

EQ launchpad loads EQ fine with MQ, via redfetch or vu5lubxC.exe

 

[brainiac]

Means isboxer is running as admin too. Go into its settings and turn that off

Also you can run macroquest.exe. It’s not necessary the run the random name one.

 

[Kallieboxer]

Means isboxer is running as admin too. Go into its settings and turn that off

Also you can run macroquest.exe. It’s not necessary the run the random name one.

I was an idiot and when i turned off admin in isboxer via config tag i hit "apply" and not "reload" so of course it didnt actually apply.

However once i did hit reload, and its no longer running ISB in admin now i get this error spamming me


[2025-09-20 18:32:39.914] [MQ] [debug] [ProcessList.cpp:913] Injecting MQ into eqgame.exe: pid=24212
[2025-09-20 18:32:39.914] [MQ] [error] [ProcessList.cpp:956] Failed to get eqgame.exe base address for pid=24212: Only part of a ReadProcessMemory or WriteProcessMemory request was completed.
[2025-09-20 18:32:39.914] [MQ] [info] [ProcessList.cpp:1098] Scheduling injection for retry: pid=24212 retriesLeft=8
[2025-09-20 18:32:39.943] [MQ] [debug] [ProcessList.cpp:913] Injecting MQ into eqgame.exe: pid=24212
[2025-09-20 18:32:39.943] [MQ] [error] [ProcessList.cpp:923] Failed to open eqgame.exe with pid 24212: The parameter is incorrect.

I was only running the random name one as a test

 

[brainiac]

Couple questions:
1. Do you have UAC turned off? (Do you get elevation prompts when launching things as admin? Prompts means uac is on. You want uac on)
2. Are any of these programs running with any compatibility modes enabled? (Right click on the exe go to properties and click compatibility) check isboxer, macroquest and eqgame.exe
3. Is your EverQuest installation owned by admin and not writeable by normal users? (Easiest test is try to create a text file in the eq folder. It should create with no issue, delete it after)
4. Same question but for the macroquest folder
5. Bonus question: you’re not mixing 32bit and 64bit, right? Emu is 32bit live is 64bit

The problem here is there is some sort of permission problem and it’s causing errors trying to inject into the eq process

 

[Kallieboxer]

Couple questions:
1. Do you have UAC turned off? (Do you get elevation prompts when launching things as admin? Prompts means uac is on. You want uac on)
2. Are any of these programs running with any compatibility modes enabled? (Right click on the exe go to properties and click compatibility) check isboxer, macroquest and eqgame.exe
3. Is your EverQuest installation owned by admin and not writeable by normal users? (Easiest test is try to create a text file in the eq folder. It should create with no issue, delete it after)
4. Same question but for the macroquest folder
5. Bonus question: you’re not mixing 32bit and 64bit, right? Emu is 32bit live is 64bit

The problem here is there is some sort of permission problem and it’s causing errors trying to inject into the eq process

1. UAC is on the default setting of on.
2. i have checked all .exe files in EQ, MQnext and ISboxer for compatability and admin to be off
3 & 4. I can create new documents in both folders
5. im fairly certain everything is 64 bit.

This problem only happens with ISB and MQ together. I can run each separately. I can run multiple instances of EQ with MQ and alt tab. I just cant use ISBoxer to have the 6 screens on my display.

The debug console is still saying Elevated

 

[brainiac]

From the log it’s creating the process in such a way that mq doesn’t have the ability to open and inject into it.

Not sure why. What was the behavior when everything was elevated?

 

[Kallieboxer]

Here are the debug files from redfetch (with isb), redguides launcher (with isb) and redguides launcher without isb (only one character)

Redfetch crashed after logging into account, didn't make it to server select

Redguides crashed after logging into account, didn't make it to server select

Redguides without ISB entered just fine

Occasionally on the crashes I'll get the Reset Device () failed error. not every time.

 

[Sic]

i'm not sure i understand what you're saying here. I think there is some confusion

rg launcher / redfetch just PATCH/UPDATE MQ - they're not MQ itself. now if you have different folder's where you're installing mq and thus launching different MQs then there's that - or the difference between launching the MQ application via rg launcher vs redfetch

looking in the "redguides.txt"

Starting MacroQuest Loader (Elevated)

so you should check that the RG Launcher itself isn't set to admin - where brain mentioned earlier checking - otherwise it will launch mq as admin

your redfetch.txt

Starting MacroQuest Loader

your no isb.txt

[MacroQuest.cpp:1830] Starting MacroQuest Loader (Elevated). Built Wed Mar 12 21:53:32 2025

 

[Kallieboxer]

i'm not sure i understand what you're saying here. I think there is some confusion

rg launcher / redfetch just PATCH/UPDATE MQ - they're not MQ itself. now if you have different folder's where you're installing mq and thus launching different MQs then there's that - or the difference between launching the MQ application via rg launcher vs redfetch

looking in the "redguides.txt"

Starting MacroQuest Loader (Elevated)

so you should check that the RG Launcher itself isn't set to admin - where brain mentioned earlier checking - otherwise it will launch mq as admin

your redfetch.txt

Starting MacroQuest Loader

your no isb.txt

[MacroQuest.cpp:1830] Starting MacroQuest Loader (Elevated). Built Wed Mar 12 21:53:32 2025

I was only using redfetch as a test.

I typically start MQ via redguides launcher, then very vanilla and launch MQ with EQBCS, then i use ISB to log in.

I have three folders, MQNext, Redguides, and Redfetch (that i installed only today to test).

I have checked every .exe file in all folders, including everquest and innerspace and nothing is set to admin. i did use the isb configuration tool to verify that is set to no admin.

I am sorry for the confusion

 

[Algar]

I was only using redfetch as a test.

I typically start MQ via redguides launcher, then very vanilla and launch MQ with EQBCS, then i use ISB to log in.

I have three folders, MQNext, Redguides, and Redfetch (that i installed only today to test).

I have checked every .exe file in all folders, including everquest and innerspace and nothing is set to admin. i did use the isb configuration tool to verify that is set to no admin.

I am sorry for the confusion

Are you using EQ in fullscreen?

 

[Sic]

I was only using redfetch as a test.

I typically start MQ via redguides launcher, then very vanilla and launch MQ with EQBCS, then i use ISB to log in.

I have three folders, MQNext, Redguides, and Redfetch (that i installed only today to test).

I have checked every .exe file in all folders, including everquest and innerspace and nothing is set to admin. i did use the isb configuration tool to verify that is set to no admin.

I am sorry for the confusion

my point was that that one of those instances was, in fact, launching as admin (the Redguides - so i would check the rg launcher isn't launching as admin, which would then launch mq as admin).

Are you using EQ in fullscreen?

yeah im curious this too - a "reset device" crash can certainly happen with game going to fullscreen

 

[Kallieboxer]

Are you using EQ in fullscreen?

my point was that that one of those instances was, in fact, launching as admin (the Redguides - so i would check the rg launcher isn't launching as admin, which would then launch mq as admin).


yeah im curious this too - a "reset device" crash can certainly happen with game going to fullscreen

I understand that MQ is saying something is running it as admin. I have checked everything multiple times. I followed your link about checking things. I'm about ready to reformat the hard drive and start over.

I just logged in the 6 via isb (without mq) and they are in 3440 x 1200 windowed mode.

When i tried switching one to full screen, that individual of the 6 crashed

 

[Kallieboxer]

If i start MQ via redguides launcher and start eq via the EQ launcher it starts as windowed, i can switch back and forth to full screen with no problems.

If i try switching to full screen while using ISB that individual character crashes

 

[brainiac]

I don’t care about admin. I don’t care about redfetch/redguides etc. it’s crashing how, what do you see? Is there any dialog?

 

[Sic]

If i try switching to full screen while using ISB that individual character crashes

yes, that sounds like the problem

 

[brainiac]

yes, that sounds like the problem

Full screen usually crashes but I didn’t read that as the issue here since he said it was windowed

 

[Kallieboxer]

i can use ISB fine without MQ, but i can not use ISB with MQ

I can use MQ fine without ISB, but i can not use MQ with ISB.

I dont know why MQ is still showing as elevated, i have checked every .exe file associated with MQ, EQ, ISB

I am just trying to get the 6 characters on one display.

I do have two monitors, ISB is set to use display 1 with the 6 toons and not use display 2. this works fine without MQ running, but crashes when i load MQ

 

[Algar]

I understand that MQ is saying something is running it as admin. I have checked everything multiple times. I followed your link about checking things. I'm about ready to reformat the hard drive and start over.

I just logged in the 6 via isb (without mq) and they are in 3440 x 1200 windowed mode.

When i tried switching one to full screen, that individual of the 6 crashed

That was my point in bringing it up (that it can cause reset device crashes); I wasn't advising you to try full screen. Sorry for that.

The fact that you are still elevated when starting mq from the rg launcher is perhaps an issue; but it is obviously not the issue here. Let's not get too hung up on that.
You can just start the exe directly instead of using the rg launcher to start mq... or continue using redfetch.

I understand that you are frustrated... it is best to focus very hard on what brainiac is asking you.

 

[Kallieboxer]

I don’t care about admin. I don’t care about redfetch/redguides etc. it’s crashing how, what do you see? Is there any dialog?

After I log into the account (all 6 characters using ISB key repeater) it goes to loading screen, music plays in the background, and then before it goes to the server select screen all 6 toons crash. Just screens go black and they close out themselves.

All 6 toons are actually logged into the server, if I try logging in again shortly after I get the toon already logged in warning.

Sometimes the “reset device” error shows up, sometimes it doesn’t.

I’m sorry if I’m getting frustrated. I know you guys are trying to help and you guys do amazing things for this community.

 

[Algar]

I am also frustrated on your behalf, believe me. Certainly nothing to apologize for in my book. No nerd wants to spend saturday night troubleshooting the game instead of playing it watching mq play it for you.

 

[Kallieboxer]

I am also frustrated on your behalf, believe me. Certainly nothing to apologize for in my book. No nerd wants to spend saturday night troubleshooting the game instead of playing it watching mq play it for you.

When I came back I swore I wouldn’t use MQ for fear of being suspended again, but then I tried to set up my old way of manual boxing and said hell no haha.
Just the quality of life things make it worth the risk.
And MQ2 bard, that I’m dying to try

 

[brainiac]

What server are you connecting to?

I would also check for driver updates in the off chance that it is graphics related (I don’t think it is, but it has helped some people)

Doesn’t sound quite like a crash. There’s a lot of red herrings and noise in this thread and I’m trying to very methodically weed it out.

 

[Kallieboxer]

Drinal.

I don’t even get to the server select screen.

ISB loads up all 6, skips the EULA button, then it’s the account name and password.

I use ISB key repeated to enter same password for all 6.

It then goes to loading screen, but goes black and crashes before server select.

I can log into characters individually with MQ, without using ISB.

 

[Kallieboxer]

I have used ISB with these same toons and MQ on this server before.

The only things that changed were a larger monitor and new graphics card with duel screens.

When I came back I deleted MQ for fear of suspensions, but I quickly said that’s stupid. MQ makes the game fun.

So after I got ISB working again I reinstalled MQ and started having my issues.

 

[Sic]

Drinal.

I don’t even get to the server select screen.

ISB loads up all 6, skips the EULA button, then it’s the account name and password.

I use ISB key repeated to enter same password for all 6.

It then goes to loading screen, but goes black and crashes before server select.

I can log into characters individually with MQ, without using ISB.

Sidenote: dude, setup autologin lol.

Will also help with having a little delay before each toon logs in, which will help with ensuring EQ doesn't shit out and load defaults for eqclient

 

[Kallieboxer]

Sidenote: dude, setup autologin lol.

Will also help with having a little delay before each toon logs in, which will help with ensuring EQ doesn't shit out and load defaults for eqclient

Yeah that’s on my list for creature comfort.

I was thinking it might be better not to have it now while trying to figure out what is causing problems.

 

[Kallieboxer]

What server are you connecting to?

I would also check for driver updates in the off chance that it is graphics related (I don’t think it is, but it has helped some people)

Doesn’t sound quite like a crash. There’s a lot of red herrings and noise in this thread and I’m trying to very methodically weed it out.

Sorry I missed part of this.

I have updated graphics drivers.

I know there’s a ton of red herrings here.

I will try what ever you want and I am very grateful for the assistance.

 

[brainiac]

Other things to check are the dbg.txt in the eq dir. and macroquest log (not the launcher log) in the mq directory under logs.

Check logs/errors for any crash reports too

Check your macroquest.ini and disable all plugins to make sure it’s not an issue with a specific plugin

 

[Kallieboxer]

when loading EQ via ISB after MQ is running

in dbg.txt i got multiple errors of

[Sat Sep 20 22:18:11 2025]00053:*** ERROR: WorldAuthenticate. ??? UNKNOWN MESSAGE

I added the macroquest launcher log.

ill disable all plugins and re-run. i think all i have installed and up to date right now are bard,war,zerk,sham

(edit, whoops you said not the launcher log as i added it like an idiot lol)

 

[Redmonkey]

You mentioned you got a "reset device" error. That is currently a big problem with the last patch over on the game forums. It seems to be related to full screen etc

https://forums.everquest.com/index.php?threads/newest-patch-caused-more-issues.305513/page-3#post-4408805

 

[brainiac]

That’s odd.

What happens when you load mq after you are fully logged in?

Also what cpu do you have?

 

[brainiac]

when loading EQ via ISB after MQ is running

in dbg.txt i got multiple errors of

[Sat Sep 20 22:18:11 2025]00053:*** ERROR: WorldAuthenticate. ??? UNKNOWN MESSAGE

I added the macroquest launcher log.

ill disable all plugins and re-run. i think all i have installed and up to date right now are bard,war,zerk,sham

Want NOT the launcher log.

Nothing relating to render errors in the dbg log?

 

[Kallieboxer]

The macroquest logs were 6 identical entries to this except the ID numbers changed for the 6 different accounts.

PC is Intel i9-10900 @3.7 ghz with 32 gb ram

I couldnt find any errors assocaited with render in DBG.txt



D 2025-09-20 22:45:13.631828 [EQLib] Logging initialized
I 2025-09-20 22:45:13.631955 [EQLib] Initializing EQMain
I 2025-09-20 22:45:13.631983 [EQLib] Initializing EQGraphics
D 2025-09-20 22:45:13.640011 [MQ] Initializing Login Detours
D 2025-09-20 22:45:13.645532 [MQ] HookMemChecker - %satching
I 2025-09-20 22:45:13.668635 [MQ] Toggle console keybind: ctrl+`
D 2025-09-20 22:45:13.738076 [MQ] Initializing module: CrashHandler
D 2025-09-20 22:45:13.738124 [MQ] Initializing module: RenderDoc
D 2025-09-20 22:45:13.738145 [MQ] Initializing module: FrameLimiter
D 2025-09-20 22:45:13.739209 [MQ] Initializing module: InputAPI
D 2025-09-20 22:45:13.739369 [MQ] Initializing module: DeveloperTools
D 2025-09-20 22:45:13.741144 [MQ] Initializing module: Windows
D 2025-09-20 22:45:13.741578 [MQ] Initializing module: ImGuiAPI
D 2025-09-20 22:45:13.741798 [MQ] Initializing module: Spells
D 2025-09-20 22:45:13.741815 [MQ] Initializing module: DataAPI
D 2025-09-20 22:45:13.741825 [MQ] Initializing module: ActorAPI
D 2025-09-20 22:45:13.741834 [MQ] Initializing module: GroundSpawns
D 2025-09-20 22:45:13.741844 [MQ] Initializing module: Spawns
D 2025-09-20 22:45:13.765185 [MQ] Initializing module: Items
D 2025-09-20 22:45:13.765755 [MQ] Initializing module: PostOffice
I 2025-09-20 22:45:13.765792 [MQ] Starting NamedPipeClient thread for \\.\pipe\mqpipe
I 2025-09-20 22:45:13.766162 [MQ] Connected to named pipe server.
D 2025-09-20 22:45:13.766201 [MQ] Created PipeConnection: connectionId=1 pid=6820
D 2025-09-20 22:45:13.766221 [MQ] Connection to named pipe created, Sending process loaded message.
I 2025-09-20 22:45:13.771105 [MQ] MacroQuest Loaded.
I 2025-09-20 22:45:13.772100 [MQ] MQGraphicsEngineDX11::AcquireDevice: Device acquired.
D 2025-09-20 22:45:13.772198 [MQ] MQGraphicsEngine: CreateDeviceObjects
I 2025-09-20 22:45:13.786097 [MQ] Received crashpad pipe name: \\.\pipe\crashpad_52464_LEXBRWGZVAHRIRYL
I 2025-09-20 22:45:13.786654 [MQ] Enabling shared crash reporter. Crash report guid: 8ef4ca79-a000-4bf2-b411-6c131755f706
D 2025-09-20 22:45:13.794996 [MQ] Launcher process ID: 52464
I 2025-09-20 22:45:13.804905 [MQ] Got identification from 6820
I 2025-09-20 22:45:13.804951 [MQ] Got identification from 6820
I 2025-09-20 22:45:13.804962 [MQ] Got name-based identification from 52464: launcher
I 2025-09-20 22:45:28.828186 [MQ] Got identification from 53096
I 2025-09-20 22:45:43.875823 [MQ] Got identification from 52776
I 2025-09-20 22:45:58.990732 [MQ] Got identification from 53792
I 2025-09-20 22:46:14.005209 [MQ] Got identification from 49400
I 2025-09-20 22:46:24.136528 [MQ] Got identification from 55596
I 2025-09-20 22:46:49.588138 [MQ] MQGraphicsEngineDX11::AcquireDevice: Device acquired.
D 2025-09-20 22:46:49.588172 [MQ] MQGraphicsEngine: CreateDeviceObjects

 

[Kallieboxer]

logging in now without mq via isb, then to load mq and see what happens