Homebrew RELEASE Development Thread - RetroArch libnx

[m4xw]

I never found any stability issues to begin with, just the other day I finished "The Shores of Hell" with no problems.

I remember we had a earlier port that just had some issues.
Wasn't sure if it was you.

 

[ZeroShift]

I remember we had a earlier port that just had some issues.
Wasn't sure if it was you.

Heh no, I saw that post and was honestly curious how there were even issues. Could've been an earlier libnx or RetroArch-nx build issue.

 

[m4xw]

Heh no, I saw that post and was honestly curious how there were even issues. Could've been an earlier libnx or RetroArch-nx build issue.

Thanks for clearing that up

 

[ZeroShift]

Thanks for clearing that up

I forgot to mention, music does work in PRBoom with .MP3 files. I updated my Readme.md with instructions.

 

[SpaceJump]

Alright folks, in other news I have moved @CatmanFan's port of Yabause over to our repo here. MR for CICD integration here. This repo will not be public for a few hours until @m4xw is back.

Attached is the build with threading support just for the kicks – I have not tested it. Consider deleting the config files to avoid freezing.

Wow, Panzer Dragoon Saga actually loads with this, just incredibly slow. Without the cfg file it's doesn't even crash. The screen stays white after the title screen, but you can hear sound effects and music in the background. Nice one

 

[baretbh]

I forgot to mention, music does work in PRBoom with .MP3 files. I updated my Readme.md with instructions.

With this being said, could we potentially make an mp3 player app for the Switch?

 

[m4xw]

With this being said, could be potentially make an mp3 player app for the Switch?

That would be a pretty clunky mp3 player

 

[CatmanFan]

@m4xw I'm not meaning to be rude or idiotic, but I'm still trying to know what CICD means. Continuous Integration Continuous Delivery maybe? What does that have to do with RetroArch?

 

[Starcarr]

@m4xw I'm not meaning to be rude or idiotic, but I'm still trying to know what CICD means. Continuous Integration Continuous Delivery maybe? What does that have to do with RetroArch?

It means that whenever changes are made the cores will be compiled and the zips will be generated without human interaction. This helps to avoid merging changes that break compilation, and once completed it will also allow the team to concentrate in just coding the features/fixes and not worry about generating the zip files for the testers/users.

Currently we have reached a great deal of integration, but there's still some things that need to be connected before we can call it end-to-end.

 

[m4xw]

So guys, I just got home and gonna work on threading fixes.
But I want to ask any of you, what are the most wanted features?

Right now my Priorities are:
-Threading
-Audio
-Dynamic Core loading
-Input losses (probably a easy fix, just polling related)
-UI
-(take a look at aspect/fullscreen)

In that exact order.

 

[Twistedziefer]

So guys, I just got home and gonna work on threading fixes.
But I want to ask any of you, what are the most wanted features?

Right now my Priorities are:
-Threading
-Audio
-Dynamic Core loading
-Input losses (probably a easy fix, just polling related)
-UI
-(take a look at aspect/fullscreen)

In that exact order.

Stretching ^^ .....

 

[baretbh]

So guys, I just got home and gonna work on threading fixes.
But I want to ask any of you, what are the most wanted features?

Right now my Priorities are:
-Threading
-Audio
-Dynamic Core loading
-Input losses (probably a easy fix, just polling related)
-UI
-(take a look at aspect/fullscreen)

In that exact order.

For me it would have to be tearing. Audio is always a huge thing too. Dynamic core loading isnt a huge concern for me, I dont mind opening different "emulators". Fullscreen seems nice too

 

[Twistedziefer]

^

 

[m4xw]

Stretching ^^ .....

So guys, I just got home and gonna work on threading fixes.
But I want to ask any of you, what are the most wanted features?

Right now my Priorities are:
...
-(take a look at aspect/fullscreen)

In that exact order.

 

[baretbh]

Stretching ^^ .....

 

[m4xw]

For me it would have to be tearing. Audio is always a huge thing too. Dynamic core loading isnt a huge concern for me, I dont mind opening different "emulators". Fullscreen seems nice too

Tearing should be fine once threading is fixed
So high prio

 

[baretbh]

Tearing should be fine once threading is fixed
So high prio

Heck yes!!!

 

[SeongGino]

I'd personally prioritize polling fixes (assuming it actually is relatively simple), but otherwise that order sounds just fine~

 

[m4xw]

@m4xw How long do you think it will take to fix it? Few hours maybe? Or a day or two?

Not gonna comment on this

I'd personally prioritize polling fixes (assuming it actually is relatively simple), but otherwise that order sounds just fine~

So right now the Input is polled by Retroarch once per frame but it seems to query the buttons more often (might be for more controllers?)
Does it make sense to pull inputs mid frame (or rather when it queries the buttons, its not done like that in other ports as far i see tho?) I think the input losses are just when you press and leave inputs faster than once per frame

 

[Zumoly]

So guys, I just got home and gonna work on threading fixes.
But I want to ask any of you, what are the most wanted features?

Right now my Priorities are:
-Threading
-Audio
-Dynamic Core loading
-Input losses (probably a easy fix, just polling related)
-UI
-(take a look at aspect/fullscreen)

In that exact order.

I'd say:
-Dynamic Core loading
-(take a look at aspect/fullscreen)
-UI
-Threading
-Audio (still using early & most stable version of Snes which looks fine for me)
-Input losses (not experiencing those personally)