[#VWR-13982] Sculpties not displaying after zoom out and zoom in

1. Second Life Viewer - VWR

Sculpties not displaying after zoom out and zoom in

Created: 11/Jun/09 07:41 PM Updated: 13/Nov/09 02:07 PM

Return to search

Component/s:

Graphics

Affects Version/s:

1.22, 1.23 Release Candidate

Fix Version/s:

None

File Attachments:

None

Image Attachments:

1. after zoom out.jpg (129 kB)	2. all visible.jpg (144 kB)	3. correctdisplay.jpg (347 kB)
4. zoom in and click.jpg (179 kB)	5. zoomoutandin.jpg (293 kB)

Environment:

« Hide

Second Life 1.23.4 (123523) Jun 9 2009 08:32:14 (Second Life Release Candidate)
Release Notes

Built with MSVC version 1400

You are at 161395.7, 251284.9, 501.6 in Piazza Fibonacci located at sim2536.agni.lindenlab.com (216.82.18.33:13001)
Second Life Server 1.26.4.120562
Release Notes

CPU: Intel Pentium III/Pentium III Xeon (0.25 micron process) with external L2 cache (3393 MHz)
Memory: 3327 MB
OS Version: Microsoft Windows XP Service Pack 3 (Build 2600)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce GTX 260/PCI/SSE2
Windows Graphics Driver Version: 6.14.0011.8585 , Nvidia driver 1.85.85
OpenGL Version: 3.0.0

Issue Links:

Duplicate

This issue duplicates:

~~VWR-13868~~ Rendermaxnodesize default value too low

This issue is original of duplicate:

~~VWR-15883~~ Various Sculpties are Deformed and i have played with the RenderVolumeLOD to 5

~~VWR-15871~~ Objects partially unrender when zooming in camera angle.

Relates

This issue Relates to:

VWR-12987 Primitives and changes made to primitives are not visible until camera is zoomed.

Last Triaged:	27/Oct/09 09:05 AM
Linden Lab Issue ID:	DEV-41885

Description

« Hide

Jewelry is sculpted prims, I was mistaken until corrected by the creator. Zoom out and zoom back in part of the jewelry "disappears" and does not rez again until i right click on it

All

Comments

Change History

Sort Order:

[ Permlink | « Hide ]

Harleen Gretzky added a comment - 11/Jun/09 07:46 PM

Possibly a duplicate of ~~VWR-13868~~ ?

[ Permlink | « Hide ]

Sharron Schuman added a comment - 11/Jun/09 08:01 PM - edited

- wrong, they are sculpted prims

possibly related, but these are not sculpted prims. the prim parts are still visible after zoom cycle. the part not showing is a texture with alpha on a simple prim. I think it may be related to #~~VWR-13097~~. I am not code savey enough to know. no changes are being made to the prim or the texture. The simple act of zooming out and back in is the only change from photo to photo. on a side note rendervolumeLOD is set to (8.).

[ Permlink | « Hide ]

Aradhana Voight added a comment - 11/Jun/09 09:56 PM

hi ...the prims are all sculpted and textures are non alpha, guess related to first link

[ Permlink | « Hide ]

Sharron Schuman added a comment - 11/Jun/09 10:00 PM

Aradhana is the creator of the jewelry... she knows, I was guessing. so is related to ~~VWR-13868~~.

[ Permlink | « Hide ]

Ann Otoole added a comment - 11/Jun/09 11:57 PM - edited

Using a version 1.23 viewer set renderMaxNodeSize to 6000 or higher (I am using 8192 - double the Linden selected 4096 - and experience no lag at all) and wait 30 to 60 seconds. If the issue ceases to be present then this issue is a duplicate of ~~VWR-13868~~. Sadly the graphics option tab in preferences is written so it overwrites custom configured settings anytime you change anything so, like with rendervollodfactor having to be set to 4 or above we will have to be constantly changing this setting to 6000 or more.

[ Permlink | « Hide ]

Tofu Linden added a comment - 12/Jun/09 02:16 AM

Amended title based on comments from the creator... as I understand them.

[ Permlink | « Hide ]

Sharron Schuman added a comment - 12/Jun/09 03:21 PM - edited

As Ann suggested I set renderMaxNodeSize to 8192. This setting had no affect. see photos "correctdisplay and zoomoutandin". As stated above rendervolumeLODfactor is set to 8.
environment is as listed above. Second Life 1.23.4 (123523) Jun 9 2009 08:32:14 (Second Life Release Candidate)

I ran the same test using the standard release: Second Life 1.22.11 (113941) Mar 6 2009. The results are the same as with the RC, so this is not a RC only problem. the description of ~~VWR-13868~~ states that it is not apparent in 1..22.11.

[ Permlink | « Hide ]

Harleen Gretzky added a comment - 21/Jun/09 02:51 PM

I have this jewelry and for me this does not reproduce in Second Life 1.22.11 (113941) Mar 6 2009 12:50:02 (Second Life 1.22.11).

In Second Life 1.23.4 (123523) Jun 9 2009 08:32:14 (Second Life Release Candidate) it only reproduces when RenderMaxNodeSize is low enough, at around 4096, at 8192 the effect does not show up, exactly as described in ~~VWR-13868~~.

[ Permlink | « Hide ]

Alexa Linden added a comment - 01/Jul/09 08:47 AM

Duplicate of ~~VWR-13868~~

[ Permlink | « Hide ]

Sharron Schuman added a comment - 01/Jul/09 10:25 AM

I suppose rather than get in a jira argument i will let this play out, setting Rendermaxnode size at 8192 has no effect on this problem for me

[ Permlink | « Hide ]

Sharron Schuman added a comment - 19/Oct/09 09:57 PM

This issue was declared a duplicate of http://jira.secondlife.com/browse/VWR-13868 and closed. http://jira.secondlife.com/browse/VWR-13868 is now closed and declared resolved by setting rendermaxnode size to 8192. That setting has no effect on the problem i describe here. I am copying my comments to http://jira.secondlife.com/browse/VWR-13868.

endermaxNodeSize does not fix this for me. I have to click on the prims. I can click on them and make visible then if i change camera to another view and return to the items (jewelry mostly) the will have disappeared again and i will have to click again. You can imagine what a PITA this is shooting models in a fashion show. This problem seems to be worse with 1.23.5. I would love to use Snowglobe, but it is important to me that prims and avatars be textured eventually. Texture loading problems make snowglobe unusable for me. I am curious what "broke". This jira issue was not a problem 6 months ago, but then neither were most of the snapshot bugs problems 6 months ago. It seems logical to me that things that used to work ok and then don't in new releases would get the highest priority. I don't get it... if you break it, fix it, new features and wizz bang doodle stuff can wait till you fix what you broke making the new stuff.

Second Life 1.23.5 (136262) Oct 14 2009 12:08:26 (Second Life Release)
Built with MSVC version 1400
You are at 161389.4, 251290.5, 501.1 in Piazza Fibonacci located at sim3852.agni.lindenlab.com (216.82.52.10:13002)
Second Life Server 1.30.2.135876
CPU: Intel Pentium III/Pentium III Xeon (0.25 micron process) with external L2 cache (3807 MHz)
Memory: 3327 MB
OS Version: Microsoft Windows XP Service Pack 3 (Build 2600)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce GTX 260/PCI/SSE2
Windows Graphics Driver Version: 6.14.0011.9107
OpenGL Version: 3.2.0
libcurl Version: libcurl/7.18.1 OpenSSL/0.9.8j zlib/1.2.3
J2C Decoder Version: KDU

[ Permlink | « Hide ]

Harleen Gretzky added a comment - 20/Oct/09 04:09 AM

Even though you cannot use Snowglove because of other reasons, does this particular issue happen in Snowglobe?

Also since this did not occur 6 months ago when I assume you were using 1.22.11, but this issue also occurs for you when using 1.22.11 now, it may possibly not even be a viewer issue.

[ Permlink | « Hide ]

Sharron Schuman added a comment - 20/Oct/09 09:22 AM

I will run snowglobe and see. Uh... what else can it be other than a viewer issue? This is not an issue that only I can see. Others commented that the problem still exists for them when ~~VWR-13868~~ was closed. It is possible it only affects nvidia users, I don't know that. I do know that many others I talk to continue to experience this problem.

[ Permlink | « Hide ]

Harleen Gretzky added a comment - 20/Oct/09 09:57 PM

Not sure I am using an nVidia and not experiencing it since increasing my RenderMaxNodeSize to 8192, it seems like a viewer issue except for the fact that you did not have the issue with 1.22.11 and then all of a sudden you do even with 1.22.11 which has not changed in the last 6 months. It was fixed for ~~VWR-13868~~ in 1.23.5, if the others who are experiencing this did not upgrade or are using third party 1.23 viewers or even Snowglobe (which shares the ~~VWR-13868~~ bug and has not been fixed yet) then they would still be experiencing it.

[ Permlink | « Hide ]

Sharron Schuman added a comment - 22/Oct/09 10:42 AM

Harleen, If you look at my system information I pasted in my comments, I am using the "official"1.23.5. I still have this problem even with rendermaxnode size set to 8192.

[ Permlink | « Hide ]

Vengence Keon added a comment - 23/Oct/09 11:38 AM

i am also having this issue ~~VWR-15883~~ and changing above settings did not work for me either

[ Permlink | « Hide ]

Harleen Gretzky added a comment - 25/Oct/09 09:26 PM

You also said:

Sharron Schuman added a comment - 12/Jun/09 03:21 PM - edited
As Ann suggested I set renderMaxNodeSize to 8192. This setting had no affect. see photos "correctdisplay and zoomoutandin". As stated above rendervolumeLODfactor is set to 8.
environment is as listed above. Second Life 1.23.4 (123523) Jun 9 2009 08:32:14 (Second Life Release Candidate)

I ran the same test using the standard release: Second Life 1.22.11 (113941) Mar 6 2009. The results are the same as with the RC, so this is not a RC only problem. the description of ~~VWR-13868~~ states that it is not apparent in 1..22.11.

[ Permlink | « Hide ]

Harleen Gretzky added a comment - 25/Oct/09 09:39 PM

Have you tried an even higher RenderMaxNodeSize, say 16384?

[ Permlink | « Hide ]

Adeon Writer added a comment - 12/Nov/09 09:47 AM

Please make sure the debug setting RenderVolumeLOD is set to a power of two, like 2, 4, or 8. Other values will be unpredictable.

[ Permlink | « Hide ]

Vengence Keon added a comment - 13/Nov/09 02:06 PM - edited

Ok......to those who have ATI cards with this problem i have found a solution........if this pertains to you......I recently Disabled The Catalyst AI program that comes with ATI cards. and set all graphics card settings to be determined by Program.......and it fixed my issue. And enabled tripple buffer on Open GL.