Regarding GpuTest, I usually use the GUI with default settings, i.e. run ‘python gputest_gui.py’, select ‘FurMark’ and ‘1024x640’ and run benchmark.
The test prints GPU statistics to the console. The GUI shouldn’t affect the results, but you’ll get a bit more details. I’ve attached logs from benchmarks with v361 and v370 drivers.
gputest.txt (5.8 KB)
Hi PeteG, There is no much drop in FPS in your logs.
Score: 3445 points (FPS: 57) = v361
Score: 3260 points (FPS: 54) = v370
With 370 drivers the average difference isn’t big, but it’s clearly noticeable. FPS is constantly switching between 50 and 60 and graphics are jerky.
Installed PCLinuxOS 2016 mate + GTX660 , downloaded firestorm application and logged in to second life.
I saw some difference FPS state depending on the stages.
In Home town stage while normally FPS used to be 60 - 61 FPS and on roaming towards a little crowd i saw FPS drops and shows up to 46 -55 .
On moving towards stage names as " Popular Places " and in the stage, standing normally FPS comes to 50 -55 but on roaming and flying all around the green scenery , houses i would see FPS drop to 20
Overall looks like there is a FPS drop between 60 - 20 , and i am facing this issue on all the driver so seems its not a regression.
In SL, it is normal that the FPS rate varies from one place to another, and from different “populations” in the same place, or even from different camera angles (the fps rate depends on the objects being rendered on your screen, as well as on the total number of objects loaded in the viewer, even when they are not in the FOV of the camera). This is NOT the issue at hand !
What I witnessed with v367, v364 and v361 drivers (in this order from worst to best case) is a sudden, permanent, massive drop (like from 50 to 10 fps, or 150 to 20), that lasts even when nothing changes in your avatar’s environment (same place, same avatars around, same camera angle, i.e. same objects rendered on screen); that drop will then last until you relog or proceed to resize the window, or sometime minimize and re-maximize it, like I explained in the above posts.
I’m currently running v370.28 and so far could not reproduce the issue (but it took me time to get it happening with v361 as well, so only time will tell if it’s fixed or still there).
I’ll keep you posted, hopefully with a video demonstrating the issue, if it still happens with 370.28.
>>I’ll keep you posted, hopefully with a video demonstrating the issue, if it still happens with 370.28.
Is this issue reproduce with 370.28 ? If yes, Can you share video recording ?
Like I wrote: “I’m currently running v370.28 and so far could not reproduce the issue …/… I’ll keep you posted, hopefully with a video demonstrating the issue, if it still happens with 370.28.”
So far, v370.28 seems robust to me (but so it looked like with v361 for a week or so before I ran into the same issue as with v367).
I’ll let you know if anything happens.
It would also be interesting to know if Zalloi is still having issues or not with Firestorm and the new v370.28 driver.
Yes still having problems. Window resizing wouldn’t work for me. I always had to restart the application, forcing my friends to always see me go online and offline every 15 mins… I just decided to downgrade to the latest version with out the problem 364.51.
Zalloi, Do you think its system specific issue? Window resizing wouldn’t work for you. So I think you both are observing different issues. Don’t know what else need to do to reproduce this issue internally.
Umm IDK… it sounds to me that we are having the same problem but his driver is maybe letting him correct it better than mine. I just recently bought the XPS 15 a month or 2 ago which is what Im using Firestorm on. It has Intel Core i7-6700HQ CPU @ 2.60GHz, A 64-bit operating system and based processor on windows 10. The problem starts for me after v364.51 although for him he says the problem still occurs with v361.
I would just play normally and it would suddenly drop, no matter how laggy the sim was. I could teleport away and still have the problem. I would refrain myself from tabbing out time to time, that I found it will also make the problem occur quicker.
Hi Zalloi, Are you sure that you experiencing the same bug? It sounds like you are using Windows 10. You also mentioned you tried driver version 364.51, but we don’t even have a 364.51 Linux build
o.O
I’m just realizing this is for Linux… Sounds like the exact same problem except I’m having the FPS drop on Windows 10 while using firestorm!
dinosaur_, can you please provide a detailed, simple recipe of how to reproduce the problem? We need to observe it locally, and haven’t been able to yet.
Does the problem appear with other OpenGL applications or not?
Thank you
Can someone please post a link to the forums of where I can state the problem I am having for my windows 10 PC with Second Life.
Please, re-read my former posts: I gave you all the details I could. The only simple recipe is to run a SL viewer…
However, I have been running the latest driver (v370.28) for almost a full month now, and so far did not encounter the issue any more with it, which is good news (at least for me), even though I’m wondering what change between v370.28 and former versions could explain that the bug is (apparently, and so far) gone…
No, but I’m running very few OpenGL applications, and the SL viewer is by far the most complex and demanding.
OK, let us know if the problem ends up appearing again in r370.xx or more recent releases.
Thanks we are closing this bug 200233115 since for linux this issue is resolved with 370.28 driver. If you face similar issue please start new thread with detail reproduction steps and isolation.