Emulation Emulator NetherSX2 - Switch Port

  • Thread starter Thread starter Nagaa
  • Start date Start date
  • Views Views 8,699
  • Replies Replies 68
  • Likes Likes 37
It is in exfat already. The games need to be in a specific folder?
No it can be put anywhere since you should be able to navigate in any folder on your HDD, can you try with a usb flash drive instead ? maybe the USB doesn't power enough the HDD

you think performance will be better in the long run? if so , i know its a hard question but how much more could we gain performance wise with improvements? that is if you plan to continue supporting this project with your amazing effort, of which we're not thankful enough
As explained here : https://github.com/NaGaa95/NetherSX2_nx/issues/7
No performance improvement is to be expected, now that fastmem is implemented it's nearly on par with what you can get by running it on Android / Linux
 
  • Like
Reactions: baobao43 and nWo
No it can be put anywhere since you should be able to navigate in any folder on your HDD, can you try with a usb flash drive instead ? maybe the USB doesn't power enough the HDD


As explained here : https://github.com/NaGaa95/NetherSX2_nx/issues/7
No performance improvement is to be expected, now that fastmem is implemented it's nearly on par with what you can get by running it on Android / Linux
aight thanks man, i gotta say the android build is still significantly better for me, even with max OC,plays BT3 full speed no issue
 
  • Like
Reactions: nWo
Can someone explain in detail how to set up cover art manually please ? Putting 600*900 jpg or png files in the cover folder doesn't work for me.
 
kgjhhkj
NetherSX2 - Nintendo Switch port

This is a wrapper/port of the Android version of NetherSX2.
It loads the original Android emulator core, patches it and runs it.
It's basically as if we emulate a minimalist Android environment in which we natively run the original Android binary as is.

Features​

  • Cover art — auto-download from SteamGridDB (one game or the whole library)
  • Region flags (US / EU / JP) and a sortable library
  • Per-game settings — override any option per title; rename and delete games
  • Full controller remapping, stick config, deadzone, and vibration
  • Resolution scaling up to 6× (4K), aspect ratio, widescreen / no-interlace patches,
    shade boost, CRT/TV shaders, and the full graphics / enhancement / audio option set
  • Experimental network adapter (DEV9 / Sockets) — off by default, opt-in in Settings → Network

Renderers​

Choose in Settings → Graphics → Renderer:
  • Vulkan (NVK) — recommended; best compatibility and performance in most games
  • OpenGL — alternative if a game misbehaves under Vulkan

Cores​

Choose in Settings → Emulation / System → Core version:
  • Patched (4248) — The most recent one
  • Classic (3668) — an older build; Can get better performance on less powerful devices

Credits :
  • The AetherSX2 / PCSX2 developers for the emulator.
  • The NetherSX2 maintainers for the patched Android builds.
  • fgsfds for the Switch so-loader groundwork reused here.
  • TheOfficialFloW for the original Android so-loader lineage.
  • Dantiicu - Switch Vulkan driver.
  • Slluxx - IconGrabber.

Available here :
https://github.com/NaGaa95/NetherSX2_nx


Amazing!

EDIT: Can someone test Shaolin Monks in docked mode with sys-clk overclocking enabled, if possible? I'd like to know how much it improves performance.
1784576753878.png

Post automatically merged:

I just tested God Hand and Urban Reign (default settings), and neither is getting good frame rates. Are there any settings you'd recommend using?
 
Last edited by dragonz,
It runs bad for me - however I'm totally confused because I just found out my switch OC does not go as high as the Nagaa's OC youtube video test.

CPU 19XX, GPU 12XX, and RAM 22XX on the his Switch. I’m really curious how you guys managed to get those overclock values.

On every standard setup I’ve seen, SysClk and Horizon OS cap the hardware at:

  • CPU max around 1785 MHz
  • GPU max around 921 MHz
  • RAM fixed at 1600 MHz
So I’d love to understand how you guys were able to push past those limits. Were you using a custom SysClk fork, kernel patches, or something else entirely?
 

Site & Scene News

Popular threads in this forum