wungasaurus

I don’t have a link to any Noggit version since I never realeased one. I have seen such links in the past on this site so they do exist. The repository is at https://bitbucket.org/berndloerwald/noggit3/.

I am told that this stuff is fixed in new versions of noggit. Try updating please.

If it is over exactly one mcnk and the m2 header bounding box values are correct, but it is not in mcrf, please report a noggit issue.

0xc000007b can be pretty much everything and it is impossible to debug without additional information. Given what you said you likely have uninstalled the MSVC++ runtime. To actually find out what it wrong, look in Windows log files, or download process monitor, filter for noggit.exe, start noggit.exe, and check for any error of loading images. That will likely tell you the missing or broken file.

- the camera bug is a broken MFBO chunk. Just removing that should fix the issue. - the bad culling I don’t know, sorry. Usually that happens if the model spans multiple chunks and is not referenced in all of them. Try it being exactly in one mcnk to verify that not being the issue.

Noggit will _never_ require you to download any .NET framework.

Have you tried asking them on how they do it or look at what they do?

There have been no changes needed to cascexplorer between 7.3.5 and 8.0?!

What part of it does not work? What is the error?

@Skarn Check the linked thread, 0x007B31F8-read-0x10 is ADT.mcnk.low_quality_texture_map, not WMO related.

http://www.modcraft.io/index.php?topic=2971.0

tbh, this really shouldn't happen. in wotlk there is no culling information other than the wmo being referenced. since it isn't rendered, it isn't referenced. that's why I asked about version and if it happens for everything. there are some hardcoded occluders, so I wasn't sure if this is one. if it does not happen in a different version of noggit, please attach the adt for that version too.

Please report the issue on https://bitbucket.org/berndloerwald/noggit3/issues/new. Be sure to include a before and after version of your ADT.

What version of the game is this on? Does this happen with every WMO or only this one? Does that WMO span multiple ADTs?

everyone but modders, I guess?

What?

Don’t rename anything, open the first file in zip/rar, click extract. This has been how large files are distributed for decades, and is not modding related at all. https://www.techwalla.com/articles/how-to-extract-split-zip-files

wmos and models added to the client _can't_ have an implication seen in the worldserver log. If you remove all changed files, does this really no longer happen? what files _did_ you change? did you try taking away half of the files, look if it still happens, and if not, take away the other half instead, … and iterate until you have the one file causing it?

Yes. Or you just fix the references by letting noggit rewrite them.

The mechastrider is a different issue. Doodads spawned on terrain are culled for performance. To do so, the client checks which MCNK is visible, and then looks in the visible chunks which models are in it. If you replace a model with one with a different bounding box, this information is incorrect. In the case of lamp post → huge as fuck thing, it will flicker out of existence once you don’t look at the exact spot the lamp post was.

Can't see anything obviously wrong. Only see that azcrater is lowercase in list file and "Azcrater" in trs. No idea if that makes a difference. It shouldn't. Also, are you sure you're using the right wmo group?

Can you do so again after restarting noggit?Is there any error in the log?What is your log?Does it happen with any model? Since you claim it depends on the map used, what happens if you copy all adts and replace them with empty adts? Does it still happen?