• All submissions to this site are governed by Second Life Project Contribution Agreement. By submitting patches and other information using this site, you acknowledge that you have read, understood, and agreed to those terms.
Issue Details (XML | Word | Printable)

Key: VWR-13038
Type: Bug Bug
Status: Fix Pending Fix Pending
Priority: Normal Normal
Assignee: Unassigned
Reporter: EddyFragment Robonaught
Votes: 9
Watchers: 3
Operations

If you were logged in you would be able to see more operations.
1. Second Life Viewer - VWR

Underlapping of what should be overlapping prims in an object. Additionally failer to set shiney after scripted alpha was released.

Created: 28/Apr/09 05:18 PM   Updated: 04/Jun/09 11:13 PM
Return to search
Component/s: Graphics
Affects Version/s: 1.23 Public Nightly
Fix Version/s: 1.23 Release Candidate

File Attachments: None
Image Attachments:

1. Underlapping non shiney prims.jpg
(239 kB)

2. Underlapping non shiney prims2.jpg
(235 kB)
Environment:
Second Life 1.22.11 (113976) Mar 6 2009 16:05:03 (Second Life Release Candidate)
Release Notes

You are at 247854.5, 311793.4, 21.6 in Chrysanthemum Island located at sim2468.agni.lindenlab.com (216.82.17.219:12035)
Second Life Server 1.26.2.117266
Release Notes

CPU: Intel Core 2 Series Processor (2000 MHz)
Memory: 3071 MB
OS Version: Microsoft Windows XP Service Pack 3 (Build 2600)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce GTS 250/PCI/SSE2
OpenGL Version: 3.0.0

libcurl Version: libcurl/7.16.4 OpenSSL/0.9.7c zlib/1.2.3
J2C Decoder Version: KDU
Audio Driver Version: FMOD version 3.740000
LLMozLib Version: [LLMediaImplLLMozLib] - 2.01.23522 (Mozilla GRE version 1.8.1.13_0000000000)
Packets Lost: 0/153407 (0.0%)

NOTE: Same system but was running the PN viewer when I saw the problem. It is not present in the RC viewer.
Issue Links:
Relates

Last Triaged: 21/May/09 11:20 AM
Linden Lab Issue ID: DEV-32680


 Description  « Hide
I am creating a simple weapon that rezzes a cage amongst other things. In the Public Nightly viewer The rezzed cage was not rendering it's shiney surface (on white default) after the script was ordering it to change from full alpha to full non-alpha via llSetLinkPrimitiveParams(). The object also had the apperance of underlapping prims (toruses) when they should have been overlapping. I have two snapshots of my view of the problem and I tested the result many times. I have also found that the effect is not seen in the release cadidate viewer. I have built an object with the name "Cage Rezzer" and left it in my objects folder for any Linden who's job it is to check these things. Nyx Linden is aware of the issue and asked for this object to be made available. It contains the screenshots (snapshots) and other than the rezzer oject script and the string names (applicable during the listen events) I have left the scripts exactly as they were when the effect was seen.

 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
EddyFragment Robonaught added a comment - 28/Apr/09 05:36 PM
Changed file type for screenshots to jpg.

EddyFragment Robonaught added a comment - 28/Apr/09 05:51 PM - edited
And again cause I got it wrong last time. Thanx to Moon Metty for her help in fixing it. (not fixing the bug, fixing the photos)

Moon Metty added a comment - 20/May/09 04:11 PM

Alexa Linden added a comment - 21/May/09 11:22 AM
Eddy, Can you drop a copy of an example script on Soft Linden to test with? Thanks

Soft Linden added a comment - 21/May/09 12:00 PM
I think Alexa wanted Nyx above.

EddyFragment Robonaught added a comment - 22/May/09 11:29 AM - edited
Roll up! Roll up!

Who wants a copy?? hehehe.

Davy Linden has already got the scripts and Nyx was present on the day I posted the jira (in fact he is gloriously framed in the attached jpg) and asked me to pass it on to QA.

Please advise if necessary Alexa or Soft or anyone else......

wonders why he is so popular today


