Problem - mq2nav Crashing Macroquest (EMU) in specific zones which happen to have large navmesh files

[piattnd]

So I seem to have narrowed this down to mq2nav and I believe the problem has to do with zones that have really large navmesh files.


To set some context:
- This is on an EMU server
- Zones confirmed having this issue are The Burning Woods (navmesh is 89.82MB) and The Warsliks Woods (navmesh is 83MB)
- Other zones in Kunark don't seem to have an issue so far. No zones in classic zones had issues (Kunark just opened today)
- I can zone into The Burning Woods and The Warsliks Woods if I turn off mq2nav before I zone in.
- If I /plugin load mq2nav while zoned into The Burning Woods or The Warsliks Woods, I crash immediately
- Macroquest Logs don't appear to have any error message
- I can load up Live Macroquest and Live EQ and zone into the zones in question without crashing.

Unfortunately, I'm not very knowledgeable when it comes to any limitations of navmesh sizes or how I could possibly generate them into smaller files. Anyone happen to have any thoughts?

 

[Redfrog]

Just to test it, have you deleted your current navmesh and redownloaded a fresh file? in the concept of corrupted file or something.

 

[piattnd]

Yeah, I tried going to https://mqmesh.com/kunark.php and grabbing those mesh files. I also tried regenerating the navmesh via the generator that ships with macroquest. Definitely struggles to function once the navmesh is fully generated (gets super choppy), but both the downloaded version and the generated version fail

 

[piattnd]

Just for kicks, I tried copying over the same files in my live Macroquest folder into my Emu Macroquest folder and confirmed I have the same issue.

 

[piattnd]

Just an update on this.

I deleted the navmesh files for the problematic zones and confirmed I no longer crash. I have begun the process of generating some very stripped-down navmesh files and have posted for suggestions in the MQ2Nav discussion page.