L4T Lakka Switch - now with audio and Vulkan

toxic9 · Jul 30, 2019

Jackson98 said:
I tried to find a solution to this multiple times. Their is no workaround at the moment.
The newer verions of Dolphin emulator have an option called "Trigger Threshhold" that ranges between 1-100% anything below 100% emulates an Analog trigger press. Unfortunately we do not have that option in in Lakka yet. However BBOX and Safe Texture options just got added, so their is hope for the future.

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

Im pretty sure if you use exfat long enough you can definitely corrupt files regardless of what driver. As much as it is a pain transferring everything across and having a 4gb transfer limit(which can be worked around anyway), it isn't worth using exfat. I switched to fat32 never had any regrets. Had 2 SD cards corrupt using exfat, 1 after 6 months and another after several weeks. Ask 95% of the people that use these forums everyone else will tell you the same thing use FAT32 . Ive come to think of using Exfat like contracting SD card HIV, sooner or later it will likely get AIDS and die.

Ok... I change my question...
When NTFS support..?

Jackson98 · Jul 30, 2019

toxic9 said:
Ok... I change my question...
When NTFS support..?

I don't think they are planning either at the moment if not for a very long time or ever. High up on the list are
wireless bluetooth controller support(along with dock)
sleep mode
& Optimising emulators to run well/smoothing out compatibilty problems

Can I ask why you need NTFS support for Lakka? In 59 pages you are literally the only person to request it ;P.

toxic9 · Jul 30, 2019

I don't want ntfs support. I was kidding because everyone talks about exfat corruption, and I'm tired of it.
I just want exfat support. and I don't care about corruption.
what about exfat correction? ..corruption occurs because homebrew code should be improved to make use of it.

PS:
corruption happens when writing a file gets messed up and/or the "TOC" is not updated correctly.
it can happen on every filesystem!
homebrews are well designed to understand "fat32".
so, to use exfat correctly they will need to be designed with that in mind.
fat32 is an obsolete filesystem.
I can't believe we are in 10tb HDD era and still thinking about fat32!
we need to move on, or someday we will have future consoles generation, with games like 100Gb each,
and splitting them on 4Gb files... just to install them! oh boy...

Fenderbendr · Jul 30, 2019

Dave_Chad said:
No you just didn't enable advanced settings

Oh, that was it. thanks

Jackson98 · Jul 30, 2019

toxic9 said:
I don't want ntfs support. I was kidding because everyone talks about exfat corruption, and I'm tired of it.
I just want exfat support. and I don't care about corruption.
what about exfat correction? ..corruption occurs because homebrew code should be improved to make use of it.

PS:
corruption happens when writing a file gets messed up and/or the "TOC" is not updated correctly.
it can happen on every filesystem!
homebrews are well designed to understand "fat32".
so, to use exfat correctly they will need to be designed with that in mind.
fat32 is an obsolete filesystem.
I can't believe we are in 10tb HDD era and still thinking about fat32!
we need to move on, or someday we will have future consoles generation, with games like 100Gb each,
and splitting them on 4Gb files... just to install them! oh boy...

The thing is, with Lakka, Wii games/Gamecube games and also PS2 games can all be compressed below 4GB and still work fine. Their are very few games in Lakka that require being over 4GB in size and the ones that are run like garbage as they are incredibly demanding Wii Games. As for corruption on a FAT32 SD card its pretty unheard of.

toxic9 · Jul 30, 2019

Jackson98 said:
The thing is, with Lakka, Wii games/Gamecube games and also PS2 games can all be compressed below 4GB and still work fine. Their are very few games in Lakka that require being over 4GB in size and the ones that are run like garbage as they are incredibly demanding Wii Games. As for corruption on a FAT32 SD card its pretty unheard of.

I know fat32 is the world's most compatible file system. no doubt about that. it's here to last!
but when the switch came across, exfat became very useful.
I don't use UBS installers at all. I use SD installations, and they are 100% accurate.
I have used 32Gb Sandisk SD card, then 400Gb Sandisk SD card, and now Samsung 512Gb SD card.
Always exfat, and no corruption at all. You can call me lucky, but I don't use all shitty homebrew you can download.
I only use trustworthy Apps.
I would like to use one card for all. so I'm waiting for exfat support.

ZachyCatGames · Jul 30, 2019

toxic9 said:
Will it be possible in the future to add exfat support?

There was a PR for it, but the person who submitted the PR was asked to submit it to the main L4T repos. But they haven't responded since
https://github.com/lakka-switch/Lakka-LibreELEC/pull/51

