(03-10-2014, 06:41 AM)Shonumi Wrote: [ -> ] (03-10-2014, 06:32 AM)metalmallow Wrote: [ -> ]So is this benchmark tool pretty much useless with an Nvidia GPU installed? How far would I have to roll back the drivers for it to even work?
What are you talking about? This benchmark measures only CPU performance. What's more, the version of Dolphin delroth provided (see the 1st page, use no other version of Dolphin than that one) has no issue with Nvidia GPUs.
I'm talking about this:
(02-11-2014, 07:36 AM)Nemesys Wrote: [ -> ]This now crashes immediately every time I try to benchmark. Only thing I've changed is upgrading to beta drivers and based on the "Fault module name" is it safe to say that's likely the culprit here? Thanks.
And this:
(02-23-2014, 11:59 AM)Nemesys Wrote: [ -> ]I'm nearly positive the newest nvidia drivers cause this benchmark to crash. Would be cool to get a fix, doubt many will stay downgraded just for this.
I'm running 335.23, but this has been happening since the first time I tried it a couple of driver versions ago.
If it's happening with other versions of Dolphin (not just with this benchmark, it's an issue that Nvidia created with their drivers. Try it with other revisions. And if the latest drivers don't work for you, the obvious solution is to try something earlier. Just revert to "a couple of driver versions ago" and bam.
(03-11-2014, 02:53 PM)Shonumi Wrote: [ -> ]If it's happening with other versions of Dolphin (not just with this benchmark, it's an issue that Nvidia created with their drivers. Try it with other revisions. And if the latest drivers don't work for you, the obvious solution is to try something earlier. Just revert to "a couple of driver versions ago" and bam.
No, it's just this benchmark that won't work. The other versions of Dolphin work perfectly. And I never got the benchmark to work, I just said that I've tried three versions of the drivers so far and had no luck.
EDIT:
I just tried the regular 4.0-652 and it loads commercial games just fine. The benchmark version of Dolphin crashes as soon as I load the .elf, with the error message referencing nvoglv64.DLL, which I'm pretty sure is Nvidia related.
Others (such as JMC47) have reported no issues on Nvidia drivers. Just keep rolling back.
(03-11-2014, 04:23 PM)Shonumi Wrote: [ -> ]Others (such as JMC47) have reported no issues on Nvidia drivers. Just keep rolling back.
I have the same issue on a fresh install of windows 7. As soon as I try to run this it crashes. Haven't tried with a previous driver as I'm not to worried about it since games run just fine in the build I'm using.
CPU: Intel Core i5-3570k @ 3.40 GHz (OC @ 4.20 GHz)
OS: Windows 7 Ultimate x64
Time: 10 minutes 1 second
Screenshot:
http://i.gyazo.com/c003c64a689d39c9804ed39f85c80309.png
(03-11-2014, 04:23 PM)Shonumi Wrote: [ -> ]Others (such as JMC47) have reported no issues on Nvidia drivers. Just keep rolling back.
I just removed the GPU and ran the test with integrated graphics, instead.
CPU: AMD FX 8350 4.0GHz@4.9GHz
GPU: Sapphire R9 280X 3GB Dual-X
OS: Windows 8.1 Update 1 x64
Time: 11 minutes 3 seconds
Screenshot:
http://imgur.com/BLQ4Slc
What's the ideal time that will actually run Hyrule field at full speed?
How the hell would anyone know that?
(03-12-2014, 01:36 PM)NaturalViolence Wrote: [ -> ]How the hell would anyone know that?
1. use same CPU & clockspeed for this test
2. find average lowest FPS in Hyrule field (where? savestate possible?)
3. find time in benchmark
4. convert minutes to seconds for easy multiplication
5. 30/FPS = FPS2
6. time/FPS2 = time2
7. convert time2 to minute
Repeat with different CPU and/or clockspeed to see if it's consistent? If so, we've prolly found ideal time that will run hyrule field at full speed.