Vanilla - Very Vanilla MQ (Live Servers) (8 Viewers) 3.1.52471.11

[Turaj Steelfist]

This is not a crashing issue or anything and after spending about 15 mins looking at these posts I did not see anything related. Is portal setter working as intended in Next? Mine sets the portal just fine, but it is slower than molasses in subzero weather. The portal setter in VV was like warp 9.2 compared to the new version.

 

[Knightly]

I haven’t had any issues with it, but admittedly I haven’t used it since the UI change. Still, that shouldn’t have impacted anything. What part is slow?

 

[Sic]

This is not a crashing issue or anything and after spending about 15 mins looking at these posts I did not see anything related. Is portal setter working as intended in Next? Mine sets the portal just fine, but it is slower than molasses in subzero weather. The portal setter in VV was like warp 9.2 compared to the new version.

yup it is working as expected.

knightly changed the speed for next to have a 1s delay between doing stuff.

it isn't that it is slow. it is just that the old mq2 version would spam try and hand the mage the item 500 times before he accepted it

I considered putting an option in it to disable that 1s wait because *someone* was complaining about it being slow (cwtn), but i showed him the old one just spammed stuff at super speed and the new one is smarter about it, and it really isn't THAT much different.

 

[Knightly]

That crazy Knightly.

 

[Turaj Steelfist]

Ok thanks Sic

Knightly the delay is noticeable. I will just learn to be patient and go watch Netflix when I use it. Just kidding I love the the thing knightly if you made this thing you are my new 2nd best friend. I hate trying to remember which item to buy to go somewhere.

 

[Sic]

That crazy Knightly.

the portal mage guy is very grateful he's not getting smacked in the face with the stone over and over and over again until he takes it

 

[Sic]

I did a video when i did the imgui updates just before xpac came out.

you can see here

you can scroll forward to like 3:38 to see the speed

 

[ASmith50]

Unable to launch MQNext live when I have MQNext test running, not sure if that is by design or not.

 

[Cannonballdex]

Unable to launch MQNext live when I have MQNext test running, not sure if that is by design or not.

Using two separate installs?

 

[ASmith50]

Using two separate installs?

Yes, test from non launcher and live from the launcher

 

[Knightly]

Yes, test from non launcher and live from the launcher

Thanks for the reminder, in your MacroQuest.ini for Test change the window names for the tray util. I need to add it to our build scripts to change this on the default for test.

 

[piattnd]

Since changing over to the new mqnext software, I seem to be having random issues where EQ instances will get hung/stop responding at logout (after char select and going back to server select, locks here). Anyone else seen that issue?

 

[Coop]

I switched over to mqnext and have used it for a couple of weeks without problems. I updated it today and it told me access to the path c:\users\name\appdata\local\application data is denied but said it was installed. It seems like it's having problems seeing where the new location is for mq2. It doesn't seem to like where I put it or something. It keeps getting hungup unpacking files 238/239 and then gives me that error message....any ideas?

 

[Cannonballdex]

Anyone else see this message in game?

 

[hellfyre]

I personally hate and ignore that message as long as possible.

 

[durango773]

slow movements, you dont want to attract its attention..

 

[Knightly]

An hour after the post above mine, brainiac had already updated.

 

[Robban]

Anyone else see this message in game?

overseer fix

 

[piattnd]

Getting a crash on the latest version if I move/resize the EQ window. Is this where I post that bug or is there a different place I should put this? This is using MQNext.

 

[Knightly]

Give us a crash id to work off of, you can post the bug here: https://gitlab.com/macroquest/next/mqnext/-/issues but we're going to need a Crash ID regardless. I did see a bunch of Nahimic OSD crashes earlier, so if that's you, check your OSD software.

 

[piattnd]

Done: https://gitlab.com/macroquest/next/mqnext/-/issues/441

 

[avolonsummers]

Hi All, I have been struggling with my eqclient crashing whenever I start my group autologin via MQNext. Everything is updated to latest. When the autologin script is executed and my chars are at the login part it throws the following error: Error - A timeout occurred, then the autologin script continues to try until the character finally logins after like several tries.

