L4T Lakka Switch - now with audio and Vulkan

enderer · Aug 28, 2019

so can i just update cores individually to get touch controls for light gun games (1.7.8)? or do i have to wait for an official lakka update?

Csmrcc · Aug 28, 2019

enderer said:
so can i just update cores individually to get touch controls for light gun games (1.7.8)? or do i have to wait for an official lakka update?

Wait

Turnbl · Sep 6, 2019

Turnbl said:
I tried some more testing tonight - no joy.

So I tried another SD card - a 32GB Samsung Evo - this allowed me to format using Windows itself rather than guiformat, I tried 8192 & 64 size sections. I also tried the SD card not named LAKKASD in case there was a weird conflict.

Gamecube, Dreamcast & MAME games all crash out to retroarch menu like you say with a black x cursor on the screen, after 2-2.5 minutes.

All that was with a copy of the file structure on my also not working 400GB sd card. So next I’ll try the same again with a fresh new Lakka copy from windows. After that I don’t really know what else to try? It’s not bios files. It’s not rom files. I can’t imagine it’s the sd card makes or sizes.

Does anybody know if retroarch game crash errors are stored to log files?

So I've tried re-installing from scratch again on the Samsung EVO 32GB. I've updated 7z in case that was causing an issue unpacking the release (v18.05>v19).

Still the same issue exists - after around 2 to 2.5 mins play on any game/core the game will exit to the Retroarch menu with a black cross on black background.

This includes Dreamcast (with bios under system\DC), GameCube (no bios), MAME2003 and MAME2010.

I also wondered if it was network related so I've connected to wifi within retroarch just in case - no change, still the same problem.

My final extra clue found tonight is this could be not game related - if i'm navigating the retroarch menu for a few minutes - the same black cross/background crash can happen, which then recovers to the retrorarch menu.

This still could be micro SD card related (only 2 tried), network related (is Retroarch making calls out that are unhandled?), or hardware related (do i have a random version of the Switch with a bad part or revision?)

Any ideas anybody? Is there any local logging to give more clues as to the crash?

EmulateLife · Sep 6, 2019

Seems to be the sd card to me. Have you tried abother card?

Nm I see in your post you quoted you tried that. No clue then.

Csmrcc · Sep 6, 2019

Turnbl said:
So I've tried re-installing from scratch again on the Samsung EVO 32GB. I've updated 7z in case that was causing an issue unpacking the release (v18.05>v19).

Still the same issue exists - after around 2 to 2.5 mins play on any game/core the game will exit to the Retroarch menu with a black cross on black background.

This includes Dreamcast (with bios under system\DC), GameCube (no bios), MAME2003 and MAME2010.

I also wondered if it was network related so I've connected to wifi within retroarch just in case - no change, still the same problem.

My final extra clue found tonight is this could be not game related - if i'm navigating the retroarch menu for a few minutes - the same black cross/background crash can happen, which then recovers to the retrorarch menu.

This still could be micro SD card related (only 2 tried), network related (is Retroarch making calls out that are unhandled?), or hardware related (do i have a random version of the Switch with a bad part or revision?)

Any ideas anybody? Is there any local logging to give more clues as to the crash?

as i told you this happens to me, i tried like 4 sd cards, no way

i´m starting to think that is because of the hardware somehow different
had you tried having the switch charging while playing?

EmulateLife · Sep 7, 2019

This may be no connection to you guys problems but that happens to me using the Saturn core Yaba Sanshiro only. Almost every game crashes within a few minutes. Every other core that I've tried doesn't crash though so it's probably just a problem with that core.

Silent_Gunner · Sep 7, 2019

EmulateLife said:
This may be no connection to you guys problems but that happens to me using the Saturn core Yaba Sanshiro only. Almost every game crashes within a few minutes. Every other core that I've tried doesn't crash though so it's probably just a problem with that core.

