Hey all.
I'd like to introduce to you, Tesla: My answer to the growing need for proper ingame front ends for sysmodules.

What is this?

• Tesla consists of three individual parts. nx-ovlloader, the Tesla menu and libtesla.
  • nx-ovlloader is basically nx-hbloader ported to run as a sysmodule. It runs in the background and loads overlay NROs (.ovl files) given to it.
  • Tesla Menu is the equivalent to the hbmenu. It's the initial thing loaded by nx-ovlloader and acts as a hub for you to select all other overlays.
  • libtesla is where it becomes interesting for developers. It's an easy to use library that handles layer creation, UI drawing and all the overlay UX. It makes it very easy to create a new overlay for anything
• A frontend for sysmodules that before required either a homebrew or a config file to change settings or used sounds or the LED to give the user feedback.

What is this not?

• A tool that lets you create overlays that are always visible. Overlays can get unloaded way to easily for this.
• An excuse to port absolutely everything to a overlay. Nobody's going to need a title manager overlay. If you consider making a overlay, keep it simple. You don't have a whole lot of memory to work with.

How do I use this?

First of all, download the latest release of nx-ovlloader and the Tesla Menu from the GitHub Release page and extract it onto your SD card.
After a reboot, hold down L and DPad Down and push on the right joy stick to bring up Tesla at any time. Navigation works as you imagine it.
Similar to normal homebrews, you place your .ovl files in the /switch/.overlays folder on your SD card.


Screenshots

Spoiler: Screenshots

Notice

Make sure to use the latest Atmosphere release when trying this as older versions ( as the one SX OS uses too ) probably won't have enough memory available for this to run. Overlays do take a lot of space so nx-ovlloader reserves 6MB. 2MB for framebuffers and around 4MB for overlay developers to use in their overlays.


GitHub

nx-ovlloader: https://github.com/WerWolv/nx-ovlloader
Tesla Menu: https://github.com/WerWolv/Tesla-Menu


For Developers

libtesla: https://github.com/WerWolv/libtesla
Tesla build template: https://github.com/WerWolv/Tesla-Template


Download

nx-ovlloader: https://github.com/WerWolv/nx-ovlloader/releases/latest
Tesla-Menu: https://github.com/WerWolv/Tesla-Menu/releases/latest
EdiZon Overlay: http://werwolv.net/downloads/EdiZonOverlay.zip ( As a little preview for what this is capable of and what EdiZon 4.0.0 will have even more of soon )

Special thank especially to averne without him, this would not have been possible!


Obligatory Donation links

GitHub Sponsors https://github.com/sponsors/WerWolv
PayPal https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=KP7XRJAND9KWU&source=url
Patreon https://www.patreon.com/werwolv


Thanks a lot and have fun using and extending it

 

[urherenow]

go to the description of the old patches if you don't want to believe me
https://github.com/WerWolv/nx-ovlloader/releases

Crash workaround

• Before, libtesla exhausted service sessions which made qlaunch crash on firmwares lower than 9.0.0. nx-ovlloader now gracefully exits instead of making qlaunch crash. If you're using a firmware lower than 9.0.0, please update!

Exit on unsupported versions again

• A check preventing Tesla from running (and crashing / causing issues) on firmwares bellow 9.0.0 went missing with the last release. This re-adds that check again. Thanks to @friedkeenan

so even if it is possible that it has nothing to do it remains possible that nx-ovlloader is the culprit

something that works does not necessarily work at 100/100 that's why the update exists again I don't know if it's his or not but its possible

Dude… I’m sorry it’s quite impossible for you to understand what you’re talking about, but I’ll try 1 more time.

1) nx-ovlloader does not use libtesla. AT. ALL. It loads .ovl files (ovlmenu.ovl being the default (Tesla menu)) that happen to be built using libstesla. That’s all it does. It loads the .ovl files. Get it?

2) You can read the submitted code for the “workaround“ as it’s only 3 lines of code. That workaround was simply: If HOS is below version 9, don’t load anything at all; just exit.

3) The above is needed because the Tesla menu (which is NOT ovlloader… how many times do I have to say this JFC…) cannot run without crashing below firmware 9.

4) Please just leave it at “I don’t know” and stop with the annoying rants. Maybe go use your energy to learn punctuation or something.

 

[silien3]

Dude… I’m sorry it’s quite impossible for you to understand what you’re talking about, but I’ll try 1 more time.

1) nx-ovlloader does not use libtesla. AT. ALL. It loads .ovl files (ovlmenu.ovl being the default (Tesla menu)) that happen to be built using libstesla. That’s all it does. It loads the .ovl files. Get it?

