|
|
|
I have included 2 screen shots of Task Manager with and without VBO/Shaders enabled My x1550 is a PCI not PCI-e otherwise nothing abnormal with my system. With VBO/Shaders enabled, the framerate = .01 Standard viewer 1.19.14 same location = 37 fps. Inworld location for this data: You are at 283776.1, 260736.0, 13.5 in Kokyanwuti located at sim3234.agni.lindenlab.com (216.82.20.223:13000) This is an empty water sim, data obtained underwater, no agents present. The client to totally unresponsive, not only to the server but to any buttons or controls. I now, do not think this is a graphics card issue but something hogging the processor. It likely has to do with the graphics card driver not supporting a rendering feature we're using and falling back to software rendering. That's why it'll use more cpu.
I'll check it out on a PCI machine, that'll probably do the trick. Wow, that would be great! Fastest fix I have seen yet, evidently it was obvious in the logs. Yay, now on to the Triangle bug, lol!
/me crosses fingers Well, I was wrong, it didn't show up on the PCI machine. So I haven't isolated the bug yet.
I noticed that your OpenGL version doesn't match the one I got from the 8.4 drivers. (I got "OpenGL Version: 2.1.7415 Release") Did you download your drivers from here? Hi Brad, I think I did have the correct driver package prior to the Logfile I sent. Had a corrupt driver and reloaded and earlier driver, 8.3 I believe.
I will download and install the driver from the link and see if it makes any difference. Brad, I managed to install 8.4 driver again and now, I cannot login. Crash at the login screen before I am even able to connect.
Several observations tho. Prior to having a problem with my driver, sent the jira on Friday, and on Sunday, I started having problems and tried to update the driver. I kept getting installations errors, foremost, "RegPermWriter.exe" has encountered a problem. This, I later discovered, is Permissions to write to the registry. From what I googled on it, it seems ATI writes data in a weird registry key. So to be able to install the driver, I had to change permissions on the root "HKLM" and all subkeys to full permissions, then the driver finally installed. But, it only took about 2 minutes to install with an error, don't remember what it was. I am wondering if, because of the permissions in the subkey may not allow proper installation of the driver to utilize the full package, that this can be causing a multitude of problems with the driver. Any idea, in the meantime, I cannot run the RC anymore. The crash reporter will not send out the report either. After removing and reinstalling several different drivers and getting totally different results, all bad, I am coming to the conclusion that this, and possible more ATI related problems, are because of corrupt or missing driver installations.
This would also explain why it is so difficult to reproduce on identical machines. My current install will not allow me to run 1.20.6, crashes on startup, just before the html page loads. Running 1,19.4 is now not working properly either. i.e. now Shaders and VBO give 0fps boost to performance whereas, prior I achieved at least a 50% increase in fps. I am learning that totally purging ATI drivers is not quit as simple as thought and suspect remnants I have found this link, quite informative: http://www.rage3d.com/BOARD/showthread.php?t=33738545 with step by step instructions to completely purge ATI files. (edit) I found another purge thread, more current and a bit different procedure: The first link is very informative and has a lot of troubleshooting info, worth the read. This is going to take some time to perform and won't get a chance to try until this evening. I attached a Logfile earlier, see if you notice anything strange. (no performance change with VBO/Shaders, 1.19.4) I do still suspect some driver corruption and in order to keep this jira from looking like a support forum,
I posted my results on VWR-3258. I am pretty sure Catalyst Control Center is causing numerous problems in some configurations. This problem seems to be related to
Posted in First Look Viewer Forum:
ATI problems have been resolved? Version 1.2.6(87323) (Mono grid viewer) works perfectly with ATI. No Triangles no matter what you try to do- gone! [url]http://jira.secondlife.com/browse/VWR-3258[/url] FPS increase with shaders and VBO enabled! [url]http://jira.secondlife.com/browse/VWR-7017[/url] Poor performance relative to release 1.19.(4) ATI driver incompatibility My system is running better on Mono than it has ever run with old ATI drivers and a PCI video card. This should be released as the standard client. I hate having this post buried in this forum and it should be also posted in Residents Conversations to get as many people exposed to this as possible. I want to make a jira report but need outside conformation to this. I would hate to see this version get swept under the rug. 1.2.6(87323) is the best viewer of the series and my system is OLD! Information from
Second Life 1.19.1 (4) Apr 2 2008 11:59:37 (Second Life Release) CPU: Intel Pentium 4 Northwood (2992 MHz) "Erick Suavage - 25/Jun/08 06:20 PM Priority upped to Critical awaiting feedback from Erick and Brad Linden This problem is solved for me. I switched to a Nvidia 6200.
Secondlife has never run better for me. I am running 1.20.11, perfect. Framerates from a low 10fps, up 35 fps. ATI it seems, is more prone to support DirectX than OpenGL. Until ATI decides to better support OpenGL, /me becomes an ex-ATI customer. FOR SALE: Pile of slightly used ATI gfx cards. Please try the latest RC Viewer which can be downloaded from here Release Candidate Test Viewers
If it still an issue, please see the Meta-Issue: Issues with ATI Catalyst 9.1 VWR-12080
For account-specific help please post a Ticket with Support |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Useful info would include your log file in "c:\Documents and Settings\<username>\Application Data\SecondLife\SecondLife.log" immediately after the problem occurred, and a slurl for the content you were looking at when the problem occurred.