Many of my games run pretty slowly; F-Zero GX, for example is prob. 50% or less (though it's not the framerate that bothers me, it's the slower than real-world progression of time). I consider my PC pretty good, but the graphics processor is really bad because I'm using an integrated graphics processor (IGP), so I'm pretty sure that's the bottleneck instead of my CPU, memory, or hard drive.
But, it'd be pointless to get a nice graphics card if the bottleneck is somewhere else, so is there some test I can do to be sure?
My system:
AMD Athlon II x3 450 3.2GHz
8 GB DDR3 1333MHz
SATA II 3.0Gb/s 7200RPM HDD
AMD Radeon HD 4250 with 128MB DDR3 1333MHz sideport memory
set internal resolution to 1x or 0.5x if the fps are still slow... its not the gpu
but isn't f-zero somehow bugged?!
how are the fps in other games?
The internal resolution is already set at 1x. How much of a difference does output resolution make? I've got it at 1440x900, which is the native resolution of my monitor. I'll get some fps numbers for other games for you after I get home.
Output resolution != Internal resolution unless IR is set to Auto. Try dropping the IR, but your CPU is probably the bottleneck because GX is one of the hardest games to emulate on Dolphin.
(01-10-2012, 06:09 AM)HawaiianPunch Wrote: [ -> ]Output resolution != Internal resolution unless IR is set to Auto. Try dropping the IR, but your CPU is probably the bottleneck because GX is one of the hardest games to emulate on Dolphin.
how i said f-zero gx is hard to emulate... (i said bugged what's wrong, but jeah.... the ending is the same)
but the cpu is just fine for most of the normal games
(01-10-2012, 06:09 AM)HawaiianPunch Wrote: [ -> ]Output resolution != Internal resolution unless IR is set to Auto. Try dropping the IR, but your CPU is probably the bottleneck because GX is one of the hardest games to emulate on Dolphin.
I must have misunderstood how IR works. I thought the multiplier was applied to the Gamecube's native internal resolution (a constant - we'll call it K), so it would render to memory at mult. x K and then scale that to the final output res. Are you saying it's actually mult. x output res. and then the final resize?
Uhm, it's indeed mult. x K and scaling to final output res (you seem to be one of the few "new" people who actually understand this), however rendering at a high internal resolution is what needs a decent GPU. The performance impact of a high output resolution is negligible.
(01-10-2012, 06:43 AM)neobrain Wrote: [ -> ]Uhm, it's indeed mult. x K and scaling to final output res (you seem to be one of the few "new" people who actually understand this), however rendering at a high internal resolution is what needs a decent GPU. The performance impact of a high output resolution is negligible.
Well I've tinkered around with homemade games, starting back in the days of DOS before DirectX was a thing and you had to code your own polygon rasterization subroutines (really fun for some of us and the bane of others). Anyway, thanks for the clarification. I'll do more testing later.
EDIT: I'm using Dolphin is version 3.0-368-dirty (64 bit).
Here's a breakdown of the speed of the games I own in percent.
F-ZERO GX 15 - 30
Finding Nemo ? - load screens too long - I haven't waited them out
Harry Potter and the Goblet of Fire ? - this was working yesterday but not today - can't think what I've changed
Lego Star Wars II 100
Lego Star Wars 100
Mario Kart Double Dash 100
Paper Mario The Thousand-Year Door 100
Star Fox Adventures 83 - 100
Super Mario Sunshine 98
Incredibles: Rise of the Underminder 50 - 73
The Legend of Zelda: The Windwaker 98 - 100
The Legend of Zelda: Twilight Princess 83 - 100
So Rise of the Underminer is iffy, but F-ZERO is the only one that's painful to play.
Also, I'm trying to set these up with shortcuts where it's easy for my kid use them, but some of the recommended settings for games don't show up in the per-rom settings. For example, the WW wiki page says to uncheck the "Disable Per-Pixel Depth" and "EFB Copies to RAM", but I didn't see either of these when I right clicked on the game and went to properties. I'd rather not have to remember what settings to change every time I run a game, and I know he won't. Is there a way around this?
And, if anyone knows what's up with Goblet of Fire or Finding Nemo, feel free to chime in.
I found the list of
in-game ini settings, so that helps, and I know you can set the back-end on the command-line. Oh, and GOF is mysteriously working again. I'm slowly putting the pieces together in my head of how this all works. Too bad there's no cohesive user manual, but I guess Dolphin changes too fast for that.