Homebrew RetroArch Switch

  • Thread starter Thread starter ShadowOne333
  • Start date Start date
  • Views Views 2,166,802
  • Replies Replies 9,226
  • Likes Likes 100
Any solution to this problem in Banjo Tooie?
Banjo-Tooie-190319-104056.png
 
id just change under options per game but he means in your retroarch.cfg for mupen plus next core keyword search mupen

EDIT - Nevermind the below! retroarch-core-options.cfg is the one I wanted


Thanks for the response! So I've tried to get into the in-game menu, but have not found it. On the SD card I found a retroarch.cfg within SD/Retroarch. However, the only mention of Mupen I see is this:
upload_2019-3-18_20-48-17.png


Do I need to just add all those lines from page1 in somewhere?
 
Last edited by Eosos,
This happens because framebuffer emulation needs to be enabled for this game.

I also recommend disabling Color Writes to DRAM and Depth Writes to DRAM to keep the framerate high.

Ugh. Framebuffer emulation makes it drag at half speed.

Edit: disabling those two DRAM settings helps a bunch! Thanks!
 
Last edited by regnad,
Did you figure it out? I just finished setting up thumbs for a few of my cores but I can't get the mame thumbs to show up either? All the other cores are fine.
Yeah, I think our playlist use the old scheme, you need go to playlist settings and set the old list method.
 
  • Like
Reactions: ploggy
It’s normally actually the Color Writes to DRAM and Depth Buffer Writes to DRAM options that are expensive on the CPU. Both only kick in when framebuffer emulation is enabled though, hence the misconception.
 
Which, I guess your saying, isn't the case with Switch?

I don't know. A lot of factors affect it, framebuffer is very hard to emulate perfectly, esp. without increasing system requirements. How well the emulator is optimized, how much the game uses it, IDK
 
First off, you have to delete any previous configuration file you had with any previous Mupen64 build, so that you can start using the new one using a fresh RA generated configuration file to avoid unwanted results.

Next, I recommend to all those people that are using the latest Mupen64 version with the GlideN64 update, to always have Framebuffer enabled so that games suffer from the least glitches possible.
If you still encounter glitches or graphical bugs with Framebuffer ON, then try playing around with the DRAM options (color writes and depth buffer).

Also, I cannot stress this enough, but please try to save your configurations PER-GAME with this new Mupen64 + updated GlideN64 build.
Once you hit the perfect configuration scheme for a certain game, be sure to save said configuration per-game, so that other games are not affected by those changes.

I would also recommend that people start sharing configuration files for conflicting games, so that whenever someone wants to play a certain game, you can simply drag-drop the config for said game and enjoy it right out of the box without having to fiddle around with the settings too much.
 
First off, you have to delete any previous configuration file you had with any previous Mupen64 build, so that you can start using the new one using a fresh RA generated configuration file to avoid unwanted results.

Next, I recommend to all those people that are using the latest Mupen64 version with the GlideN64 update, to always have Framebuffer enabled so that games suffer from the least glitches possible.
If you still encounter glitches or graphical bugs with Framebuffer ON, then try playing around with the DRAM options (color writes and depth buffer).

Also, I cannot stress this enough, but please try to save your configurations PER-GAME with this new Mupen64 + updated GlideN64 build.
Once you hit the perfect configuration scheme for a certain game, be sure to save said configuration per-game, so that other games are not affected by those changes.

I would also recommend that people start sharing configuration files for conflicting games, so that whenever someone wants to play a certain game, you can simply drag-drop the config for said game and enjoy it right out of the box without having to fiddle around with the settings too much.
Good advice all around. Thanks.
 
  • Like
Reactions: ShadowOne333
Alright, I just deleted and re-updated my RetroArch and see the UI is vastly different now. I've enabled Rewinding and set my Rewind and Fastforward settings but where do I go to assign those functions to keys? When I try I can only cycle through the standard buttons, turbo options and a light sensor (this is on GBA). How can I set ZL and ZR to rewind and fast forward?
 
Alright, I just deleted and re-updated my RetroArch and see the UI is vastly different now. I've enabled Rewinding and set my Rewind and Fastforward settings but where do I go to assign those functions to keys? When I try I can only cycle through the standard buttons, turbo options and a light sensor (this is on GBA). How can I set ZL and ZR to rewind and fast forward?
In the Controls options (I think) there should be an option called Hotkey binding or something similar.
That's where you can set the key for Rewind and Fast Forward.

Word of advice though, be careful when enabling any of the two, as some cores do not play well with them.
 
  • Like
Reactions: RetroGenerica
In the Controls options (I think) there should be an option called Hotkey binding or something similar.
That's where you can set the key for Rewind and Fast Forward.

Word of advice though, be careful when enabling any of the two, as some cores do not play well with them.


I've had a few issues with Rewind. Fast forward can be abit finicky but majority of the time it works pretty good
 
  • Like
Reactions: ShadowOne333

Site & Scene News

Popular threads in this forum