- Status
- Joined
- Aug 7, 2008
- Messages
- 2,464
- Trophies
- 2
- Location
- Melbourne
- Website
- vaguerant.tumblr.com
- XP
- 3,316
- Country
@mikimusone Nope. I believe this is a matter of a RetroArch feature which adjusts its cores to run at the Hz expected by the platform running the system. While we usually talk about NTSC games running at 60Hz and PAL games running at 50Hz, we're really generalizing because they actually all run somewhere in the range of those values and TVs are able to adjust to match the console's refresh rate (within reason). So maybe an NTSC SNES refreshes at a rate point four of a percent faster than a 3DS screen. Instead of skipping .4% of all frames, RetroArch will just slow down the emulated SNES so that it refreshes at the 3DS's rate. It's such a small difference that nobody is likely to notice the change without some kind of external hardware checking the framerate for them.
However, what you're seeing there is that you're running a PAL version game (~50Hz as the message stated) on a ~60Hz screen (the 3DS). This is a huge gap, so RetroArch leaves the emulated refresh rate alone at ~50Hz rather than speeding up the game. You might see a bit of frame juddering because the 3DS still has to display 60 frames per second but the core is only providing 50, so 10 of those 50 frames will just have to display twice.
On the subject of Terranigma, I'd recommend applying this patch which adjusts the ROM header to specify that it's a US cart and patches out the region lock. It means the game will run at 60Hz and this will look much better on the 3DS (and play at the intended gameplay speed, as the PAL release wasn't optimized to account for the 50/60Hz difference). There's essentially no reason to play the game at 50Hz. Incidentally, this game seems to work pretty well on blargSNES. I only tried it for a couple of minutes, but unless it breaks later, you'd be better off there instead of RetroArch.
For clarity, there's no setting you can change to fix the current scaling behavior in RetroArch 3DS. That's just a result of it being very early software that's not fully functional yet.
However, what you're seeing there is that you're running a PAL version game (~50Hz as the message stated) on a ~60Hz screen (the 3DS). This is a huge gap, so RetroArch leaves the emulated refresh rate alone at ~50Hz rather than speeding up the game. You might see a bit of frame juddering because the 3DS still has to display 60 frames per second but the core is only providing 50, so 10 of those 50 frames will just have to display twice.
On the subject of Terranigma, I'd recommend applying this patch which adjusts the ROM header to specify that it's a US cart and patches out the region lock. It means the game will run at 60Hz and this will look much better on the 3DS (and play at the intended gameplay speed, as the PAL release wasn't optimized to account for the 50/60Hz difference). There's essentially no reason to play the game at 50Hz. Incidentally, this game seems to work pretty well on blargSNES. I only tried it for a couple of minutes, but unless it breaks later, you'd be better off there instead of RetroArch.
For clarity, there's no setting you can change to fix the current scaling behavior in RetroArch 3DS. That's just a result of it being very early software that's not fully functional yet.
You're on o3DS correct? Because they're not slow on n3DS. Please specify which system you have when posting something like that. It's page 17, we know they're slow on o3DS. Lol.
Nice to see Starfox and Starfox 2 running, but alas too slow to be enjoyable, playable but not fun at that speed! Using New 3DS.
Picodrive crashed for me, but genesis_plus_gx_libretro is awesome... am playing Sonic 3 Complete as per my tradition of completing sonic 3 on every deviceI can run it on!
Picodrive crashed for me, but genesis_plus_gx_libretro is awesome... am playing Sonic 3 Complete as per my tradition of completing sonic 3 on every deviceI can run it on!
FCEUMM runs great on o3DS, from the games that I have tested. Snes9x is very, very slow at the moment (for o3DS)
Snes9x is very, very slow at the moment (for o3DS)
Can someone tell me the reason for this error: "Assertion failed at griffin/../audio_driver.c:447." Cause happened with many games and i have to make a hard reboot
Seriously hope they Port 'njemu_cps2_libretro' for other Device Builds
Hmm I think that's a though one, njemu has a lot of PSP specific code as far as I understand, it has full hardware acceleration and memory paging.
I asked aliaspider and he said he has not managed to implement vsync in the manner he intends to, but I think he's working on it.
Mainline is highly unlikely... it's a memory hog and consoles (and portable consoles) don't really have RAM to spare. Maybe 078 or imame4all could be possible
catSFC doesn't have SRAM saving from my testing. Save states should work fine
WOW, catsfc already performs very well, it's much better than BlargSNES already. Running it through Ninjhax 2.1 on my 9.0.0.20U N3DS produces some seriously impressive results. Once the options and interface are polished up a bit, (and 3D slider enabled, even if there is no actual 3D layer effect) it will be perfect!
coinblock, you are using a 2.1 ninjhax on the same firmaware i have.
What custom firmware do you use to still use cia's? or how do you switch from 1.1b to 2.1?
Thanks , i m still stuck on this ! can t try those emulators...
What custom firmware do you use to still use cia's? or how do you switch from 1.1b to 2.1?
Thanks , i m still stuck on this ! can t try those emulators...
That's great to hear! How's Gambatte on o3DS? I'm tempted to try it out.FCEUMM runs great on o3DS, from the games that I have tested.
I don't think they work in Ninjhax 1.x, you need 2.x.
I think all you'd have to do is have Ninjhax 1.x in one save slot & 2.x in another. I'm not sure though.
My sysnand firmware is 9.0.0.20U with the mset exploit and cubic ninja cia installed to the system menu. From there, I can launch Reinand and enter my 9.5 GW emunand, or go back into sysnand with sig checks patched and launch ninjhax 2.1b. If for whatever reason the exploit gets uninstalled, I can re-install it from the dstwo in my card slot. It's kind of a pain in the ass, but the best solution I could come up with for now.
I repeat: Can someone tell me the reason for this error: "Assertion failed at griffin/../audio_driver.c:447." Cause happened with many games and i have to make a hard reboot
- Status
