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
Homebrew RetroArch Switch
- Thread starter ShadowOne333
- Start date
- Views 1,874,438
- Replies 9,158
- Likes 96
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
- Joined
- Jan 21, 2014
- Messages
- 210
- Trophies
- 1
- Age
- 33
- Location
- Dinosaur Land, Donut Plains
- XP
- 1,268
- Country
Well, mine is freezing when I try to open the menu...Tested it with TLoZ - OOT, it seems to have some graphical issues that was not present before. Altough I haven't seen any graphics issues in game.
Only during the N64 logo and title screen
Nice to hear that this one should have better compatibility with some games though
Edit: Deleted my config and everything is working... Just has that weird blur effect in some games...
Last edited by eldavo2090,
, Reason: Fixed it
D
Deleted User
Guest
Sounds like people are having quite a few issues with the new build.
What are the different settings?
What are the different settings?
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
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,
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.
Last edited by FanboyKilla,
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
Last edited by m4xw,
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.
Like I said, it's just some settings you need to adjust.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.
Btw no drops in the menu in handheld @720p with optimized settings
Last edited by m4xw,
Which setting/s do I need to change to workaround the white background I'm getting with FBEmu On?
Told ya, one of the depth and/or colorbuffer options.
This looks like u have color buffer to rdram off
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"
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"
Figured it out, it was the "GPU shader depth write" setting! Changing this to "False" resolved the issue for me. Now it's working fine WITH or WITHOUT Color/Depth to RDRAM on/off.
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: False
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,
:-/ 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.
Ok I will test it out myself and see what happens. I'll post back and let you know what I find.
D
Deleted User
Guest
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?
m4xw I am curious. In docked how do you prefer the zelda games. With 16:9 or 16:9 adjusted?
Looks like someone should start collecting config files for good per-game settings.
Looking forward to trying out the updated core.
Looking forward to trying out the updated core.
Similar threads
- No one is chatting at the moment.
-
-
-
@
Psionic Roshambo:
One thing that just occurred to me.... The sound on the 2600 sucked less back then the harsh sound we hear now is from infinitely better speakers we have now, back when the 2600 was new speakers produced a almost muffled sound, like CRTs made old graphics look slightly better. -
@
Psionic Roshambo:
I wonder if I could recommend that to some emulation devs that perhaps the sound could use some smoothing out to simulate those old TVs
-
@
Psionic Roshambo:
I think a few of the early systems could benefit from that, at least up to the 8 bit generation, by the 16 bit generation I think TVs had gotten a lot better in almost every way
-
-
-
-
-
-
-
-
-
-
@
Xdqwerty:
it says it only works for the original R4, R4i Gold (r4ids.cn), R4iDSN (r4idsn.com) and Acekard R.P.G. -
-
-
-
-
-
@
Psionic Roshambo:
Just give it a try, but honestly if you have a 3DS you can play DS games without a card just off the internal SD card
-
-
-
-