2) You can read the submitted code for the “workaround“ as it’s only 3 lines of code. That workaround was simply: If HOS is below version 9, don’t load anything at all; just exit.

3) The above is needed because the Tesla menu (which is NOT ovlloader… how many times do I have to say this JFC…) cannot run without crashing below firmware 9.

4) Please just leave it at “I don’t know” and stop with the annoying rants. Maybe go use your energy to learn punctuation or something.

you are not serious I hope you are telling yourself it was only 3 lines of code for lower firmware, in point 2. the problem lines of code are lines of code to be circumvented or corrected to make it work correctly. this is why nx-ovlloader had been updated in the past, without this correction there may be bugs, crashes or even not work at all. as we currently have bugs it can be something similar lines of code too many, missing or wrong or simply responding badly for a security update
that can cause crashes

the worst is that you say yourself that this type of bug is possible and you continue to say that it is not nx-ovlloader look for the error
Obviously the error can be different as I have already said but since we do not know where the crashes come from, it can come from there as it was already the case in the past and this kind of bug is not exclusive to firmware 9.0.0 or even at the level of the switch its exists on everything that has programming code its more thanks to the erroneous answer linking to the code that some hack exists and it is also for this reason that on the ps4 / ps5 and other consoles precisely to avoid this kind of bug and prevent hacks via this kind of procedure that they are updated

a single abnormal response whether it is ovl or nx-ovlloader even if it is only a small insignificant line can cause crashes and even if everything works it will crash at some point because there is an abnormal response

a memory leak can have other reasons such as overload or too much bandwidth for example so basically the culprit is the nx-ovlloader which remains possible or the ovl no matter where the cause is I did not say it was one or the other the culprit but it remains possible

yes there are other possible reasons for the crash but pretending that it is not nx-ovlloader without having tampered with the code yourself or looking for the error, etc., you have to stop

 

[urherenow]

you are not serious I hope you are telling yourself it was only 3 lines of code for lower firmware

I’ve been trying to avoid saying this, but I guess I can’t. You’re an idiot. Or would you like to call the extra space a 4th line of code? Just curious

https://github.com/WerWolv/nx-ovlloader/pull/9/commits/147af2ef8df4ee3a3e59c8d7f47a7afda0cab118

edit: wait, I guess you need this explained to you too: The red line is a line that was removed, while the green lines were added. The other lines are existing code from before the change, and used as a reference point.

 

[silien3]

I’ve been trying to avoid saying this, but I guess I can’t. You’re an idiot. Or would you like to call the extra space a 4th line of code? Just curious

https://github.com/WerWolv/nx-ovlloader/pull/9/commits/147af2ef8df4ee3a3e59c8d7f47a7afda0cab118

edit: wait, I guess you need this explained to you too: The red line is a line that was removed, while the green lines were added. The other lines are existing code from before the change, and used as a reference point.

here the idiot its you you prove me right here
you give additional proof that the nx-ovlloader has already been modified in the past to work correctly and you still dare to come and say that the others are wrong saying that it's impossible that it's the culprit seriously you have to do it

yes that's what I'm saying lines of code we change here we are added to work correctly in 9.0.0 so it may be similar with the latest so 16.0.0 may even be something to remove for the latest firmware

code may change to work properly this is not a 9.0.0 exclusive this is exactly what I said above is not reserved for the switch or the firmware or any other programming everyone may have to change even just one line to work correctly obviously this is perhaps not the problem as already said

 

[JeepX87]

There is no need to bickering in this thread, please.

 

[TomSwitch]

There is no need to bickering in this thread, please.

People just want to be labeled as right. How many actually care about the truth? I rather discover that I was wrong than to continue to believe I was right when I wasn't. Some will pull rank to be right.

 

[JeepX87]

People just want to be labeled as right. How many actually care about the truth? I rather discover that I was wrong than to continue to believe I was right when I wasn't. Some will pull rank to be right.

Ok, I understand.

For me, I don't pick a side when two members bicker, and I do want to treat both equally.

Fortunately, I'm easy person to admit a mistake if I made a mistake, and no one is perfect.

 

[TomSwitch]

Ok, I understand.

For me, I don't pick a side when two members bicker, and I do want to treat both equally.

Fortunately, I'm easy person to admit a mistake if I made a mistake, and no one is perfect.

When the argument is binary there is really only one who can be with the truth. I think there is no need for inquisition as it really don't matter that much. Have not seen evidence that nx-overloader needs an update with HOS16 and the stake is very low to hold on to that believe for most people anyway.

As to the rights to be wrong I think everyone should be treated equal. Nobody have more rights than others to being wrong.

Getting corrected is a privilege and a grate kindness on the part of the person who take the effort to do so.

 

[silien3]

