-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Killer Instinct - Low FPS #458
Comments
Thank you for taking some more time to document the issue for us. (For other folks, this started as a forum thread here: https://forums.libretro.com/t/mame-2010-2nd-player-remap/16025) Bringing over my notes from that thread:
|
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
I'm looking at the MAME 0.80 source right now. this caught my attention
|
This comment was marked as spam.
This comment was marked as spam.
Hm.. For what it's worth the OP mentioned in the forums that Killer Instinct runs at full speed on their system via MAME 2010. Although it has some controls issues for P2 in MAME 2010 so that's when this discussion began about how it performs worse in MAME 2003-Plus than it does in MAME 2010, at least for this setup. |
This comment was marked as spam.
This comment was marked as spam.
@grant2258 sorry I made some noise in the thread. Are you asking @purplesanz to try Killer Instinct in the regular MAME 2003 core, and disable the DCS Hack core option when doing the testing? |
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
I'm sorry. i3-3220 @3.30 GHz, 8 Gb RAM, GTX 660.
Believe me, so am I, but trust me, they are.
Oh, I forgot to mention that. Yes, I already tried DCS Hack ON and OFF, it doesn't make a difference. |
This comment was marked as spam.
This comment was marked as spam.
UPDATE: I got rid of some of the slowdown by disabling Hard GPU Sync in RetroArch. I have no idea why, but seems like MAME 2003 and MAME 2003 Plus are the only two cores that won't play nice with Hard GPU Sync, which is weird, since I use it with every other core (including MAME 2010, MAME 2014 and MAME 2016) in order to achieve less input lag, and I never had any issues with it before. Ok, that took care of the huge FPS drop when playing FMVs and when fireballs break into sparks, I don't know if the core is intended to work that way (without Hard GPU Sync), in which case, I'm sorry, my bad. However, the framerate difference is still there and it is VERY noticeable. I wish I could show you, is it possible to upload videos here? |
This comment was marked as spam.
This comment was marked as spam.
It is not, I tried that already. It is actually cool that you mention Progetto Snaps, since they have a very clear example of what I'm talking about: http://www.progettosnaps.net/videosnaps/mp4/kinst.mp4 See what happens when the stage is rotating at the beggining of the match? That's exactly what happens in MAME 0.78b and both MAME 2003 & MAME 2003 Plus cores, and I know it is not very noticeable in the video, but the overall speed of the game is not accurate, feels as if it was running at 40 - 45 FPS when compared to MAME 2010 (or any newer version). |
This comment was marked as spam.
This comment was marked as spam.
@purplesanz do you know what the most recent libretro MAME core you have access to that can run Killer Instinct at full speed? @Arcadez it seems almost like we should mark this as GAME_NOT_WORKING (or some other flag if there's a more specific one) :( At one point I was talking with twinaphex about the theoretical possibility of grafting a second, more recent version of MAME together with an older version like MAME 2003 so that only games that required the newer MAME code was running on it. This was a theoretical question understanding it would take an investment of time and energy, maybe also some money. My question is: does Killer Instinct run accurately and playable on MAME 2010 for anyone who can't also run it on more recent MAME cores? |
This comment was marked as spam.
This comment was marked as spam.
That would be MAME 2016 without Hard GPU Sync or any Frame Delay, which sucks for input lag. That's why I love how it performs in MAME 2010, with Hard GPU Sync ON and Frame Delay 5 the input lag is almost not noticeable, and FPS won't drop at all, it's perfect. |
I've just been having some Killer Instinct Chat ™️ with @barbudreadmon who was saying that
I don't have any objective in adding this to the discussion except as another datapoint |
This comment was marked as spam.
This comment was marked as spam.
@grant2258 that was a test with the mips3 standard interpreter in fba (the x86_64 dynarec runs at full speed), this is preliminary emulation stuff currently, and yeah my cpu was at 100% :) |
This comment was marked as spam.
This comment was marked as spam.
No, it was written by a fba developper, afaik there is no "pure" mips3 dynarec for x86_64 in mame, just the old x86_32 one, and the more recent "UML" one. |
I heard killer instinct runs full speed on Pentium 4 PCs using older versions of Mame but it lacks mips3 arm dynarec. it may be slow for all Android Devices even a snapdragon 855+ |
On an overclocked Pi 4 the exact description by the OP occurs. The slowdowns at those specific instances are exactly the same. If you also disable sound altogether, the game plays way too fast. It seems like the Pi 4 is capable (overclocked). I’d be willing to throw in a bounty if this is achievable. |
#1100 takes this discussion further. Moving this issue there, also added CPU clock scale core option to help increase performance |
But how about ARM CPUs? |
You'll have to expand your question a bit. But we added a new core option "CPU clock scale" which allows you to modify the clock speed of the emulated state. This has shown promise of increasing about 15 fps or so but requires tinkering to get a setting that works on your specific platform. For most cases the default setting should be used but if your looking to pull a few more fps this may be the key. For me I find a setting of about 40 to 60 yields the best results on my arm based platform. Noted that altering clock speeds can result in odd behaviors... Freezing, crashes, speed ups , slow downs, etc . |
Using Xiaomi Mi 9, Snapdragon 855 (ARMv8), Retroarch Plus APK, 1.10.3 Mame 2010 (0.139 932e6f2) core, Killer Instinct 1 plays nicely, with minor drops of fps during gameplay |
This repository is for mame2003-plus not mame2010, so I can't comment on the performance of mame2010. This core should be less demanding in general so I would recommend it over mame2010 in that regard. Altering the clock speed isn't exactly a magic fix, but can yield a slightly better experience. I would consider that option experiential for the tinker-er type of user |
Whenever an FMV is displayed or one of the top of buildings stages rotate at the beginning of a match, the FPS drop to 40s. Also, during any match (or whole game overall), even when the FPS counter stays at 60, the framerate feels choppy compared to any other MAME core. Framerate also drops when a fireball breaks into sparks.
Service mode is also broken. Some options cannot be set, and fps go too fast when trying to set the volume in-game.
The text was updated successfully, but these errors were encountered: