Any other ideas? Also, is the psp version of the bios the best and I was correct in renaming to scph5501?
Homebrew RetroArch Switch
- Thread starter ShadowOne333
- Start date
- Views 1,880,660
- Replies 9,158
- Likes 96
Any other ideas? Also, is the psp version of the bios the best and I was correct in renaming to scph5501?
Psp ps1 bios are the best. Everything is optimized. Also mupen64 is seriously a wip. Nothing runs full speed. I'm surprised no has taken the bounty yet.
Thx i tried it it did't do much to the audio. The audio is cracking a little but playable :-) thx again
For anybody who's having audio stutter issues, here are some things to try:
1) make sure you have the right bios
2) threaded video enabled (in video settings)
3) switch_thread audio driver (in driver settings)
4) play with audio latency (in audio settings) 80-100 seems to help
5) play around with dithering and frame duping to see if that eeks out a bit more FPS (in quick menu -> options)
If you are still hearing audio stutter, turn on your FPS counter (in on-screen notification settings) and look at it while running the game. If you are getting less than 59 FPS, audio stutter is expected. This is because the game is running at less than full speed, so the audio will try to keep pace and also run at less than full speed. There is no kind of audio smoothing to make up for the lower pace.
There is no "glitchy nightly build". You just need to temper your expectations until we get some bounties filled for improvements to the core.
1) make sure you have the right bios
2) threaded video enabled (in video settings)
3) switch_thread audio driver (in driver settings)
4) play with audio latency (in audio settings) 80-100 seems to help
5) play around with dithering and frame duping to see if that eeks out a bit more FPS (in quick menu -> options)
If you are still hearing audio stutter, turn on your FPS counter (in on-screen notification settings) and look at it while running the game. If you are getting less than 59 FPS, audio stutter is expected. This is because the game is running at less than full speed, so the audio will try to keep pace and also run at less than full speed. There is no kind of audio smoothing to make up for the lower pace.
There is no "glitchy nightly build". You just need to temper your expectations until we get some bounties filled for improvements to the core.
Thanks for making a video man! Guess Spiderman is just an issue overall. It's funny my Spidey wasn't as bad as yours but your GTA sounds much better. Maybe it's the PSB format I'm using? I might try the bin/cue method and see if that helps.
If Reicast comes to the Switch...!!!!!!
Big Sega Naomi update coming in Reicast Libretro! Games that will be fully playable soon: Gun Survivor 2: Biohard Code Veronica, 18 Wheeler DX, FTS, Maximum Speed, Alien Front, Confidential Mission, Death Crimson OX, Jambo Safari, Sega Strike Fighter, Typing Dead, and Virtual On! pic.twitter.com/MOOKEAqhuP
— libretro (@libretro) October 11, 2018
Question for the PCSX core. All 8-16bit systems don't give me any issues but for some reason the PCSX core gives me issues, and ends up not loading games and freezing. This happens wether is use the NSP and or go through the Homebrew Menu. Before using the official Retroarch, I used retroNX without any issues. I completely deleted all retroNX files and configurations before doing a fresh install of Retroarch. Any Ideas on what it might be causing the issues when I changed from RetroNX to Retroarch? All files Rome, ISO's, bios, are the same, the only differences are Retroarch flies VS RetroNX files. My SD card is formatted to FAT32 and I use Hekate to launch CFW.
Other changes I've made once on Retroarch are...My memory card does have less space, like 250MB space free if that can affect it too? I also added the shader 4xScaleHQ.glsl. Could that maybe make game compatibility worse also, making games that worked before freeze now?
I usually choose core first, then load content, then verify it's the right core. It looks like it's loading but then it just stays on the black screen. Also when I go to the XMB menu to try to close content or close retroarch, it freezes. Also the XMB menu is messed up, it's missing all icons, it just has the words.
Thanks in advance!
Other changes I've made once on Retroarch are...My memory card does have less space, like 250MB space free if that can affect it too? I also added the shader 4xScaleHQ.glsl. Could that maybe make game compatibility worse also, making games that worked before freeze now?
I usually choose core first, then load content, then verify it's the right core. It looks like it's loading but then it just stays on the black screen. Also when I go to the XMB menu to try to close content or close retroarch, it freezes. Also the XMB menu is messed up, it's missing all icons, it just has the words.
Thanks in advance!
Last edited by zenjiki,
When you installed RetroArch, did you delete all of your old RetroNX files? or overwrite? Try deleting all RA/RNX files (except saves if you care to keep those) and installing completely fresh.
It was a complete fresh install, but googled the error code and took me to a YouTube video that didn't pertain to Retroarch to homebrew but using a device called Brrok Super Converter...
On the video it said to fix the error one must go under system settings and turn the setting Pro Controller Wired Communication to on, it wasn't pertaining to Retroarch but I did it anyway and it has fixed it. So far I've booted at least 20 PS1 ISO's without an error. Weird but ill take it!
Last edited by zenjiki,
What are considered the optimal settings for Retroarch Switch at the moment? For PSX and N64 emulation
P.S. guys my scanned PS1 games won't appesr in the playlist. Only 3 of 34 do, even though when I load them individually they work
P.S. guys my scanned PS1 games won't appesr in the playlist. Only 3 of 34 do, even though when I load them individually they work
Last edited by FightingPolygon,
i made an interesting discovery earlier today. I thought why don't i try the NEW nsp and the latest nightly. BAM bad audio in psx rearmed. Across the board too. Rolled back BAM back to what I like. So methinks something broke in latest nightlies so I would roll with stable not latest nightly. Nightly that works fine for me is 10/07 hope this helps others.
zenjiki I have no idea what that last post means (like what you ended up doing etc) but oddly I do always play with a pro controller. Is this part of the magic formula?
zenjiki I have no idea what that last post means (like what you ended up doing etc) but oddly I do always play with a pro controller. Is this part of the magic formula?
Last edited by grabman,
For the most part, I haven't had any issues aside from getting random error codes when using PCSX. But as weird as it seems, what finally fixed my issue was just to go to system setting and turn the setting for Pro Controller Wired Communication to on.
So I've re-re-formatted my real 128GB microSD to fat32 with 32KB cluster size, and installed RetroArch fresh from here using the nightly build 2018-10-12_RetroArch.7z. I'm still using ReiNX 1.7 and there are two crashes I have observed.
If you have an improperly set playlist entry it will crash upon loading. Obviously this can simply be fixed by properly configuring the playlist, but it does indeed crash and take the whole system.
Also, if you enable thumbnails at all, and I'm aware that others on here have had this issue - I assure you it's not an SXOS specific issue as I have never used and do not use SXOS - it can turn thumbnails black, allow you to do whatever you want, and then crash 100% of the time no matter what you select next. I would imagine this is very repeatable on just about any build, although it took me several minutes of flipping through thumbnails to trigger. I surmise disabling thumbnails completely would make this very stable; I believe I will do that now.
Before you ask, none of the thumbnails are corrupted as they work perfectly on the PC version of RetroArch. Also, they came from here manually, and are verbatim.
I did not enable save state thumbnails, because they are in play when "volatile" save data is around and I did not want to "poke the bear" so to speak.
Edit: Forgot to mention. Just checked my system time; it is correct and up-to-date. The time in RetroArch is always exactly 4 hours ahead of my system time. Can this be synced to System Time directly instead of however it's derived now?
Thank you to everyone for all of their work on this. It's been a long road, but I think I finally see a stable light at the end of the tunnel.
If you have an improperly set playlist entry it will crash upon loading. Obviously this can simply be fixed by properly configuring the playlist, but it does indeed crash and take the whole system.
Also, if you enable thumbnails at all, and I'm aware that others on here have had this issue - I assure you it's not an SXOS specific issue as I have never used and do not use SXOS - it can turn thumbnails black, allow you to do whatever you want, and then crash 100% of the time no matter what you select next. I would imagine this is very repeatable on just about any build, although it took me several minutes of flipping through thumbnails to trigger. I surmise disabling thumbnails completely would make this very stable; I believe I will do that now.
Before you ask, none of the thumbnails are corrupted as they work perfectly on the PC version of RetroArch. Also, they came from here manually, and are verbatim.
I did not enable save state thumbnails, because they are in play when "volatile" save data is around and I did not want to "poke the bear" so to speak.
Edit: Forgot to mention. Just checked my system time; it is correct and up-to-date. The time in RetroArch is always exactly 4 hours ahead of my system time. Can this be synced to System Time directly instead of however it's derived now?
Seconded. If it would simply fail and push you back to homebrew or Horizon that would be amazing. How possible is it to do this right now without some weird workaround?
Thank you to everyone for all of their work on this. It's been a long road, but I think I finally see a stable light at the end of the tunnel.
Last edited by bluedart,
Just thought I'd leave this here in case somebody else runs into the same problem I did.
I installed RetroArch on a fresh install of Reinx on firmware 6.0.1 (A few Nintendo accounts had been linked and WiFi was enabled but other than that and the fimware upgrade, the Switch was basically brand new) and tested a game or two and everything was working fine. I opened the Video settings menu just to peek at what was in there and I'm pretty sure I didn't change anything. Immediately after exiting the Video settings menu the backlight started flickering really bad. I got really worried when the flickering continued even after I exited RetroArch and went back to the Horizon menu. Power cycling didn't fix the problem. Booting into the OFW didn't fix the problem. I searched around online but couldn't find anybody else reporting the same problem. There were a couple people stating it might have to do with the battery and let it completely drain then recharge but nothing stating what caused it to start happening. Luckily, I did find a program in the homebrew app store named ScreenTester-NX. Using that program, I was able to have it run through the rapid color change mode for a bit and that seems to have fixed the flickering problem. Thanks Marice Lamain (the author of that package), I was close to restoring my NAND backup and returning this console back to the store.
I installed RetroArch on a fresh install of Reinx on firmware 6.0.1 (A few Nintendo accounts had been linked and WiFi was enabled but other than that and the fimware upgrade, the Switch was basically brand new) and tested a game or two and everything was working fine. I opened the Video settings menu just to peek at what was in there and I'm pretty sure I didn't change anything. Immediately after exiting the Video settings menu the backlight started flickering really bad. I got really worried when the flickering continued even after I exited RetroArch and went back to the Horizon menu. Power cycling didn't fix the problem. Booting into the OFW didn't fix the problem. I searched around online but couldn't find anybody else reporting the same problem. There were a couple people stating it might have to do with the battery and let it completely drain then recharge but nothing stating what caused it to start happening. Luckily, I did find a program in the homebrew app store named ScreenTester-NX. Using that program, I was able to have it run through the rapid color change mode for a bit and that seems to have fixed the flickering problem. Thanks Marice Lamain (the author of that package), I was close to restoring my NAND backup and returning this console back to the store.
Similar threads
- No one is chatting at the moment.
-
@
Sonic Angel Knight:
Or, I also heard that if you use flash memory, it can act as more "RAM" at least windows tell me when I stick a flash drive into it. -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
@
K3Nv2:
I can think of the design teams process another joystick and no audio or a joystick and mono audio -
-
-
-
-
-
-
-
-
