Homebrew RELEASE Development Thread - RetroArch libnx

[wicksand420]

Three questions:

1. 4DO crashes the Switch with the Yabause config, modified with the BIOS loaded, as well as VSync off and threading on. Any fix or specific configuration needed to work?
2. Any hope for a compiled build of Mednafen-PSX without the fullscreen hack on by default?
3. Shouldn't anyone be working on why the current build of Yabause doesn't work?

I'd say that the more labor intensive cores should not be worked on now, get the basic ones established then work on the labored ones

 

[CatmanFan]

I'd say that the more labor intensive cores should not be worked on now, get the basic ones established then work on the labored ones

I think M4xw already has a private repo of Mednafen-PSX somewhere on his hard drive, lol
What we should begin with is (no surprise) the 4DO issue, I guess.

 

[DollyWhipDoll]

Lmfao haha I guess we all have are terminology we use to refer to our graphics card.

It's an MSI GP62MVR

That's the laptop check out the specs.

https://www.msi.com/Laptop/GP62MVR-6RF-Leopard-Pro.html

Has great specs but probably should have held off for the 7th gen processor, would have gotten far more battery life.

Is this yours? That setting doesn't look familiar. Sounds like you. I didn't watch the whole thing.

 

[m4xw]

@m4xw I think I fixed the root cause. Patch provided if you want to apply. Testing looks good on my side.

