• 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-3684
Type: Bug Bug
Status: Resolved Resolved
Resolution: Needs More Info
Priority: Critical Critical
Assignee: Unassigned
Reporter: Umbra Lunardi
Votes: 3
Watchers: 3
Operations

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

Framerate below 0.3 FPS in Windlight 1.18.5.74965

Created: 05/Dec/07 10:48 PM   Updated: 10/Mar/08 10:43 AM
Return to search
Component/s: Graphics
Affects Version/s: First Look: WindLight
Fix Version/s: None

File Attachments: None
Image Attachments:

1. Picture 3.png
(797 kB)

2. Picture 6.png
(788 kB)

3. Picture 8.png
(745 kB)
Environment:
 Machine Name: PowerBook G4 15"
  Machine Model: PowerBook5,6
  CPU Type: PowerPC G4 (1.2)
  Number Of CPUs: 1
  CPU Speed: 1.67 GHz
  L2 Cache (per CPU): 512 KB
  Memory: 1.5 GB
ATI Mobility Radeon 9700:

  Chipset Model: ATY,RV360M11
  Type: Display
  Bus: AGP
  VRAM (Total): 64 MB
Issue Links:
Relates
 


 Description  « Hide
Current Windlight release 1.18.5.74965 suffers from extreme performance loss manifested by a 0.1 to 0.3 FPS framerate. (That's right: zero point one FPS) After 20 minutes connected to the grid, my machine was still attempting to draw everything in the scene. Avatar movement was out of the question. Graphics settings were not adjusted by me, I simply used it at the default settings immediately after installation of the viewer update. Fast timers screen capture to be included.

Edited Graphics prefs by turning OFF Atmospheric Shaders, and framerate jumped up to close to 6,0 FPS



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
WarKirby Magojiro added a comment - 06/Dec/07 05:19 PM
For comparison, what is your framerate like normally ?

Umbra Lunardi added a comment - 08/Dec/07 04:08 AM
I test framerate in my home sim, and the area I was testing in normally delivers 12 FPS, and in some parts of the island I get 35 FPS. Since I was unable to move or even turn to look at a different view, I can only comment on the view that usually gives 12FPS, which was doing 0.1 and 0.2 FPS.

My MacBook Pro does better, but still gets only about 3 FPS compared to 12 FPS when using the normal (non-Windlight) client.


Joshua Philgarlic added a comment - 11/Dec/07 01:37 AM
I've the same problem. I use a 2 years old Intel iMac. Normal frame rate is 10-20. With Windlight it's EXTREMELY slow.

Celierra Darling added a comment - 11/Dec/07 02:39 AM
For the timers, can you expand the "|+Render" node in the tree (click the plus next to "Render", which is the second-to-last in the current screenshots), and if a lot of the time is still grouped under a single node, keep expanding those nodes until you can't anymore? (You can tell the times from the numbers in brackets, ex. currently next to "|+Render" it says "[3137.8]".) That screenshot would probably narrow things down a lot more. Thanks!

Torley Linden added a comment - 13/Dec/07 09:51 AM
Those of you on Macs experiencing SLOW performance, what OS are you on? If it's Leopard, then this issue is likely a duplicate – you can resolve it and link to VWR-3160. Thanks. =)

Umbra Lunardi added a comment - 13/Dec/07 11:07 AM
Torley,
I am experiencing this performance problem on two Macs, both running OS X Tiger 10.4.11, NOT Leopard. The MacBook Pro I have with Leopard on it runs just fine.

Rascal Ratelle added a comment - 24/Jan/08 05:05 PM
Same thing here, using Imac PowerPC based proccesser, Tiger 10.4.11

Hardware Overview:

Machine Name: iMac
Machine Model: PowerMac6,1
CPU Type: PowerPC G4 (3.3)
Number Of CPUs: 1
CPU Speed: 1.25 GHz
L2 Cache (per CPU): 256 KB
Memory: 768 MB
Bus Speed: 167 MHz
Boot ROM Version: 4.6.8f4

GeForce FX 5200:

Chipset Model: GeForce FX 5200
Type: Display
Bus: AGP
VRAM (Total): 64 MB
Vendor: nVIDIA (0x10de)
Device ID: 0x0329
Revision ID: 0x00a2
ROM Revision: 2068


Barney Boomslang added a comment - 13/Feb/08 01:48 AM
I experience the same thing with the Windlight builds: very low framerates compared to the 1.18.5 client. Normally in my lab (Lummerland, at height 700, so not much distraction) I get something around 40 FPS, but with the windlight builds at max get 12 FPS. On ground, I normally get 15-20 FPS, with windlight more like 8. The framerate with Windlight is at best half of what I am used to with 1.18.5.

My machine is a MacBook Pro 15" with a ATI Radeon X1600, running Mac OS X 10.4.


Torley Linden added a comment - 10/Mar/08 10:43 AM
This issue was resolved as "Needs More Info" during our batch cleanup because it was set as affecting First Look: WindLight. On the Issue Tracker, we've noticed many duplicate issues and issues that lacked actionable info or were already fixed.

WindLight recently "graduated" from a "First Look" technology preview to Release Candidate status – nearing inclusion in the main viewer with your help! So, "First Look: WindLight" does not exist anymore.

More info and how to download the RC viewer: http://blog.secondlife.com/2008/03/06/new-release-candidate-viewer-1191-rc0-available/

If you've verified that this issue is still a problem in the newest Release Candidate, here's what to do next:

(1) Search the Issue Tracker to make sure it isn't a duplicate of an existing issue we know about. If it is, link it as a duplicate using the "Link this issue..." link on the left. You can learn more about searching by watching this video tutorial: http://www.youtube.com/watch?v=SAlXK5hSVMc

(2) Reopen the issue and BE SURE to update the "Affects Version/s" to the correct one, most likely ONLY "1.19.1 Release Candidate". However, if this bug affects the main viewer (1.19.0 as of this writing), then DO NOT set it to an RC version. Only set it to 1.19.0 instead. Be as specific with versions as possible – there's generally no need to set multiple versions, as it tends to dilute and confuse where a bug originated.

(3) Add any other relevant details that would help us fix it. We can't stress the importance of a "solid repro" enough – a reliable series of steps to make a bug happen reliably.

(4) Come and attend our inworld bug triages, where you can meet with Linden Lab employees to look at, verify, and expedite bugs for fixing. More info @ http://wiki.secondlife.com/wiki/Bug_triage

Thank-you for helping us improve Second Life!