Jackson98 said:
Im pretty sure if you use exfat long enough you can definitely corrupt files regardless of what driver. As much as it is a pain transferring everything across and having a 4gb transfer limit(which can be worked around anyway), it isn't worth using exfat. I switched to fat32 never had any regrets. Had 2 SD cards corrupt using exfat, 1 after 6 months and another after several weeks. Ask 95% of the people that use these forums everyone else will tell you the same thing use FAT32 . Ive come to think of using Exfat like contracting SD card HIV, sooner or later it will likely get AIDS and die.

exfat certainly isn't perfect, but most of the issues on Switch are caused by Nintendo's buggy FS sysmodule

Jackson98 · Jul 30, 2019

ZachyCatGames said:
There was a PR for it, but the person who submitted the PR was asked to submit it to the main L4T repos. But they haven't responded since
https://github.com/lakka-switch/Lakka-LibreELEC/pull/51

exfat certainly isn't perfect, but most of the issues on Switch are caused by Nintendo's buggy FS sysmodule

Seems likely to me, as both times I've had SD card issues with exfat both have been ones I've used for the switch. I have swapped mine to FAT32 though and never looked back.
I would many times over see Play! running on this than see exfat supported, which realistically offers nothing that can't already been done on FAT32 for lakka

. Sadly the Play! core doesn't seem to wan't to work at all in Lakka. While it works in ubuntu through sudo, through Lakka it is completely busted in its current state.

spotanjo3 · Jul 30, 2019

toxic9 said:
I'm waiting for exfat support.

You are asking the wrong place. Contact Nintendo and ask over there. I doubt they cannot care about it.

toxic9 · Jul 30, 2019

azoreseuropa said:
You are asking the wrong place. Contact Nintendo and ask over there. I doubt they cannot care about it.

Lakka can use its own exfat driver.

spotanjo3 · Jul 30, 2019

toxic9 said:
Lakka can use its own exfat driver.

I am talking about Nintendo's fault exfat driver.

Shaneus · Jul 31, 2019

Has anyone noticed any sound issues with some of the cores? It's been across multiple ones (MAME-2003Plus, Genesis Plus GX) where it sounds like it can't process audio or there's some buffering issue. Going to the XMB and back into the game clears it, but it definitely didn't happen with the last build.

Also, is there a way to try out cores for this that weren't included with the build? I'd like to compare the core I built for Genesis Plus GX with the one included in this release, I'm sure it handled the Nuked audio synth more efficiently/without slowdown.

Basketto · Jul 31, 2019

Shaneus said:
Has anyone noticed any sound issues with some of the cores? It's been across multiple ones (MAME-2003Plus, Genesis Plus GX) where it sounds like it can't process audio or there's some buffering issue. Going to the XMB and back into the game clears it, but it definitely didn't happen with the last build.

Also, is there a way to try out cores for this that weren't included with the build? I'd like to compare the core I built for Genesis Plus GX with the one included in this release, I'm sure it handled the Nuked audio synth more efficiently/without slowdown.

Ya noticed a few sound issues that have cropped up with mupen, and idk if im imagining it either but a couple of games seem to have dropped 1-2 fps aswell, with the new retroarch config.

Jackson98 · Jul 31, 2019

Shaneus said:
Has anyone noticed any sound issues with some of the cores? It's been across multiple ones (MAME-2003Plus, Genesis Plus GX) where it sounds like it can't process audio or there's some buffering issue. Going to the XMB and back into the game clears it, but it definitely didn't happen with the last build.

Also, is there a way to try out cores for this that weren't included with the build? I'd like to compare the core I built for Genesis Plus GX with the one included in this release, I'm sure it handled the Nuked audio synth more efficiently/without slowdown.

Try creating a new retroarch.cfg with the older version of lakka & compare with the latest. I would try just by grabbing an older retroarch.cfg and copy pasting into the latest Lakka. If that solves the problem go through and edit the changes in a newer retroarch.cfg file so as to avoid any bugs.

Basketto · Jul 31, 2019

Is it just me, or does GPU overclock no longer work? I have tried extreme overclocks after having increased visual resolution for certain games.
It literally does nothing now for fps increase. Anyone else having the same issue??
Coincidentally Hardware Per Pixel Lighting option, in Mupen64, no longer works & causes a crash.
Edit:
Going to revert back to the old build, Zelda the Ocarina of Time is now completely broken(in game menu causes a crash), meaning can not equip any items. N64 Games in general seem to stutter much more aswell.

Shaneus · Aug 1, 2019