When zoning into a zone out of my 6 characters usually 1 or 2 characters will have their clients crash. I will have to go into my task manager end task each client and relaunch, then I run into that A timeout occurred. This is extremely painful. I have no idea how to fix it.

I have deleted all of my character ini files and eqclient.ini and other system files and revalidated it. That didn't help at all. Anyone else running into this issue?

Here are the logs that I could find:
D 2022-01-10 08:11:52.086345 [MQ2] Logging Initialized
I 2022-01-10 08:11:55.065594 [MQ2] Starting NamedPipeClient thread for \\.\pipe\mqpipe
I 2022-01-10 08:11:55.074867 [MQ2] Toggle console keybind: ctrl+`
I 2022-01-10 08:11:55.082045 [MQ2] Connected to named pipe server.
D 2022-01-10 08:11:55.082084 [MQ2] Created PipeConnection: connectionId=1 pid=5256
D 2022-01-10 08:11:55.160452 [MQ2] Initializing module: FrameLimiter
D 2022-01-10 08:11:55.161194 [MQ2] Initializing module: DeveloperTools
D 2022-01-10 08:11:55.161904 [MQ2] Initializing module: Windows
D 2022-01-10 08:11:55.162910 [MQ2] Initializing module: ImGuiAPI
D 2022-01-10 08:11:55.163100 [MQ2] Initializing module: Spells
D 2022-01-10 08:11:55.163115 [MQ2] Initializing module: DataAPI
D 2022-01-10 08:11:55.163125 [MQ2] Initializing module: GroundSpawns
D 2022-01-10 08:11:55.163136 [MQ2] Initializing module: Spawns
D 2022-01-10 08:11:55.308402 [MQ2] Initializing module: Items
I 2022-01-10 08:11:55.381853 [MQ2] IDirect3DDevice9::EndScene: TestCooperativeLevel was successful, reacquiring device.
D 2022-01-10 08:11:55.381972 [MQ2] MQ2Overlay: InvalidateDeviceObjects
D 2022-01-10 08:11:55.381982 [MQ2] MQ2Overlay: CreateDeviceObjects
I 2022-01-10 08:11:55.394221 [MQ2] Received crashpad pipe name: \\.\pipe\crashpad_8344_BIBTFZHETBNNMEXS
I 2022-01-10 08:11:55.394479 [MQ2] Enabling shared crash reporter. Crash report guid: 2da9d7a8-b6af-4650-9a7a-74bd60993172
D 2022-01-10 08:11:55.394649 [MQ2] Launcher process ID: 8344
I 2022-01-10 08:17:05.407316 [MQ2] IDirect3DDevice9::Reset hook: device instance is the acquired device.
D 2022-01-10 08:17:05.407353 [MQ2] MQ2Overlay: InvalidateDeviceObjects
I 2022-01-10 08:17:14.213257 [MQ2] IDirect3DDevice9::EndScene: TestCooperativeLevel was successful, reacquiring device.
D 2022-01-10 08:17:14.213317 [MQ2] MQ2Overlay: CreateDeviceObjects
I 2022-01-10 08:17:21.595743 [MQ2] MQ2Overlay: Resetting overlay
D 2022-01-10 08:17:21.595769 [MQ2] MQ2Overlay: InvalidateDeviceObjects
I 2022-01-10 08:17:22.922894 [MQ2] IDirect3DDevice9::EndScene: TestCooperativeLevel was successful, reacquiring device.
D 2022-01-10 08:17:22.922990 [MQ2] MQ2Overlay: InvalidateDeviceObjects
D 2022-01-10 08:17:22.923006 [MQ2] MQ2Overlay: CreateDeviceObjects
I 2022-01-10 08:18:24.849654 [MQ2] MQ2Overlay: Resetting overlay
D 2022-01-10 08:18:24.849681 [MQ2] MQ2Overlay: InvalidateDeviceObjects
I 2022-01-10 08:18:25.053360 [MQ2] IDirect3DDevice9::EndScene: TestCooperativeLevel was successful, reacquiring device.
D 2022-01-10 08:18:25.053401 [MQ2] MQ2Overlay: InvalidateDeviceObjects
D 2022-01-10 08:18:25.053410 [MQ2] MQ2Overlay: CreateDeviceObjects
I 2022-01-10 08:18:30.598213 [MQ2] IDirect3DDevice9::Reset hook: device instance is the acquired device.
D 2022-01-10 08:18:30.598292 [MQ2] MQ2Overlay: InvalidateDeviceObjects
I 2022-01-10 08:18:30.748771 [MQ2] MQ2Overlay: Resetting overlay
I 2022-01-10 08:18:31.829576 [MQ2] IDirect3DDevice9::EndScene: TestCooperativeLevel was successful, reacquiring device.
D 2022-01-10 08:18:31.829633 [MQ2] MQ2Overlay: InvalidateDeviceObjects
D 2022-01-10 08:18:31.829643 [MQ2] MQ2Overlay: CreateDeviceObjects

 

[Cannonballdex]

Hi All, I have been struggling with my eqclient crashing whenever I start my group autologin via MQNext. Everything is updated to latest. When the autologin script is executed and my chars are at the login part it throws the following error: Error - A timeout occurred, then the autologin script continues to try until the character finally logins after like several tries.

When zoning into a zone out of my 6 characters usually 1 or 2 characters will have their clients crash. I will have to go into my task manager end task each client and relaunch, then I run into that A timeout occurred. This is extremely painful. I have no idea how to fix it.

I have deleted all of my character ini files and eqclient.ini and other system files and revalidated it. That didn't help at all. Anyone else running into this issue?

Here are the logs that I could find:
D 2022-01-10 08:11:52.086345 [MQ2] Logging Initialized
I 2022-01-10 08:11:55.065594 [MQ2] Starting NamedPipeClient thread for \\.\pipe\mqpipe
I 2022-01-10 08:11:55.074867 [MQ2] Toggle console keybind: ctrl+`
I 2022-01-10 08:11:55.082045 [MQ2] Connected to named pipe server.
D 2022-01-10 08:11:55.082084 [MQ2] Created PipeConnection: connectionId=1 pid=5256
D 2022-01-10 08:11:55.160452 [MQ2] Initializing module: FrameLimiter
D 2022-01-10 08:11:55.161194 [MQ2] Initializing module: DeveloperTools
D 2022-01-10 08:11:55.161904 [MQ2] Initializing module: Windows
D 2022-01-10 08:11:55.162910 [MQ2] Initializing module: ImGuiAPI
D 2022-01-10 08:11:55.163100 [MQ2] Initializing module: Spells
D 2022-01-10 08:11:55.163115 [MQ2] Initializing module: DataAPI
D 2022-01-10 08:11:55.163125 [MQ2] Initializing module: GroundSpawns
D 2022-01-10 08:11:55.163136 [MQ2] Initializing module: Spawns
D 2022-01-10 08:11:55.308402 [MQ2] Initializing module: Items
I 2022-01-10 08:11:55.381853 [MQ2] IDirect3DDevice9::EndScene: TestCooperativeLevel was successful, reacquiring device.
D 2022-01-10 08:11:55.381972 [MQ2] MQ2Overlay: InvalidateDeviceObjects
D 2022-01-10 08:11:55.381982 [MQ2] MQ2Overlay: CreateDeviceObjects
I 2022-01-10 08:11:55.394221 [MQ2] Received crashpad pipe name: \\.\pipe\crashpad_8344_BIBTFZHETBNNMEXS
I 2022-01-10 08:11:55.394479 [MQ2] Enabling shared crash reporter. Crash report guid: 2da9d7a8-b6af-4650-9a7a-74bd60993172
D 2022-01-10 08:11:55.394649 [MQ2] Launcher process ID: 8344
I 2022-01-10 08:17:05.407316 [MQ2] IDirect3DDevice9::Reset hook: device instance is the acquired device.
D 2022-01-10 08:17:05.407353 [MQ2] MQ2Overlay: InvalidateDeviceObjects
I 2022-01-10 08:17:14.213257 [MQ2] IDirect3DDevice9::EndScene: TestCooperativeLevel was successful, reacquiring device.
D 2022-01-10 08:17:14.213317 [MQ2] MQ2Overlay: CreateDeviceObjects
I 2022-01-10 08:17:21.595743 [MQ2] MQ2Overlay: Resetting overlay
D 2022-01-10 08:17:21.595769 [MQ2] MQ2Overlay: InvalidateDeviceObjects
I 2022-01-10 08:17:22.922894 [MQ2] IDirect3DDevice9::EndScene: TestCooperativeLevel was successful, reacquiring device.
D 2022-01-10 08:17:22.922990 [MQ2] MQ2Overlay: InvalidateDeviceObjects
D 2022-01-10 08:17:22.923006 [MQ2] MQ2Overlay: CreateDeviceObjects
I 2022-01-10 08:18:24.849654 [MQ2] MQ2Overlay: Resetting overlay
D 2022-01-10 08:18:24.849681 [MQ2] MQ2Overlay: InvalidateDeviceObjects
I 2022-01-10 08:18:25.053360 [MQ2] IDirect3DDevice9::EndScene: TestCooperativeLevel was successful, reacquiring device.
D 2022-01-10 08:18:25.053401 [MQ2] MQ2Overlay: InvalidateDeviceObjects
D 2022-01-10 08:18:25.053410 [MQ2] MQ2Overlay: CreateDeviceObjects
I 2022-01-10 08:18:30.598213 [MQ2] IDirect3DDevice9::Reset hook: device instance is the acquired device.
D 2022-01-10 08:18:30.598292 [MQ2] MQ2Overlay: InvalidateDeviceObjects
I 2022-01-10 08:18:30.748771 [MQ2] MQ2Overlay: Resetting overlay
I 2022-01-10 08:18:31.829576 [MQ2] IDirect3DDevice9::EndScene: TestCooperativeLevel was successful, reacquiring device.
D 2022-01-10 08:18:31.829633 [MQ2] MQ2Overlay: InvalidateDeviceObjects
D 2022-01-10 08:18:31.829643 [MQ2] MQ2Overlay: CreateDeviceObjects

