Cool VL Viewer forum

In short: Not really a bug but a regression - you also mentioned some yo-yo effect again is back in the release notes of v1.30.2.34 - my "hint" is that root cause had been introduced in 1.30.2.28.

I realized from version 1.30.2.28 on that the texture decoder consumes more CPU power than before. I have 3 cores dedicated to texture decoder (CPU affinity) so i can see it very easily. In a crowded place (Peak Club / QOS club) > 45 persons it a) keeps cores much longer at 100% load at arrival and afterwards more load than versions before: When it settle i can see a little Yo-Yo effect again with the Bias in my case going back and forward between 5.00 and 4.75.

The behavior is still the same in all recent viewers (as of yesterdays 1.30.2.34), didn't change really much. I have fps after all stable reduced only by 10-20% thats not really much or noticable. But then more CPU is necessary for other tasks it leaves less "buffer".

I can say 1.30.2.27 was last good (at least for me). It has not the yo-yo effect after reached high Bias 5.0: discard bias starts to go down and continues. I have checked it by switching viewer same place.

A setting i have adjusted is "TextureUpdateBoostRatioPerDiscard" i use 0.5 instead of default 0.25
One addition: Threaded Cache reads isn't it, i have it enabled also in 1.30.2.27.

My config:
CPU: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (4256 MHz)
Memory: 32026MB
OS version: Linux-x86_64 v5.14.21-150400.24.88-default #1 SMP PREEMPT_DYNAMIC Thu Sep 21 12:45:42 UTC 2023 (2cab595)
Memory manager: jemalloc v5.3.1-20230829
Graphics: NVIDIA GEFORCE GTX 1070/PCIE/SSE2
OpenGL version: 4.6.0 NVIDIA 525.78.01
Detected VRAM: 8192MB
J2C decoder: OpenJPEG: 1.4.0.635f
Audio driver: FMOD Studio v2.02.17 (ALSA)
Networking backend: libcurl 7.47.0/OpenSSL 1.0.2u/zlib 1.2.13.zlib-ng
Browser plugin: Dullahan 1.13.1/CEF 116.0.12/Chromium 116.0.5845.96

That's a very interesting report, thank you !

Very helpful too, because identifying the exact version in which a problem appeared makes it easy to find the cause...

The one and only change in v1.30.2.28 that went in textures LOD determination was "Fixed a bug that caused some animated textures to stay blurry", and indeed, this is the culprit for this issue, the problem being that the case when the fix triggers (and indeed solves the blurry animated textures issue) also triggers for many other textures that are not animated (especially avatar attachments textures), causing them to load at way too high a resolution, in turn involving a large memory consumption and violent reloads when the fetcher finally reaches a 5.0 discard bias and returns to anything lower afterwards...

Fixed for next release. Here is the patch to apply to current sources:


But this is such a serious issue for venues with 20+ avatars or so, that I decided to publish new releases to fix this today !

New releases published, with this nasty bug fixed.