Jackson98 said:
Try creating a new retroarch.cfg with the older version of lakka & compare with the latest. I would try just by grabbing an older retroarch.cfg and copy pasting into the latest Lakka. If that solves the problem go through and edit the changes in a newer retroarch.cfg file so as to avoid any bugs.

I still have the old CFG backed up, so I might just try renaming etc. and testing.

Still probably won't fix the speed issue with Nuked audio on Genesis Plus GX though, so I might just roll back to the older version for now.

Xandrid · Aug 1, 2019

I have a problem, I'm trying to play 7th Dragon 2020 with the PPSSPP core, but when I'm trying to make a name for my character (which I have too to continue) the keyboard doesn't popup no matter how long I wait. Basically I can't continue the game

Shaneus · Aug 1, 2019

I don't mean to sound naggy and whiny, but my Dreamcast stuff now doesn't load at all. Just throws me back to the xmb, happens with CHD and GDI files.

Josshy0125 · Aug 1, 2019

Shaneus said:
I don't mean to sound naggy and whiny, but my Dreamcast stuff now doesn't load at all. Just throws me back to the xmb, happens with CHD and GDI files.

That happened to me too. I had to delete my retroarch config. Then it worked

Fenderbendr · Aug 1, 2019

Jackson98 said:
Considering Lakka progress is slow, because of how many developers contribute to it , I thought i would share
a bit more testing and mainly on N64/Dreamcast/PS1

Disable Vsync and enable Adaptive Vsync, increases peformance large margins for N64(and a few other emulators) at pretty much no visible disadvantage 99% of the time
Enable Threaded video
N64 emulation- all stock GPU(handheld)/CPU running HD 1280x720

Banjo Tooie: Runs 100% fps, however the game has very occasional fraction of a second stutters maybe 1 time every few minutes or so, however the fps doesn't drop, running handheld with sharp textures.
Goldeneye: 100% fps maybe dropping to 98% fps in most intensive places however pretty much perfect
Conker's Bad Fur Day: Absolutely perfect, have completed 100% audio and gameplay
Donkey Kong 64: Gameplay is 100% perfect full speed however their is minor lag entering a Kong Swap Barrel(loading) and using the Banana Warp pads(loading)
Mischief Makers: Game runs 90-100% speed most of the time sometimes dropping down to 80%.
Yoshi Story: Still haven't found a solution to this, game runs full speed until you try and move Yoshi then fps drops from 100% to 20%, no amount of overclocking has any effect whatsoever.
Zelda Ocarina of time: Running 100% fps using a beautiful (3DS style)high resolution texture pack.

PS1 Emulation

Not sure why it took me so long to figure out, however
BEETLE>PCSX

Even though PCSX has a few higher FPS by default, Beetle offers 100 more configuration options but most importantly
1) Increase resolution over 10X scale (you actually can't do this at all with PCSX you are stuck playing at under 400p ;P)
2) Change emulated clock speed

Crash Bandicoot: Runs full speed 60FPS stock CPU/GPU 2x resolution, Lower Beetle clock speed to 50%/disable dithering
Diablo: Runs full speed stock CPU/GPU 2x resolution, Lower emulated clock speed to 70%/disable dithering.

If one of these gets a Dynarec, I hope its Beetle, because games look 100X better after upscale and it has many more options.

Dreamcast Emulation

All stock CPU/GPU resolution upscaled to x960p

Legacy of Kain Soul Reaver: Runs perfect
Super Magnetic Neo(DC Crash Bandicoot): Runs perfect, however make sure to use either CHD or GDI as CDI breaks at a certain point in game.
Silver(use CDI) runs about 90% in gameplay needs minor overclocking
Record of Lordoss War(DC Diablo) Runs 95%-100% speed, slow downs when lots of enemies on screen, minor overclocking helps.
Skies of Arcadia: Perfect
Sonic Adventure: Perfect
Rayman 2: Perfect

Highly suggest download the GDI to CHD converter raspberrypie website, Magnetic Neo for example is 10% of the original size and runs perfectly.

I have included some optimisations for some of the harder to emulate N64 games below, delete the .txt extension, show SD card Hidden files and place inside Lakka/storage/.config/retroarch/config/
Mupen64Plus-Next OpenGL. Make sure to delete the .txt extension so they read Banjo-Tooie.opt for e.g They must also be renamed to match your rom(not including .n64/z64/v64). So if you have Goldeneye 007 (USA).n64 as your rom the opt file needs to be renamed Goldeneye 007 (USA).opt.

Hey, thanks for these settings! What video driver should I be using for PS1 and N64 games? gl, glcore, or vulkan?

Well-Known Member

Well-Known Member

Well-Known Member

Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Banned!

Member

Similar threads

Popular threads in this forum