RetroArch Switch

Discussion in 'Switch - Emulation, Homebrew & Software Projects' started by ShadowOne333, Dec 30, 2017.

  1. Milenko

    Milenko GBAtemp Advanced Maniac

    Member
    9
    Oct 16, 2017
    Australia
    I'm pretty sure I did, when it did show up as a different name it was just the corename.nro not what I called it and it would crash retroarch

    I'll retry after work in a few hours
     
  2. eldavo2090

    eldavo2090 GBAtemp Regular

    Member
    4
    Jan 21, 2014
    Mexico
    Dinosaur Land, Donut Plains
    Well, mine is freezing when I try to open the menu...
    Edit: Deleted my config and everything is working... Just has that weird blur effect in some games...
     
    Last edited by eldavo2090, Mar 16, 2019 at 2:17 AM - Reason: Fixed it
  3. FanboyKilla

    FanboyKilla GBAtemp Regular

    Member
    1
    Mar 9, 2019
    United States
    When was it crashing? When you tried to start a game?
     
    Last edited by FanboyKilla, Mar 16, 2019 at 2:25 AM
  4. seanp2500

    seanp2500 GBAtemp Advanced Fan

    Member
    5
    Jun 2, 2010
    United States
    Naw when you shoot the gun like immediately
     
  5. regnad

    regnad Button Masher

    Member
    7
    May 19, 2008
    Sounds like people are having quite a few issues with the new build. :(

    What are the different settings?
     
  6. Milenko

    Milenko GBAtemp Advanced Maniac

    Member
    9
    Oct 16, 2017
    Australia
    When I tried to load the core, it was working before I renamed it and made the .info so I know its something I did
     
  7. m4xw

    m4xw Ancient Deity

    Member
    14
    May 25, 2018
    Germany
    No they don't.
    The mitigation only affects stuff that would crash otherwise, so far the Issue reports are layer 8.
    Some FBEmu stuff has changed, in fact so much was rewritten that a rebase wasn't possible anymore (hence why I had to port the plugin fully again).
    If you get some black bars (in intro), its fbemu.
    Overscan options also only work with FBEmu on.
    If you get actual black bars ingame, you can set the overscan options for each game, eliminating them completely.
    Also there are no "different settings" per se. It changed a lot on a game by game basis, whats required (as it always was)

    Sounds like your history pointed to smth that didnt exist.
     
    Last edited by m4xw, Mar 16, 2019 at 2:37 AM
    lordelan likes this.
  8. FanboyKilla

    FanboyKilla GBAtemp Regular

    Member
    1
    Mar 9, 2019
    United States
    Here are some screenshots taken from the Game Menu of LoZ - OOT. (See Spoiler Below)
    - RetroArch Nightly 2019-03-15
    - Core: indi_fix_mupen64plus_next_libretro_libnx
    - Core: mupen64plus_next_libretro_libnx_svc (3/7/2019)
    - With the exception of "Framebuffer Emulation" I'm using the Default settings for each core.

    If Framebuffer Emulation is Off, then performance is great, but there are graphical issues in the Game Menu.
    If Framebuffer Emulation is On, then the graphical issues go away in the "SVC Build" but in not the "indi_fix GlideN64 Build".
    Graphical issues aside, the performance is awful with Framebuffer Emulation On. There's a lot of audio glitching/delays when flipping thru the game menu, as well as sputtering and audio delays while playing the game.

    Warning: Spoilers inside!
     
    Last edited by FanboyKilla, Mar 16, 2019 at 2:41 AM
    lordelan likes this.
  9. m4xw

    m4xw Ancient Deity

    Member
    14
    May 25, 2018
    Germany
    Color/Depthbuffer (these are fbemu settings).
    For perf Lower your resolution or overclock/dock (there is a perf drop while the menu is open tho, legacy blending helps a lot too).
    As i said, lots of options have been changed internally.
    This pulls in several years of development.

    That's OoT running at 1080 in handheld.
    Just barely drops in the menu at 460MHz

    2019031603423700-F1C11A22FAEE3B82F21B330E1B786A39.
     
    Last edited by m4xw, Mar 16, 2019 at 2:45 AM
    lordelan likes this.
  10. FanboyKilla

    FanboyKilla GBAtemp Regular

    Member
    1
    Mar 9, 2019
    United States
    Oh I can tell! These builds are clearly far superior to the builds that RA ships with. These other little issues are minor IMO and I have no problem working around them and still enjoying the game. Just wanted you to be aware though just for future coding changes. :)
     
    lordelan likes this.
  11. m4xw

    m4xw Ancient Deity

    Member
    14
    May 25, 2018
    Germany
    Like I said, it's just some settings you need to adjust.
    Btw no drops in the menu in handheld @720p with optimized settings
     
    Last edited by m4xw, Mar 16, 2019 at 2:48 AM
  12. FanboyKilla

    FanboyKilla GBAtemp Regular

    Member
    1
    Mar 9, 2019
    United States
    Which setting/s do I need to change to workaround the white background I'm getting with FBEmu On?

    [​IMG]
     
  13. m4xw

    m4xw Ancient Deity

    Member
    14
    May 25, 2018
    Germany
    Told ya, one of the depth and/or colorbuffer options.
    This looks like u have color buffer to rdram off
     
    FanboyKilla and ShadowOne333 like this.
  14. jpsondag

    jpsondag Newbie

    Newcomer
    1
    Feb 14, 2011
    United States
    Has anyone found a magical config-incantation to get Dr. Mario 64 to work?

    The ColorBuffer ToRDRam seems to be related but combinations of settings give me:

    1) Pills visible [with glitches] + no background
    2) Background no pill
    3) Garbled background, no pill

    There were definitely bugs in the past regarding dr. mario but I believe fixes should be available in mupen64plus-next branch:

    See github mupen64plus-core/pull/477 "Fix FB Info"
     
  15. FanboyKilla

    FanboyKilla GBAtemp Regular

    Member
    1
    Mar 9, 2019
    United States
    Figured it out, it was the "Less accurate blending mode"setting! Changing this to "False" resolved the issue for me. Now it's working fine WITH or WITHOUT Color/Depth to RDRAM on/off. B-)

    On another note, could you please explain to me what the hell the difference is between "Aspect Ratio" (16:9) and (16:9 adjusted)? I'm looking at the Mpuen64plus Doc's on libretro and GitHub, and neither of them mention exactly what the difference's are.

    Try these...
    Framebuffer Emulation: On
    Color buffer to RDRAM: Async
    Depth buffer to RDRAM: Software
    Less accurate blending mode: True
    GPU shader depth write: False

    Make sure you "Close Content" after making these changes and then reload the game. Don't just try to "Restart".
     
    Last edited by FanboyKilla, Mar 16, 2019 at 3:32 AM
    eldavo2090 likes this.
  16. jpsondag

    jpsondag Newbie

    Newcomer
    1
    Feb 14, 2011
    United States
    :-/ no luck for me. With these settings you see the pills and background is ungarbled. I may have a bad base-config I have one that m4xw uploaded awhile ago, is there a new base config coupled with the glide64 release? In the release I only saw a link for an "Old Glide 64" config.
     
  17. FanboyKilla

    FanboyKilla GBAtemp Regular

    Member
    1
    Mar 9, 2019
    United States
    Ok I will test it out myself and see what happens. I'll post back and let you know what I find.
     
  18. tabnk

    tabnk GBAtemp Regular

    Member
    4
    Jan 20, 2016
    United States
    New Glide 64 3.0 improve performance for Banjo-Tooie :)
     
    Broduskii likes this.
  19. seanp2500

    seanp2500 GBAtemp Advanced Fan

    Member
    5
    Jun 2, 2010
    United States
    yeah we all need to work together on settings testing.

    m4xw I am curious. In docked how do you prefer the zelda games. With 16:9 or 16:9 adjusted?
     
  20. hippy dave

    hippy dave BBMB

    Member
    13
    Apr 30, 2012
    United Kingdom
    Looks like someone should start collecting config files for good per-game settings.

    Looking forward to trying out the updated core.
     
Loading...