Homebrew RELEASE VBA-next for Switch(works 4.1)

[notimp]

Your typical millennial solution. You do you.

The other way to go about this would be to actually make the issue visible enough, that some of the devs looks in detail whats causing it - forwards it to the libnx team.

Also - all those words that impressed you so much, total uneducated guesses, not worth the bit that are used to produce them here..

But its important to know, that this is an issue with many libnx ports, or so it seems.

 

[sora10pls]

The build does fix the audio for some games. Pokemon Fire Red is not fixed, but sm advance 3 is fixed now. Thanks.

FireRed, in addition to the other Gen 3 Pokémon games and Pokémon Mystery Dungeon: Red Rescue Team, work fine for me... huh.

 

[DiJornios]

MY GOD ITS LIKE NIGHT AND DAY FINALLY

 

[notimp]

Also to every millenial posting about sound ISSUES - could you please be descriptive - at all?

You don't share what build you are using, neither what firmware, neither what the issue is , neither if frameskip helps,....

Every report is literally in the vast gap between "totally imagined - non existant issue" to 1/3 of a frame lag, every second, to "entirely stuttery" - so something is up.

Again, most people in here dont read the postings, arent able to download the most recent version from a github repo, or an experimental build. Giving great descriptions like "it works now", .. what? Exactly? How... I mean? Words?

 

[GalaxyYT]

FireRed, in addition to the other Gen 3 Pokémon games and Pokémon Mystery Dungeon: Red Rescue Team, work fine for me... huh.

Are you on 5.0.2? I'm still pretty sure the issues are firmware based since so many people are having different results.

 

[notimp]

MY GOD ITS LIKE NIGHT AND DAY FINALLY

What version where you on prior to this, what firmware are you on.. anything?

No? Service? Can someone link me to "just works"? Argl. Even I don't know whats going on anymore...


Either everyone failed to download 0.2 in the first place -or this is an issue with 5.x.x that got fixed by the test build, are the most promising guesses...

I don't know about others in here, but I'd actually be interested in reports that are not just "it haz works, finally - BYE!"

 

[sora10pls]

Are you on 5.0.2? I'm still pretty sure the issues are firmware based since so many people are having different results.

I am indeed on 5.0.2.

 

[GalaxyYT]

I am indeed on 5.0.2.

Aaand now fire red's audio is fine. wot da fuk

 

[DiJornios]

Apologies, on 5.0.2 sound was there but more distorted than a walkie talkie for version .2 of, the emulator the one I was linked to fixed it and now it’s pretty clear!

 

[Cencil]

Your typical millennial solution. You do you.

Millennial?

 

[DiJornios]

Also I was testing solely on Sonic Advance and Mother 3 (Translated File)

 

[notimp]

Apologies, on 5.0.2 sound was there but more distorted than a walkie talkie for version .2 of, the emulator the one I was linked to fixed it and now it’s pretty clear!

Thank you, that made it somewhat clear.

Also - we've now progressed a page with celebration, so the "crash on dock" issue (many of the libnx emulators are experiencing) got burried again. Maybe the seventh time we'll bring it up, we have more luck and it won't be overlooked anymore.. Hint - someone really should look into this.

 

[Cencil]

Thank you, that made it somewhat clear.

Also - we've now progressed a page with celebration, so the "crash on dock" issue (many of the libnx emulators are experiencing) got burried again. Maybe the seventh time we'll bring it up, we have more luck and it won't be overlooked anymore.. Hint - someone really should look into this.

Hence why I brought it up

 

[ownedlol]

Thank you, that made it somewhat clear.

Also - we've now progressed a page with celebration, so the "crash on dock" issue (many of the libnx emulators are experiencing) got burried again. Maybe the seventh time we'll bring it up, we have more luck and it won't be overlooked anymore.. Hint - someone really should look into this.

Your overexcessive ranting and double posting certainly doesn't help.

 

[GhostlyCrowd]

Thank you, that made it somewhat clear.

Also - we've now progressed a page with celebration, so the "crash on dock" issue (many of the libnx emulators are experiencing) got burried again. Maybe the seventh time we'll bring it up, we have more luck and it won't be overlooked anymore.. Hint - someone really should look into this.

Best way to have a bug addressed is to submit the issue on github.

 

[notimp]

Yes, lets make this a thread about talking about each others feelings about how each person in here behaved. We've already had two pages of entirely uneccessary postings - theres still room.


To sumerize.

3.0.0 and 4.1.0 users seem seem to have "good" sound performance even on v0.2
5.x.x users report, that they had to update to the test build a few pages ago, to get similar results.

 

[Deletedmember448668]

Also to every millenial posting about sound ISSUES - could you please be descriptive - at all?

You don't share what build you are using, neither what firmware, neither what the issue is , neither if frameskip helps,....

Every report is literally in the vast gap between "totally imagined - non existant issue" to 1/3 of a frame lag, every second, to "entirely stuttery" - so something is up.

Again, most people in here dont read the postings, arent able to download the most recent version from a github repo, or an experimental build. Giving great descriptions like "it works now", .. what? Exactly? How... I mean? Words?

How old are you?

 

[Cencil]

Yes, lets make this a thread about talking about each others feelings about how each person in here behaved. We've already had two pages of entirely uneccessary postings - theres still room.

No one's talking about anyone's feelings. You sort of came out of no where with a stick up your ass.

 

[notimp]

Best way to have a bug addressed is to submit the issue on github.

Eh, Ill just raise that "crashes while docking" is an issue with several libnx based ports 10, or 15 times, and someday someone will look at it and forward an error report to the libnx team, that they could do something with. That way we strengthen the "an empty bugtracker doesnt mean, that people dont have issues with your project" notion in devs.. (I do file bug reports, but it is had to do so, when you have no inkling in what library, or module might be responsible. It would be great, if issues afhecting almost all ports out there currently wouldnt have to be solved by every dev separately - is something that also just came to mind. )

And Im not sure if I can adequatly "upstream" the issue.

 

[senas8]

is there a way to play in full screen and add maybe a bilinear effect? its a little blocky. But it runs really well. Nice job. im on 4.1.