I have this happen on rare occasion , usually something about my video device failing. This is when I log in like 16 toons at one time.

 

[burdsjm]

I have this happen on rare occasion , usually something about my video device failing. This is when I log in like 16 toons at one time.

I had this happen as well. Someone told me to adjust the delay on the autologin and it rarely happens after that change.

 

[AmericanNero]

@avolonsummers That looks like a DirectX issue. Is your video card driver up to date?

Also, install this, if you haven't already. /ht Sic

DX9.0c Directx 9.0c June 2010 Redist (Windows 10 comes with a stripped-down version) https://www.microsoft.com/en-us/download/details.aspx?id=8109

 

[Knightly]

/ht Sic?

Is that...are you harm touching Sic?

 

[Sic]

/ht Sic?

Is that...are you harm touching Sic?

*Has been slain*

 

[avolonsummers]

@avolonsummers That looks like a DirectX issue. Is your video card driver up to date?

Also, install this, if you haven't already. /ht Sic

DX9.0c Directx 9.0c June 2010 Redist (Windows 10 comes with a stripped-down version) https://www.microsoft.com/en-us/download/details.aspx?id=8109

Hi there, thanks so much for the suggestion and link. I have installed it. I am assuming this will fix the client crashing issue when zoning in?

How do I go about adding the delay in autologin? Thanks.

 