Saturn emulation's better than it's ever been (fuck SSF and having to use Daemon Tools *growls in frustration* and the lack of documentation worse than UNIB's story mode translation), but it's still far from being practical. Case-in-point: the RetroArch core of Yabause (and while we're on the subject of Saturn emulation, the fuck is the difference between this, Yaba Sanshiro, and the beetle core? Which one is generally the best on Windows?) runs 2D games just fine on my ODroid XU4, but the moment anything 3D is rendered, that framerate tanks! And it can run Soul Calibur and other 3D games on DC at a playable framerate, even NAOMI games!

I know, Saturn was such a failure that it was forgotten outside of having a good port of Virtua Fighter 2, the hardware is like having a multi-core CPU in a console before that was the standard, the 3D support wasn't optimized if you weren't making a first party game, there's not much documentation in English about the what all the Saturn can do, etc..

Basketto · Sep 7, 2019

Turnbl said:
So I've tried re-installing from scratch again on the Samsung EVO 32GB. I've updated 7z in case that was causing an issue unpacking the release (v18.05>v19).

Still the same issue exists - after around 2 to 2.5 mins play on any game/core the game will exit to the Retroarch menu with a black cross on black background.

This includes Dreamcast (with bios under system\DC), GameCube (no bios), MAME2003 and MAME2010.

I also wondered if it was network related so I've connected to wifi within retroarch just in case - no change, still the same problem.

My final extra clue found tonight is this could be not game related - if i'm navigating the retroarch menu for a few minutes - the same black cross/background crash can happen, which then recovers to the retrorarch menu.

This still could be micro SD card related (only 2 tried), network related (is Retroarch making calls out that are unhandled?), or hardware related (do i have a random version of the Switch with a bad part or revision?)

Any ideas anybody? Is there any local logging to give more clues as to the crash?

Can i suggest(if you have a friend with an exploitable switch) trying the exact same sd card on his switch in its current state.
Honestly, the only thing I can think of is 1) for some reason your .cfg files are getting corrupted on the initial lakka boot.
2) The hardware inside your switch is somehow causing this issue.

Turnbl · Sep 7, 2019

Csmrcc said:
as i told you this happens to me, i tried like 4 sd cards, no way i´m starting to think that is because of the hardware somehow different
had you tried having the switch charging while playing?

Reading back through your posts I see your Switch revision number starts XAJ7001... mine starts XAJ70001... so could well be a specific hardware issue? Unless anybody else can confirm their Lakka works fine with that revision?

Another clue in case it means anything to anyone - as well as it seems Retroarch itself is crashing periodically in the menu with the black cross and background, before recovering to the menu so possibly not game related - after leaving the device for a bit longer, I have seen Retroarch re-orientate itself to portrait mode (i.e. the text turns 90 degrees like in TATE mode). This remains until i reboot.

A few more questions just to check with everybody:

1) I'm using RCMloader & Hekate. I assume i am payloading correctly by choosing: Launch -> (down twice) More Configs... -> (down once) Lakka?
2) I'm removing the payload & jig after Retroarch menu appears on boot and sliding the right joycon in. Assume this is correct?
3) I can't find specific information anywhere of what cluster the SD card should be formatted to? I'm going to try 32kb a final time.
4) I haven't used the add games method - i've only ever browsed to the game itself in a folder. I shall try this method although I'm not sure this is a requirement?

My current test games are:
Sonic Adventure 2 (DC) - for a bios test
Mario Golf (GC) - for a non bios test on a stable emulator
Frogger (MAME2003) - for a simple lightweight game not maxing the processors

But like I say it's probably not game related now... Unfortunately I don't have a friend with a Switch so can't test my SD image on other hardware.

Csmrcc · Sep 8, 2019

Turnbl said:
Reading back through your posts I see your Switch revision number starts XAJ7001... mine starts XAJ70001... so could well be a specific hardware issue? Unless anybody else can confirm their Lakka works fine with that revision?

Another clue in case it means anything to anyone - as well as it seems Retroarch itself is crashing periodically in the menu with the black cross and background, before recovering to the menu so possibly not game related - after leaving the device for a bit longer, I have seen Retroarch re-orientate itself to portrait mode (i.e. the text turns 90 degrees like in TATE mode). This remains until i reboot.

A few more questions just to check with everybody:

1) I'm using RCMloader & Hekate. I assume i am payloading correctly by choosing: Launch -> (down twice) More Configs... -> (down once) Lakka?
2) I'm removing the payload & jig after Retroarch menu appears on boot and sliding the right joycon in. Assume this is correct?
3) I can't find specific information anywhere of what cluster the SD card should be formatted to? I'm going to try 32kb a final time.
4) I haven't used the add games method - i've only ever browsed to the game itself in a folder. I shall try this method although I'm not sure this is a requirement?

