(01-15-2011, 06:29 AM)NaturalViolence Wrote:Wow, why are you using such old revisions? Also, FIFO received a dramatic speed-up in r6837. I noted that for FZeroGX it nearly doubled framerate. Lots of other games feel much smoother now too.Quote:@NaturalViolence: Yeah, right, but it was also James who fixed the shader cache from dumping stuff again and again; that's when the worst stutters (at least for me) disappeared.I stand corrected. I've been using 6505 due to the recent fifo changes and never noticed.
Testers needed for refactoring of texture decode/upload code
|
01-15-2011, 06:34 AM
01-15-2011, 06:45 AM
Well, F-Zero is still much slower than it was a few months ago...I'm not totally sure when that changed, but my guess is the big FIFO reorganization.
Intel i5-4690k (Devil's Canyon) @ 3.5 GHz (+Scythe Mugen) / Gainward GTX 1070 Phoenix (OC'd) / ASUS Z97 PRO GAMER / 16GB G.Skill DDR3-2400 CL10 TridentX / X-Fi XtremeMusic / Win10 Pro 64bit / Dell S2716DG Monitor / 3x original WiiMote+MotionPlus+Nunchuk
01-15-2011, 06:49 AM
(01-15-2011, 06:45 AM)StripTheSoul Wrote: Well, F-Zero is still much slower than it was a few months ago...I'm not totally sure when that changed, but my guess is the big FIFO reorganization.Ah. Did not know that. I would guess the FIFO work was done to extend emulation support and improve correctness? 01-15-2011, 06:52 AM
Yeah, before marcosvit's rework it was quite messy and hacky and a some games didn't even boot.
I have to correct myself about F-Zero, though...it's not as slow as I thought...I still gotta get used to the per-game-settings (in this case EFB Copy to RAM enabled) -_- (though it's still a bit slower than before, I think)
Intel i5-4690k (Devil's Canyon) @ 3.5 GHz (+Scythe Mugen) / Gainward GTX 1070 Phoenix (OC'd) / ASUS Z97 PRO GAMER / 16GB G.Skill DDR3-2400 CL10 TridentX / X-Fi XtremeMusic / Win10 Pro 64bit / Dell S2716DG Monitor / 3x original WiiMote+MotionPlus+Nunchuk
01-15-2011, 06:56 AM
(This post was last modified: 01-15-2011, 06:59 AM by NaturalViolence.)
Quote:Wow, why are you using such old revisions? Also, FIFO received a dramatic speed-up in r6837. I noted that for FZeroGX it nearly doubled framerate. Lots of other games feel much smoother now too. SMG2 latest revision - 45 fps 6505 - 55 fps That's why. Performance in all of my games is A LOT better in 6505 before the fifo changes. And with the exception of pixel depth (per-pixel depth stenciling) and pictobox (alpha read) fixes none of my games have had any fixes since then. I use 2.0 for WW since it's emulated perfectly except for audio, in fact it actually has less issues in those older revisions. MP and MP2 are unstable since the fifo changes. I can't think of a good reason for me to be using the latest revisions. Until I see some major fixes for any of my games that aren't already emulated properly on older builds or I see a sharp improvement in performance I'm going to continue only using the latest revisions for testing and not actually playing my games for fun.
"Normally if given a choice between doing something and nothing, I’d choose to do nothing. But I would do something if it helps someone else do nothing. I’d work all night if it meant nothing got done."
-Ron Swanson "I shall be a good politician, even if it kills me. Or if it kills anyone else for that matter. " -Mark Antony 01-15-2011, 07:00 AM
(01-15-2011, 06:56 AM)NaturalViolence Wrote:Makes sense, hence the complaint against FIFO. I can think of a reason - you're missing out on MY CODE!! Hahaha .Quote:Wow, why are you using such old revisions? Also, FIFO received a dramatic speed-up in r6837. I noted that for FZeroGX it nearly doubled framerate. Lots of other games feel much smoother now too. 01-15-2011, 07:04 AM
(This post was last modified: 01-15-2011, 07:05 AM by NaturalViolence.)
I'm no longer entirely sure it's the fifo changes that are the cause anymore. Xtreme removed all of the commits related to fifo changes using tortoisesvn after downloading the source then compiled it (gave it to me for testing). And it was still much slower than 6000-6553.
Anyways lets not derail this thread any more.
"Normally if given a choice between doing something and nothing, I’d choose to do nothing. But I would do something if it helps someone else do nothing. I’d work all night if it meant nothing got done."
-Ron Swanson "I shall be a good politician, even if it kills me. Or if it kills anyone else for that matter. " -Mark Antony 01-15-2011, 07:08 AM
(01-15-2011, 07:04 AM)NaturalViolence Wrote: I'm no longer entirely sure it's the fifo changes that are the cause anymore. Xtreme removed all of the commits related to fifo changes using tortoisesvn after downloading the source then compiled it (gave it to me for testing). And it was still much slower than 6000-6553.Lol m'kay then. I'm more or less using this thread as an update log for what I'm working on. 01-15-2011, 07:18 AM
TexDecoder_DecodeBGRA_GX_TF_RGB5A3_SSE2 crashes for me in line 513, the reference implementation works fine tho.
This silly me was wondering if it magically fixed the I4/I8 texture issues in Harvest Moon: A(nother) Wonderful Life - guess not, since the implementation is the same 01-15-2011, 07:20 AM
(This post was last modified: 01-15-2011, 07:33 AM by JamesDunne.)
(01-15-2011, 07:18 AM)Jack Frost Wrote: TexDecoder_DecodeBGRA_GX_TF_RGB5A3_SSE2 crashes for me in line 513, the reference implementation works fine tho.I (thought that I) disabled calls to SSE2 decoders in that branch. Oh I did just push a commit to re-enable that. Reset to the commit ID I mentioned in the OP. (01-15-2011, 07:18 AM)Jack Frost Wrote: TexDecoder_DecodeBGRA_GX_TF_RGB5A3_SSE2 crashes for me in line 513, the reference implementation works fine tho.Also, what I4/I8 texture decoding issues might you be referring to? The code looks correct and is pretty simple in the first place. Works fine for MKWii's use of these texture formats. |
« Next Oldest | Next Newest »
|
Users browsing this thread: 1 Guest(s)