[AmericanNero]

Hi there, thanks so much for the suggestion and link. I have installed it. I am assuming this will fix the client crashing issue when zoning in?

How do I go about adding the delay in autologin? Thanks.

I don't know anything about it. Here's where you can learn more. Hope all your issues are sorted out soon!

Release - AutoLogin (core plugin)

Welcome to the MQ2Autologin discussion thread!

www.redguides.com

 

[Lara]

I moved to Next a few weeks back and as far as I'm aware the following apply at this time;

Next is not the default VV build, so you need to start EQBC manually buy right clicking on MacroQuest2 in task bar and "Start EQBC Server." This will open an eqbc window EQBCS (EQ Box Chat Server) 1.5.

That EQBCS Window will have the line "Waiting for connections on port: 2112..."

As I then load my characters I receive Client connections in the EQBCS window and see my characters joining as normal.

The main difference at this time is in the VV Launcher you cannot tick a box to say, auto-fire-up EQBC when launching MQ.

Please note: This is NOT a first time setup EQBC guide. I already had eqbc running on standard VV, then moved to the Next build.

I've spent 10 hours trying to solve the same problem. Your solution worked. Thank you very much. I've tried everything else. As MQNEXT is now Live and the default in the Launcher, this problem should have been fixed already.
I'm grateful.

 