My current test games are:
Sonic Adventure 2 (DC) - for a bios test
Mario Golf (GC) - for a non bios test on a stable emulator
Frogger (MAME2003) - for a simple lightweight game not maxing the processors

But like I say it's probably not game related now... Unfortunately I don't have a friend with a Switch so can't test my SD image on other hardware.

I have the rotation issues too, it's the same my problem and yours.
I though that the updated lakka maybe would fix this but I'm starting to think it's hardware related, and our same serial number supports that option.

Maybe there is no lakka for us unfortunately.

Btw: I also tried Ubuntul4 on switch for playing Wii and gc games and also it installed properly but after that it worked badly like lakka, stopping, being slow. . .

intellettuanale · Sep 8, 2019

Is there a way to update ota?
And a way to run a script on boot?

Shaneus · Sep 9, 2019

intellettuanale said:
Is there a way to update ota?
And a way to run a script on boot?

Cores need to be manually compiled for each release (or something like that) and tested, so there's no online updating... at least for cores. It may be different for shaders/overlays etc.

It's different with Retroarch in Horizon, but not Lakka.

Imancol · Sep 11, 2019

Josshy0125 said:
Hey thanks! So lakka can read the wbfs format?

Ciso better

Basketto · Sep 11, 2019

Ghost92 said:
Ciso better

Ciso is much riskier as it can remove vital data that can outright break games. I guess it depends if you consider more compressed better with much higher risk.

Shaneus · Sep 12, 2019

Not wanting to nag, but what are the chances we'd get the Android/iOS lightgun touchscreen feature implemented into Lakka? I don't know if that's a difficult task or not, or if it's even possible.

Hemboy · Sep 13, 2019

Loving this, great work :bow:

Any ideas why the display isn't switching to my tv when docked though? Is there a display option to toggle somewhere? I can see it should be displaying as the overclock options include those for in the docked state. Any thoughts much appreciated

Jackson98 · Sep 13, 2019

Hemboy said:
Loving this, great work Any ideas why the display isn't switching to my tv when docked though? Is there a display option to toggle somewhere? I can see it should be displaying as the overclock options include those for in the docked state. Any thoughts much appreciated

https://lakka-switch.github.io/documentation/faq.html

Teach a man to fish

JPZ5 · Sep 13, 2019

Anyone having issues with Zelda games and Mupen? It seems to be emulating great, but cannot hit the start button, crashes immediately. Occurs on both OOT and MM. I know this didn't happen on the previous version of Lakka. I just upgraded to the new one, it was an upgrade, not a fresh install. I tried to do some googling but could not find anything specficially that caused it. I also downloaded 3 different versions of both US and EU verions and all crash when clicking start to open the menu.

Basketto · Sep 13, 2019

JPZ5 said:
Anyone having issues with Zelda games and Mupen? It seems to be emulating great, but cannot hit the start button, crashes immediately. Occurs on both OOT and MM. I know this didn't happen on the previous version of Lakka. I just upgraded to the new one, it was an upgrade, not a fresh install. I tried to do some googling but could not find anything specficially that caused it. I also downloaded 3 different versions of both US and EU verions and all crash when clicking start to open the menu.

If you want to use mupen64 mainly, i very strongly suggest the older build of L4T lakka(unless you want to play yoshis story). Using the older lakka release i can promise will fix zelda, (hdperpixel lighting mupen option-as a sidenote), fix conkers bad fur day, and reduces stuttering in a good few games. The plugin breaks zelda with the version you are running.

Purple_Heart · Sep 13, 2019

my hekate says no ini found on bootloader/ini.....there is an ini of lakka

Well-Known Member

Well-Known Member

Member

Well-Known Member

Well-Known Member

Well-Known Member

Crazy Cool Cyclops

Well-Known Member

Member

Well-Known Member

Well-Known Member

Well-Known Member

Otak Productions

Well-Known Member

Well-Known Member

New Member

Well-Known Member

Member

Well-Known Member

GBATemp´s weirdest Individual

Similar threads

Popular threads in this forum