• You've discovered RedGuides, an EverQuest multi-boxing and scripting community 🧙‍♀️⚙️. We want you to play several EQ characters at once, come join us and say hello! 👋

  • A TLP without truebox has thawed (Very Vanilla ready)
    Frostreaver

Problem - MQ2Nav crashes EQ in certain zones, and only on one pc.

rebeis

New member
Joined
Apr 15, 2019
RedCents
40¢
It tends to happen in the open world zones, that are massive large, in my case burning woods and dreadlands for example.

I have tested various setups, from unloading the plugin, rebuilding the mesh in various different sizes, without any success. If i delete zone.navmesh file, dreadlands.navmesh as an example i wont crash, obviously cant navigate either.

The odd thing, i have a laptop next me with zero issues, It just works with mq2nav loaded. so im pretty sure there isnt anything wrong with mq2nav.
The two pc's are different hardware, so im guessing its something driver related, sound card, gfx whatever.


If anyone with more knowledge than myself would be so kind and maybe pinpoint why my EQ is crashing, buyt just that one pc.
I have a made a minidump using windbg where i load MQ2Nav
M2Nav Minidump Crash

And before anyone mentions it, I have reinstalled Windows, EQ and MacroQuest from scratch too.
 
I have tried different meshes from various sources, the working laptop meshes are a actually a copy from the crashing pc.
Good suggestion however :)

I'm more or less certain its more of hardware / driver issue than mq2nav or meshes, just no idea where to look.
As sidenote, also testet with affinity, since the main pc has a heapload more cores than laptop.
 
i've been having crash problems just loading into game from char select if i try to load my 6 box in at once i might get 2-3 to load into world and the others just crash, sent mule my dmp files but its only been since the last patch
 
So you just email eqmule@.. with attachments or ?
Well - particularly and especially since this is on one computer and not the other I would ensure that the computer it is crashing on is fully patched/updated - this includes windows updates, video drivers, and very vanilla before sending your dumps to mule
 
Indeed, everything is fresh installed and updated.

As i mentioned earlier, even windows is newly installed, bit extreme i know.. but running into dead ends where ever i look.
 
Indeed, everything is fresh installed and updated.

As i mentioned earlier, even windows is newly installed, bit extreme i know.. but running into dead ends where ever i look.
I help dozens of people a week - the few times that I haven't mentioned things like updating because someone says in their post that they updated, 50% of the time they aren't actually fully updated and we spend hours trying to fix something that would have been fixed if I had just mentioned it before. Sometimes people forget to update something simple like video drivers - or ensure you have direct X versions updated correctly (EQ needs directX 9.0c which doesn't naturally come now etc) so forgive me =p

Last week I remoted into someone's PC to try and help them out - turns out they were using a windows 7 release candidate install from like 2007(or 09 i forget now), it had *never* been patched/updated and was so old windows update didn't work because it was a RC and not an authorized version - because of this video drivers and everything else on the machine hadn't been updated in literally years :(

But if everything is patched, and such - send the nav dump file to @brainiac or post your issue at his github

Hopefully we can get you back and fixed up real quick
 
It's also helpful to know under what conditions you crash. An easy find triggered crash is different from a macro triggered crash, for example. Were you doing anything in particular when it crashed or does it seem random?
 
@Knightly It (only) happens on zone in, with or without macro running, mostly i can also reproduce by unloading and reloading mq2nav
@brainiac Yes, mq2map is loaded (i have tested with bare minimum, but mq2map has always been loaded. (i would be lost without ;o )
 
Steps to reproduce are very good. Since unloading and loading nav is probably faster than zoning, under that test how frequently does it happen?
 
I think 90%'ish i will crash when entering Dreadlands, mostly i have tested from Burning Woods to Dreadlands and vice versa.
its not garantied i will crash, it happens the odd one time where it just works.

Zoning doesn't take that long hehe, not compared having to log back in, sometimes waiting for toon to time out.
 
Problem - MQ2Nav crashes EQ in certain zones, and only on one pc.

Users who are viewing this thread

Back
Top
Cart