[ChatWithThisName]

I've spent 10 hours trying to solve the same problem. Your solution worked. Thank you very much. I've tried everything else. As MQNEXT is now Live and the default in the Launcher, this problem should have been fixed already.
I'm grateful.

The issue is resolved unless I'm misunderstanding what you feel the issue is. There is now a tick box in the launcher.

 

[dalalron]

I have been getting a fairly regular error upon loading my toons in. The message I get says:

Macroquest caught a crash
Version 3.0.0.0
Location mq::getcolorforchatcolor+0
(c:\users\daves\desktop\mq2\live\next\mq2main.dll+00225aFO)
crash id: not reported.

It won't load the toons. It has been happening fairly regularly lately. Usually I can get past it by running the EQ Patcher and then re installing new versions and re booting. Not working yet tongith. Please advise thanks.

Dalalron

 

[Sic]

I have been getting a fairly regular error upon loading my toons in. The message I get says:

Macroquest caught a crash
Version 3.0.0.0
Location mq::getcolorforchatcolor+0
(c:\users\daves\desktop\mq2\live\next\mq2main.dll+00225aFO)
crash id: not reported.

It won't load the toons. It has been happening fairly regularly lately. Usually I can get past it by running the EQ Patcher and then re installing new versions and re booting. Not working yet tongith. Please advise thanks.

Dalalron

well version 3.0.0.0 means you're self building, so only you would be able to check your dmp and see what is causing it

do you have something calling the getcolorforchatcolor?

also inb4 giving folks a stroke with mq2/live/next directory lol

it is possible you might have better luck posting an issue on the MacroQuest issue tracker with your specific issue since you're self-building > here < try to provide any surrounding context or custom stuff etc, or a call stack from a dmp

 

[Zebadiah]

Look in taskmanager and see if in the background processes that you don't have any eqgame.exe in there...

Zeb

 

[dalalron]

Thanks guys.

Sic not sure what you mean by "self building". My tech skills are very basic and no way I set anything up myself other than what comes in the downloads. again on the calling of getforchatcolor I don't even know how to look for that. I will try your link to the specific issue tracker. Love your videos btw!

Zeb I did check the processes and the only thing that was running that would apply was Redguides and EQBC

 

[Sic]

Thanks guys.

Sic not sure what you mean by "self building". My tech skills are very basic and no way I set anything up myself other than what comes in the downloads. again on the calling of getforchatcolor I don't even know how to look for that. I will try your link to the specific issue tracker. Love your videos btw!

Zeb I did check the processes and the only thing that was running that would apply was Redguides and EQBC

are you self compiling?

your build says version 3.0.0.0 which is what build number you get if you self-compile macroquest

otherwise you should see something like 3.0.0.298 (or maybe not now RG is building?) @Knightly @Redbot

 

[Redbot]

Logs show they're downloading Very Vanilla, so it's a current RG build. Knightly had something in his script to modify build number that I've yet to introduce in ours.

 

[BrianGragg]

Logs show they're downloading Very Vanilla, so it's a current RG build. Knightly had something in his script to modify build number that I've yet to introduce in ours.

You should set the build number to 242. Knightly / Brainiac will appreciate it!

 

[dalalron]

Yes all I have been doing is downloading Very Vanilla and updating as necessary. . I don't even know what self compiling means let alone how to do it. I make very, very few modifications to anything.

 

[Sic]

Yes all I have been doing is downloading Very Vanilla and updating as necessary. . I don't even know what self compiling means let alone how to do it. I make very, very few modifications to anything.

cool thanks for the confirmation. this means we need to update the RG build to put a version so the crash reporting can happen - the 3.0.0.0 is supposed to be the " "dev build" version.

nothing you did wrong or anything