[Zaralot]

When deleting an object. I presume a WMO of sorts the frustrum check still seems to be in place here. The chunks behind the object still seem to dissapear despite the object clearly being deleted. Does anyone have a remedy for this? In the screenshot there use to be a wall here.

 

An idea I have... would I be expected to re-run mmaps, vmaps, etc with the patch implemented to fix this on the client side?

 

Here is video showing this in real time camera movement: https://i.gyazo.com/9422fd2e443fb35a41a4e48b9c96f43d.mp4

 

What I dont expect to see:

 

What I expect to see:

[Zaralot]

3 hours ago, wungasaurus said:

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.

This seems to only happen (at least to my knowldge) with this WMO, other ones haven't produced this result.

The WMO causing is 'valgarde_walls.wmo'  and exists in northrend_41_30 ADT.

 

I'm going to do some more testing to see if I can narrow it down some more.

[wungasaurus]

What version of the game is this on?

Does this happen with every WMO or only this one?

Does that WMO span multiple ADTs?

 

[Zaralot]

6 hours ago, wungasaurus said:

What version of the game is this on?

Does this happen with every WMO or only this one?

Does that WMO span multiple ADTs?

 

WotLK. This happens with every WMO. Does not span multiple ADT

 

I understand why it happens, it's a performance thing. All clients do it, if the chunks are entirely covered by an object, why render it? The problem is I think that mapping is not removed by noggit when the object is deleted. (similar to shadow map) and was wondering if anyone else has experienced this issue.

[wungasaurus]

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

[Zaralot]

40 minutes ago, wungasaurus said:

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

Sure thing will do.

Ill try to be as descriptive as possible. Now, I don't recall this issue happening beforehand when I use noggit SDL. So I'm going to test a few different versions to double check and see. It is not the first time I've modded this ADT and this WMO. And I don't recall this issue at all, then again I may have just not noticed it.

[wungasaurus]

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.