Moon Metty added a comment - 22/May/09 12:43 PM
According to Nyx, it's Runitai working on the bug.

EddyFragment Robonaught added a comment - 22/May/09 12:46 PM
/me shrugs giggles and heads for search >people in world.

EddyFragment Robonaught added a comment - 02/Jun/09 01:46 PM
Appears to be fixed in Second Life 1.23.3 (122084) May 28 2009 21:01:25 (Second Life Public Nightly)
Release Notes

Built with MSVC version 1400

Well done LL. Good job. Can someone confirm so I can close this?


EddyFragment Robonaught added a comment - 03/Jun/09 10:38 PM - edited
Helloo? Since I am not the only person watching this. I wonder if someone could please confirm that this is fixed?

Appears to be fixed in RC 1.23.3 too.


Moon Metty added a comment - 04/Jun/09 05:49 AM
Hi Eddy,

Indeed, RC3 is out, and the bug looks very much fixed.


EddyFragment Robonaught added a comment - 04/Jun/09 11:12 AM
\o/ Thanx Moon for confirming my findings and a HUGE THANX to Linden Labs.

EddyFragment Robonaught added a comment - 04/Jun/09 10:55 PM
Since a conversation on bsi I looked into the resolutions and cannot make head nor tail of what is correct for this. According to the guidelines I should not have marked it "fixed" as that would mean that it it fixed in a public release. Since I cannot choose "Resolved" cause (I assume) it was never assigned but it is not present in RC3 I am guessing that "Cannot Reproduce" must be fair. However that would be inappropriate cause it was a problem but isn't any more.

Status of your Issue

[edit] Available states
Here is how Linden Lab uses the various resolution states:
Open
This is an issue that belongs to the Assignee to resolve. The Assignee may fix the issue, or kick the issue back to the person who reported it, by marking it "Resolved" (see below)
In Progress
This is how a developer signals to everyone that he/she is working on the issue.
Reopened
same as "Open". Even though it was closed before, it is now reported as still a problem that needs attention.
Resolved
This is an implicit assignment back to the reporter of the issue. It is not closed yet, but rather in a state of limbo that depends on the resolution. It's up to the Reporter to decide whether to reopen an issue, or close it.
Fixed
means that the bug is fixed in a public release of Second Life.
Fix Pending
means that the bug is fixed in a version of the code that should soon be publicly available.
Contact Support
the issue in the Pjira is one that needs to be handled through the support team and the resident needs to fill out a support ticket.
Won't Finish
means that the assignee or Linden Lab doesn't believe this issue should or will be fixed in any foreseeable future.
Duplicate
means that there's some other issue that describes the same problem/idea.
Expected Behavior
the issue being discussed is not a bug and functions as it does by design.
Needs More Info
this issue lacks enough information. Please add that information or it CANNOT be investigated further.
Under Advisement
this is used by Linden Lab for issues that tend to fall more in the category of Policy rather than being just a technical bug. This is used to let the community know that the Pjira has been viewed and is being discussed.
Cannot Reproduce
this means that following the stated steps still does not show the problem. Perhaps there is additional settings/actions or factors that need to be true in order for the problem to occur. Please provide an even more detailed description of how to reproduce a problem. Issues that can't be reproduced will eventually be closed.
Misfiled
this issue doesn't belong in this issue tracker.
Closed
The final resting place. It's done!

All the above are the guidelines so I am opting for fix pending but at the time of writing cannot choose that option. I will edit if after changing the resolution I find I can choose that.

I understand that this all seems a bit messy but in my defense the above seems to have some omissions to me. And my intention was simply to state that in RC3 the problem no longer exists. By closing this I was rather hoping to be saving time and space. Ooops.


EddyFragment Robonaught added a comment - 04/Jun/09 11:00 PM
Resolved(fix pending) seems to only be available for LL staff cause it needs an internal branch thing that I haven't got. I give up for now and hope someone else knows what to do. At least the bug was fixed (even though apparently calling it fixed when it is is wrong).

EddyFragment Robonaught added a comment - 04/Jun/09 11:13 PM
Thanx to Harleen for tidying up my mess.