(I knew I didn't lose my T&F skillz that quickly)

FYI: this patch should fix all cores; not sure if it's entirely related but even the retroarch menu seems to respond much better now

tldr; the current input mechanism only recognizes buttons pushed at the precise time they're polled resulting in potential lost input. This patch ensures buttons pressed leading up to the poll within a frame cycle are not dropped => much better responsiveness in games

EDIT: dpad was messed up on the first patch, 2nd patch fixes that!

Thats great! Is the actual fix the | with hidKeysHeld?
Because AFAIK inputs should only be polled once every frame. (I am at work currently, cant check out the func/macro)

Could you try without the fix and change input polling type to early or normal rather than late, anyway that looks good to me, just curious.
This is honestly the first 3rd party fix for my code... finally...
Anyway your's is way cleaner so I like it. Could I maybe ask you to look at multiplayer support /2nd player
Should be easy

Three questions:

1. 4DO crashes the Switch with the Yabause config, modified with the BIOS loaded, as well as VSync off and threading on. Any fix or specific configuration needed to work?
2. Any hope for a compiled build of Mednafen-PSX without the fullscreen hack on by default?
3. Shouldn't anyone be working on why the current build of Yabause doesn't work?

1. No Idea

2. I have the nro, you gotta wait 10h at least

3. No, who gives a fuck? If you don't see the Issue here https://git.m4xw.net/Switch/RetroArch/RetroArch/boards you can be sure I am not gonna work on that anytime soon.

Not like I get paid for giving you free shit. I've been working non stop in my free time to make this possible.

I would lie if I tell you my private life is not suffering, so... maybe practice for u.

Sorry but this "shouldn't", I really dislike the tone

I'd say that the more labor intensive cores should not be worked on now, get the basic ones established then work on the labored ones

+1

I think M4xw already has a private repo of Mednafen-PSX somewhere on his hard drive, lol
What we should begin with is (no surprise) the 4DO issue, I guess.

That doesn't make any sense, so no.

 

[stinkoman]

I think M4xw already has a private repo of Mednafen-PSX somewhere on his hard drive, lol
What we should begin with is (no surprise) the 4DO issue, I guess.

Lol why? 3DO emulation is probably the last thing on anyone's mind. It makes more sense to get stable NES, SNES, Genesis, etc. done before moving onto some weird shit.

 

[m4xw]

Lol why? 3DO emulation is probably the last thing on anyone's mind. It makes more sense to get stable NES, SNES, Genesis, etc. done before moving onto some weird shit.

Idk why people wanna focus on fixing cores when there isn't a stable build that runs with good performance yet (non threaded).

I bet that 90% of all issues are caused by retroarch code, not the cores (with a few exceptions)

Literally any config or performance issue is retroarch (leading up to this point), not the cores (except psx)

 

[Trunks2304]

2. I have the nro, you gotta wait 10h at least

That's exciting! Not sure why any1 wouldn't want it in fullscreen though..looks amazing on the first psx release in fullscreen imo

 

[m4xw]

That's exciting! Not sure why any1 wouldn't want it in fullscreen though..looks amazing on the first psx release in fullscreen imo

Oh its still fullscreen right now on this version (had some issues, don't really feel like fixing that)
spoiler: performance feels the same, I would prefer using the already released version myself

 

[SeongGino]

We REALLY should keep the pace going in working on having a sound backbone for all the other cores to work on, rather than adding more superfluous cores when RA itself is barely working on a thread (haaa!).
ALSO THRILLED IF THE INPUT POLLING HAS BEEN FIXED AHHHH

 

[m4xw]

We REALLY should keep the pace going in working on having a sound backbone for all the other cores to work on, rather than adding more superfluous cores when RA itself is barely working on a thread (haaa!).
ALSO THRILLED IF THE INPUT POLLING HAS BEEN FIXED AHHHH

Not live yet tho.

Will be home in 4h

 

[SeongGino]

Not live yet tho.

Will be home in 4h

I'll be waiting anxiously for it.

Nah, I'll be patient enough -- whenever you get to it.

 

[lifajucejo]

Thats great! Is the actual fix the | with hidKeysHeld?
Because AFAIK inputs should only be polled once every frame. (I am at work currently, cant check out the func/macro)

It's actually the call to hidKeysDown that fixed the buttons, the hidKeysHeld fixed the dpad so events are registered if it's held down.

I doubt changing the polling type in retroarch will help as I reproduced the issue outside of retroarch separately but I agree it should be confirmed:

I won't be home for another 10 hours but your suggestion can be tested by anyone here with the existing fceumm build: load up Track & Field for NES and see how high you can register the cm/sec. Try the options @mx4w mentioned and see if you can sustain 800+ (I got stuck around 350-450).

Sent from my Pixel XL using Tapatalk

 

[m4xw]

It's actually the call to hidKeysDown that fixed the buttons, the hidKeysHeld fixed the dpad so events are registered if it's held down.

I doubt changing the polling type in retroarch will help as I reproduced the issue outside of retroarch separately but I agree it should be confirmed:

I won't be home for another 10 hours but your suggestion can be tested by anyone here with the existing fceumm build: load up Track & Field for NES and see how high you can register the cm/sec. Try the options @mx4w mentioned and see if you can sustain 800+ (I got stuck around 350-450).

Sent from my Pixel XL using Tapatalk

Ah yea I missread that. I thought I read "keys that have been pressed since the last frame" not held down.

 

[Phenj]

Maybe this is old, but saves don't work in VBA-next

 

[Trunks2304]

Maybe this is old, but saves don't work in VBA-next

Yes they do. Update to latest

 

[m4xw]

Maybe this is old, but saves don't work in VBA-next

Close content

 

[Phenj]

Yes they do. Update to latest

I've downloaded the build from the main post.

--------------------- MERGED ---------------------------

Close content

well

 

[m4xw]

The cores are just being rebuilt right now.

You can check the status on the main post. This is the Input fix ! Ping @SeongGino

 

[Fadi5555]

The cores are just being rebuilt right now.

You can check the status on the main post. This is the Input fix ! Ping @SeongGino

Please is there any fix for 3.0.0?

 

[m4xw]

Please is there any fix for 3.0.0?

There is nothing wrong on 3.0 with the stable builds.

Threading is WIP, won't work until its ready. Stop asking.

It only delays it if I have to take the time to answer.