Cool VL Viewer forum

Hi Henri, I just updated to the Cool VL Viewer v1.26.6 (current stable branch with the v3.4 renderer) - 1.26.6.1
Prior to today, I had been using the Cool VL Viewer v1.26.4 (legacy stable branch with the v2.6 renderer).

I noticed that a fur sculpt and the corresponding fur texture (an alpha) that is made for the sculpt no longer appear the same as when I used the v2.6 renderer. In the past, the fur would appear "fluffy" and bright in the center without any hint of the texture bleeding onto the edges of the sculpt.
Today, when working with it and using the latest viewer, 1.26.6.1, I noticed the edges of the sculpt now appear to have an artifact of the texture along them.

I don't use the LL Official Viewer at all, so I am not sure if this is an issue common to both viewers (and apologize in advance if it is and if I should be reporting it to LL through the JIRAs).
Unfortunately, my screenshots are too big to be uploaded here. I am more than happy to send you a shot inworld (or show you when you have a moment).
I hope you are able to help! Thank you, Arwen

Try disabling the "Advanced" -> "Rendering" -> "Automatic Alpha Masks" (deferred and/or non-deferred).

There could also be graphics drivers settings that could negatively impact rendering in the viewer (such as NVIDIA's "texture sharpening", for example and anything dealing with ATI's "AI" settings: your graphics driver must be configured to let the viewer decide of the graphics settings and must not impose global system settings on it).

Note however that the v3.4 render (used in the Cool VL Viewer v1.26.5 and newer branches) renders things differently from the v2.6 one (used in the v1.26.1 to v1.26.4 branches). Each one got their own strengths and weaknesses/glitches, and it's up to LL to fix the current glitches in the current renderer, not to me.
If you don't obtain the result you would expect, I therefore recommend that you try and reproduce the issue with LL's official viewer and open a JIRA issue for the latter (do NOT open JIRA issues for the Cool VL Viewer (or any other TPV): they would be dismissed/ignored by LL, even if the issue also happens with their own viewer).

Thank you Henri for the speedy reply. I just downloaded the SL Viewer and the issue exists there as well. I will file a bug report in the SL JIRAs for this issue.

FYI - I did try the tips you suggested, however, they didn't correct the issue.

I've also discovered two additional issues:
- certain sculpts failing to rez - this issue is common to both the SL Viewer and the Cool VL Viewer, so I will file a bug report for it in the JIRAs
- inability to take a coalesced object into inventory - this is occurring only in the new Cool VL Viewer. The SL Viewer does allow me to select and take the coalesced object. So, I will file a new bug report here for you.

Thank you again and Happy Holidays to you!
~Arwen

Edited to add:
JIRA created for the sculpt/texture artifact issue - https://jira.secondlife.com/browse/BUG-1149
JIRA created for the sculpt failure to rez issue - https://jira.secondlife.com/browse/BUG-1148
Comment added to the Bug Report here in the Cool VL Viewer Forums regarding the inability to pick up unlinked/coalesced objects (instead of starting a new bug report)

This is nothing new... Got worst, lately, because LL apparently changed their texture server parameters (for the worst, obviously)... The Cool VL Viewer however entitles you to force-reload object textures (including sculpt texture), by selecting the object and using the "Advanced" -> "Rendering" -> "Reload Selected Texture" feature (to perform this quickly, just right-click on the object to reload and press CTRL SHIFT U).

This bug has already been reported and since fixed (fix will be part of this week's releases).

Thank you!
I will try the reload option for sure.
I didn't create a new bug report, just added a comment to the one I saw that was there already.
Many thanks for everything you do!

edited to add: I just tried the Ctrl-Shift-U and it doesn't work for these 2 sculpts that are giving me headaches. I did file a JIRA regarding the issue.