Cool VL Viewer forum

Henri, sorry to bug you with this, but I am experiencing something weird with v1.32.2.0 and the mirror drop down in preferences.

My Initial drop down setting: none (renderHeroProbeResLevel = 0 )

When I log on I have a significantly lower than usual FPS, and flipping the drop down to typically 1024 and back to none for a brief moment gives me a much higher FPS again (the normal to me).
Same behaviour every time I logon, sometimes I notice it at once, some times a bit later (depending on the surroundings of course), the momentary flip always makes things smooth again.

Log from current (running) session attached. Not that I think it tells much, no crash no on-screen error.
An yes old graphic driver I know, but it's the distro-supplied one.

The fact that just changing drop down values back and forth cures it and makes the viewer run smoothly is a bit of a mystery for me, as the situation does not return to the former state. Something obviously changes with the "turning it on and off again" and have impact on the viewer FPS in the end.
Any idea what's up?

(I did not notice anything odd with 1.32.1.9, so this looks like it turned up with the new dropdown as far as I can tell.
I can try the 1.32.1.9 version again if you think it helps. I have the install file left in my downloads.)

When you switch the renderer settings, shaders are recompiled, vertex and target buffers are reallocated, etc, and they can sometimes be allocated in RAM if the VRAM is full at this moment, thus the fps rate slow down...

There are also "VRAM leaks" happening when switching PBR on/off, and I so far could not find out from where it comes.

This is on my ToDo list... but there are so many bugs in PBR (LL's code), that you can expect it to stay flacky for a loooong while...

OK, I was just surprised it always (as in reproducible) seems to start slow, then after a switch (recompile as you put it) always continues to run smooth and fast for me.
Same thing every day. And that is what makes me confused about it, I totally get that the code is buggy and there are some possible leaks, but that should go the other way shouldn't it? Degrade over time? I see the opposite really.

Anyway, it's a manageable nuisance with a working workaround for me, I will blame it on LL for now unless you have a better idea.
And despite all the LL bugs, PBR rendering mode works well for me, good work you did there (with all bugs in mind)

Note that mirrors are still very much in "beta state" (well, the whole PBR shebang is pretty much still of beta quality too, but it is even worst with mirrors).

I do NOT recommend enabling mirrors by default: for a start, they will eat up a shitload of VRAM, even when there is no mirror around. This is because they use a pre-allocated set of three "cubemap arrays", each cube bearing 6 faces with the resolution of the mirror... And for each face, there are as many "mips" (sized down textures) as the power of two of the mirror size (i.e. 2048 = 2^11 = 11 mips) !