Cool VL Viewer forum

Resetting vertex buffers was the first i tried, it didn't help.

Just now I am on mainland and it happened again, not much different to private estates. Edit appearance, cancel editing appearance, camming out of the house where I am in, more than the half of objects vanished, even more on the neighbor sim. Surprisingly the sim ground is still there

What is strange however, is that you mention v1.26.24.18 as the last working version for you... v1.26.24.19 should work the same, since the changes were not already done in it !

Can you please confirm you do see the bug in v1.26.24.19 ?

I only kept v1.26.24.18, so I thought it started with v1.26.24.19. I will compile v1.26.24.19 and try if it happens for this version.

I checked now v1.26.24.19 and it starts with this version.

Definitely a different bug, then... Starting to suspect culling changes backported in v1.26.24.19 from Singularity... Will investigate.

Thank you

OK, I think I found the issue... It's about dynamic textures and how I thought LL had the old render target + FBO culling issue resolved (scoop: they did not) when I backported the EE renderer to the viewer (and part of the rendering fixes that came with it, in the Windlight renderer).

But what does it got to do with avatar appearance editing, will you ask ?... Good question !... And the answer is: local bakes and texture previews in the appearance editing floater *are* dynamic textures !...

Yeah, not quite obvious, was it ?... In any case, thanks to the narrowing of the bug introduction to the changes that were done between v1.26.24.18 and v1.26.24.19, I could (relatively) quickly find where the problem came from.

I'd gladly accept a confirmation, if you could apply the following patch to either v1.26.24.22 or v1.27.0.2 sources and compile the viewer:

That's it!

I applied the patch to v1.26.24.22 and tried especially the places where it happened always. I don't see this bug anymore.

Thanks a lot!

I have tested with OcclusionPauseDuration set to zero and can also confirm the patch corrects the issue for me (in v1.27.0.2).

Good... Next releases will have the fix. Case closed.