There is no need to bickering in this thread, please.

When the argument is binary there is really only one who can be with the truth. I think there is no need for inquisition as it really don't matter that much. Have not seen evidence that nx-overloader needs an update with HOS16 and the stake is very low to hold on to that believe for most people anyway.

As to the rights to be wrong I think everyone should be treated equal. Nobody have more rights than others to being wrong.

yes especially that I only say that it is possible not that he is responsible and I highlight each time what I put in bold are the points that I highlight not anger or anything else but in any case the random crashes can be linked to him that's a fact and its what I'm trying to show him that it's still possible by specifying that he may not be responsible but he insists on the impossibility when nothing in the world is impossible or almost

anything man made may need updating for whatever reason or stop working and programming code and nx-overloader are no exception its all that i try to make him understand so the crash can always be linked to it even if it may not be the cause I insist each time on the may not be responsible since its each time in bold in addition

personally I think of a memory leak given the crash but I could be wrong the future will tell

finally let's move on

 

[dsrules]

yes especially that I only say that it is possible not that he is responsible and I highlight each time what I put in bold are the points that I highlight not anger or anything else but in any case the random crashes can be linked to him that's a fact and its what I'm trying to show him that it's still possible by specifying that he may not be responsible but he insists on the impossibility when nothing in the world is impossible or almost

anything man made may need updating for whatever reason or stop working and programming code and nx-overloader are no exception its all that i try to make him understand so the crash can always be linked to it even if it may not be the cause I insist each time on the may not be responsible since its each time in bold in addition

personally I think of a memory leak given the crash but I could be wrong the future will tell

finally let's move on

if you are still having crash problems, then have you tried this and see if there is any improvements
https://gbatemp.net/threads/tesla-the-nintendo-switch-overlay-menu.557362/post-10094422

 

[silien3]

if you are still having crash problems, then have you tried this and see if there is any improvements
https://gbatemp.net/threads/tesla-the-nintendo-switch-overlay-menu.557362/post-10094422

not yet tested but according to some does not change I will test personally when I have the time with luck it will work I will see

 

[dsrules]

not yet tested but according to some does not change I will test personally when I have the time with luck it will work I will see

try the official release of Atmosphère 1.5.1

 

[silien3]

try the official release of Atmosphère 1.5.1

hope this fixes all i will test when i have time

 

[nefariouslegion]

Hey nefa, refer to this https://gbatemp.net/threads/tesla-the-nintendo-switch-overlay-menu.557362/post-10091531

Tried this and it said no changes were needed. Didn't fix the issue

Post automatically merged: Mar 14, 2023

I just updated to Atmosphere 1.5.1 using the switch All-in-one Updater. Now my tesla menu doesn't open. I followed the rentry guide and it said to select Yes to delete all custom sysmodule startup flags. I'm wondering if that broke it? Also wondering if anyone knows a fix?

 

[binkinator]

Tried this and it said no changes were needed. Didn't fix the issue

Post automatically merged: Mar 14, 2023

I just updated to Atmosphere 1.5.1 using the switch All-in-one Updater. Now my tesla menu doesn't open. I followed the rentry guide and it said to select Yes to delete all custom sysmodule startup flags. I'm wondering if that broke it? Also wondering if anyone knows a fix?

Ahhh...the old what does this button do?

You've deleted your sysmodule flags. You will need to go back in and enable them or reinstalll.

 

[dsrules]

Tried this and it said no changes were needed. Didn't fix the issue

Post automatically merged: Mar 14, 2023

I just updated to Atmosphere 1.5.1 using the switch All-in-one Updater. Now my tesla menu doesn't open. I followed the rentry guide and it said to select Yes to delete all custom sysmodule startup flags. I'm wondering if that broke it? Also wondering if anyone knows a fix?

maybe the files from All in one updater are outdated, not compatible with 16.0

 

[nefariouslegion]

Ahhh...the old what does this button do?

You've deleted your sysmodule flags. You will need to go back in and enable them or reinstalll.

How do I re-enable them?

Post automatically merged: Mar 14, 2023

maybe the files from All in one updater are outdated, not compatible with 16.0

Nah they're up to date. Atmosphere 1.5.1

 

[ELY_M]

I always update manually and use USB way via hekate.
I updated to 1.5.1

the tesla overlay still crashing when I switch pokemon in pokemon violet.
it works for few Pokemon changes then it crashed.

 

[binkinator]

How do I re-enable them?

Easy way is via Hekate Toolbox or DeepSea Toolbox. underneath it’s just adding a blank file called boot2.fs into /atmosphere/contents/<titleID>/flags/

 

[[Truth]]

Has @WerWolv said anything about updating his applications for 16.0.0?