Well, a 280x is ~670, so why did you just hop sides? No substantial performance boost would be gotten from getting the equivalent GPU from a different company.
If increasing the IR causes an issue, then you might be running into an NB, GPU, or VRAM bottleneck. The lattermost is, by far, the most likely, since, iirc, the HD 7800 series cards (270, 270x now) had higher effective memory bandwidth than the 7900 cards (280, 280x now), and the 7800 GPUs were definitely not the best on the block for memory speed.
Though, I don't see how it could be happening at such a low IR. Maybe... well, looking at the settings you have in your sig, did you turn off LLE on thread, and turn off force texture filtering? And, with your hacks, try turning off Skip EFB Access.
What's your exact dev version revision? The reduced performance at higher IR indicates a GPU bottleneck. How are your GPU clocks/temps looking?
Change framelimit from Audio to Auto
Change fullscreen to auto
Turn off LLE on separate thread. Recently, it seems to brings slowdowns, and switch over to HLE DSP
(04-10-2014, 11:17 AM)kinkinkijkin Wrote: [ -> ]Well, a 280x is ~670, so why did you just hop sides? No substantial performance boost would be gotten from getting the equivalent GPU from a different company.
If increasing the IR causes an issue, then you might be running into an NB, GPU, or VRAM bottleneck. The lattermost is, by far, the most likely, since, iirc, the HD 7800 series cards (270, 270x now) had higher effective memory bandwidth than the 7900 cards (280, 280x now), and the 7800 GPUs were definitely not the best on the block for memory speed.
Though, I don't see how it could be happening at such a low IR. Maybe... well, looking at the settings you have in your sig, did you turn off LLE on thread, and turn off force texture filtering? And, with your hacks, try turning off Skip EFB Access.
The 670 stopped working and I never owned a Radeon before so I went for it. I turn off LLE thead by default now as it caused hanging with WW.
I just tried playing Mario Kart again with the settings on my sig (minus LLE on thread and force filtering) WITHOUT any graphical enhancement, so Native res, no AA, 1x AF, no post-processing, no PPL and no scaled EFB, and I still got major drops in Kart and <60 frames throughout the race. How is that a gpu issue?
(04-10-2014, 11:17 AM)rokclimb15 Wrote: [ -> ]What's your exact dev version revision? The reduced performance at higher IR indicates a GPU bottleneck. How are your GPU clocks/temps looking?
1356. HWinfo only gives me gpu temps, how can I check?
(04-10-2014, 11:25 AM)KHg8m3r Wrote: [ -> ]Change framelimit from Audio to Auto
From what I saw Auto gave me a very small performance boost but audio stuttering from <60/60 frames was horrible. Audio still gives stuttering just not as bad. OpenAL with 'Audio' gives no stuttering at all but gave me a performance hit of ~25fps.
Use gpu-z. I wonder if CCC is configured to do something wonky to dolphin or isn't configured to run at max settings. I don't know since I avoid AMD cards like the plague.
Under the Catalyst Control Center, do you have Dolphin set to use maximum performance?
CCC leaves GPU settings to the driver and OC software when you don't have CCC's OC software enabled (given that you have OC software). It's quite nice, actually, and the driver should respond properly to programs asking for certain performance levels (though, I don't think dolphin does this, so set it to max. perf. in CCC). Well, in windows, anyways.
As for clocks and temps together, I'd recommend picking up MSI Afterburner (which is very helpful for disabling PowerPlay, as well, which has caused issues on my own machine in the past). The recent betas, that is. And to make sure you don't let it install RivaTuner. RivaTuner's driver is known to cause BSoDs on many hardware configurations, and also cause performance degradation and a lower maximum OC on GPUs that reject it (like my own, but my own is a special case of special-itis). You just start Afterburner, configure it to monitor temps, clocks, and the GPU load, and run dolphin. You could either keep it on a separate monitor, or view the graphs once you're done in your game. If you do the latter, I recommend running the game, then clearing the graphs, then going back to the game, so that you get accurate minimums.
(04-10-2014, 11:44 AM)rokclimb15 Wrote: [ -> ]Use gpu-z. I wonder if CCC is configured to do something wonky to dolphin or isn't configured to run at max settings.
I'll post the results when I can, thanks.
(04-10-2014, 11:51 AM)KHg8m3r Wrote: [ -> ]Under the Catalyst Control Center, do you have Dolphin set to use maximum performance?
This crossed my mind before but I don't know. I'm using radeon pro and at one point I had Dolphin set to max settings and that did give me a performance loss but dolphin no longer has a profile. However like rokclimb15 mentioned it is a little "wonky" and sometimes I think enhancements still get applied regardless or something or that it's applying max settings in general or even interfering because I get performance drops on the ps1 emulator and can't apply sweetfx to any game. Might uninstall and let you know if that did anything.
(04-10-2014, 11:44 AM)rokclimb15 Wrote: [ -> ]I don't know since I avoid AMD cards like the plague
Mind telling me why? I'd like to know in case I made the wrong decision :/
I don't think you did necessarily. Mainly because I *hate* CCC and the buggy AMD drivers. AMD cards actually have a slight leg up in performance in recent dev versions. It's just a preference. I haven't owned an AMD card since they were owned by ATI (other than one early IGP that won't really game).
Well, the windows drivers don't have any issues, if you stay single-screen, single-card, don't use GPU Overdrive, and are completely okay with forced settings not being forced.
RadeonPro is completely safe if you make sure that it doesn't do API monitoring in software that doesn't have a profile. Actually, I'd bargain that THAT, right there, be your problem. Go into RadeonPro's configuration and find the thing under "advanced" that says something about disabling the API monitoring in the things not on the stuff list.