• 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.
MAINTENANCE ANNOUNCEMENT - JIRA will undergo maintenance starting 1:00am PDT through 3:00am on Saturday 2010.03.20. Please do not enter issues during this time as the system maybe restarted.
Issue Details (XML | Word | Printable)

Key: VWR-6658
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Khashai Steinbeck
Votes: 3
Watchers: 1
Operations

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

X, Y, Z alignment lines when editing a prim no longer accurately display spacial position

Created: 18/Apr/08 06:38 PM   Updated: 08/May/08 12:52 PM
Component/s: Building (in-world), User Interface
Affects Version/s: 1.20 Release Candidate
Fix Version/s: None

Time Tracking:
Not Specified

File Attachments: None
Image Attachments:

1. VWR6558.jpg
(410 kB)
Environment:
Windows XP Professional SP2
GeForce 8600GTS (256MB GDDR3)
2048MB DDR2 800
Issue Links:
Duplicate
 
Relates
 


 Description  « Hide
In viewer version 1.20.2 (85278), the alignment lines for X, Y, and Z coordinates no longer accurately appear to be at correct spacial positions when editing prims. This is very disorienting, and could severely limit building where this sort of alignment is necessary.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Gellan Glenelg added a comment - 18/Apr/08 11:28 PM
Spoke to Khashai.

When editing a prim, the red/green/blue X, Y,Z axis lines are being rendered after surrounding prims.
The lines are visible "though" the prims, making it more difficult to determine the relative positions.

See VWR6558.jpg - note the difference in appearance of the red line, going through the darkest prim.


Aimee Trescothick added a comment - 23/Apr/08 06:56 AM - edited
Like VWR-6244 and VWR-6301 this is another thing broken while fixing VWR-5211.

Lex Neva added a comment - 23/Apr/08 10:48 AM
This kind of bug also showed up before, a few years ago.

Aimee Trescothick added a comment - 23/Apr/08 10:52 AM
Compiling from the latest SVN this doesn't seem to be happening, so hopefully fixed in RC3.