Tesla - The Nintendo Switch Overlay Menu

fhwyjbd.png

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

W8yN2M6.jpg

fdfWAXw.jpg


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: https://download.werwolv.net/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 :)
 
Last edited by WerWolv,
Hi, I've been having a problem with the atmosphere program 0000000000534C56 (SaltyNX's content library). I use it mainly for the FPS counter,and it works flawlessly. The problem I'm having is that if I close any game and re-launch it a second time, atmosphere crashes with no exceptions, if I disable the SaltyNX module the crashes are gone tho. So I would like to know if there's any solution. My only guess rn is that the crash has to be related with SaltyNX no being 100% supported on 16.0.3 (Atmosphere 1.5.3) . Also I would like to add that I installed this module recently so I couldn't test it with older versions.View attachment 373548
absolute same issue
Post automatically merged:

So a little update. It seems I solved the problem and 0000000000534C56 is no longer crashing my switch as I stated above, it might not be the easiest solution tho. Tl;dr Yesterday my emunand on my microSD card got corrupted, so I ended up re-installing all my CFW from scratch after formating my microSD (partitioning it again, creating a new emummc, etc), and with this new setup the issue got solved. So yeah I kinda had a feeling that it was related with some kind of incompatibility with other hombrew, but sadly I couldn't find the the exact thing that was causing the issue as I was intending before the data corruption.
that sux bc idk how to do half of that, rly dont wana take the time to do the half i do know how to do lol. i guess i can get along without salty nx for now. thnx for the info tho.
 
IMG_3868.jpg


Hello everyone. I'm fairly new to the switch modding scene, so I appreciate your help and patience. I cannot get the Tesla overlay mod to work. I have updated overlays, using the very ones linked on this thread, but this crash always happens on boot up. The only time my switch boots up properly is when I remove the 4200000000007E51A folder from the contents folder, or I remove the ovlmenu.ovl file from the .overlay folder. Again, I have tried a ton of different combos of Tesla builds and overlay files, including the updated linked ones in this thread. Nothing seems to work. Can you help me out please?
 
View attachment 375614

Hello everyone. I'm fairly new to the switch modding scene, so I appreciate your help and patience. I cannot get the Tesla overlay mod to work. I have updated overlays, using the very ones linked on this thread, but this crash always happens on boot up. The only time my switch boots up properly is when I remove the 4200000000007E51A folder from the contents folder, or I remove the ovlmenu.ovl file from the .overlay folder. Again, I have tried a ton of different combos of Tesla builds and overlay files, including the updated linked ones in this thread. Nothing seems to work. Can you help me out please?
Backup and remove your SD:/ATMOSPHERE folder, then download again Atmosphère, sigpatches, tesla and overlays from net and extract to root of SD, maybe a incompatible sysmodule.
 
absolute same issue
Post automatically merged:


that sux bc idk how to do half of that, rly dont wana take the time to do the half i do know how to do lol. i guess i can get along without salty nx for now. thnx for the info tho.
i had the same problem, the problem is also explained in the saltynx's github..its somewhat related to "dirty" compilation of saltynx module (probably a fork from someones cfw pack). Original files by masagrator (dev) are working just fine. But to fix the problem i had to delete everything related to saltyNX (SaltySD folder and atmos contents related stuff), then just installed everything fresh (saltyNX, NXfps, reverse-nx etc.) Didn't have time to figure out the exact culprit but that did the trick for me, no need to reinstall EVERYTHING. Also the problem didn't go away by replacing/overwriting files, i had to delete the folders manually and reisntall.
 
Backup and remove your SD:/ATMOSPHERE folder, then download again Atmosphère, sigpatches, tesla and overlays from net and extract to root of SD, maybe a incompatible sysmodule.
I just spent the last few hours doing this. Reinstalled fresh Atmosphere update multiple times. No sysmodules other than Tesla. Sigpatches are updated. Overlays removed, redownloaded, and replaced. I even tried the zip file from post #1444. It still threw up the same error code. This is so frustrating. The only time I've been able to boot into Atmosphere without a crash is when the only thing in the contents folder is the Tesla mod. If I add sys-clk, MissionControl, or any other sysmodules, it crashes on boot.
 
  • Wow
Reactions: impeeza
I just spent the last few hours doing this. Reinstalled fresh Atmosphere update multiple times. No sysmodules other than Tesla. Sigpatches are updated. Overlays removed, redownloaded, and replaced. I even tried the zip file from post #1444. It still threw up the same error code. This is so frustrating. The only time I've been able to boot into Atmosphere without a crash is when the only thing in the contents folder is the Tesla mod. If I add sys-clk, MissionControl, or any other sysmodules, it crashes on boot.
try the zip files in post #1432 instead
 
try the zip files in post #1432 instead
Just tried this. It seems to boot fine into Atmosphere, but I can't bring up the Tesla Menu with the L+down+R3 combo. When I launch a game, and then go into EdiZon to check sysmodules, it shows Tesla as OFF. When I turn it on and exit back to the game, the switch crashes and throws the same error code as previous. Does the EdiZon nro version matter? Could that be causing the issue? Again, the only thing I have in my contents folder this time is the nx-ovlloader-1.0.7. The only overlays I have are the Tesla Menu v1.2.3 downloaded directly from github repo and the EdiZon 1.0.5. Am I missing something here?
 
Humm strange as the doctor, what have your stratosphere.ini?
I didn't have one in my config folder. I might have had one before, but I've wiped my atmosphere folder so many times now it's hard to keep track. What setting should I have in my stratosphere.ini?

nogc = 1 or nogc= 0?

And how does the NoGameCard setting effect how sysmodules function?
 
I didn't have one in my config folder. I might have had one before, but I've wiped my atmosphere folder so many times now it's hard to keep track. What setting should I have in my stratosphere.ini?

nogc = 1 or nogc= 0?

And how does the NoGameCard setting effect how sysmodules function?
is on the sd root.
 
Moved it to the SD Root. With both nogc = 0 & nogc = 1 , I launch the game, then on EdiZon I toggle the Tesla sysmodule on. I go back to game, then input the L+down+R3 button combo, and a crash happens with the same error code.
Post automatically merged:

I finally figured it out! After digging around, I found out that the problem was due to macOS using "." to make files invisible. So, the .overlays didn't copy over as intended. This effected Atmosphere not being able to properly recognize the .overlays folder. The solution I came up with was to use Atmosphere's USB File Transfer and create an .overlay folder using Android File Transfer. I then transferred the overlays (olvEdiZon.ovl, ovlmenu.ovl, and ovlSysmodules.ovl) into the newly created .overlays folder, rebooted Atmosphere, and everything worked as it should!

Here is the link to the thread on GitHub that helped me figure out what was wrong:
https://github.com/WerWolv/Tesla-Menu/issues/62

Thanks everyone for your patience and help! I hope this is helpful to any Mac users out there who have also run into this issue.
 
Last edited by SwayStation,
Hey everybody, I just updated the post https://gbatemp.net/threads/tesla-the-nintendo-switch-overlay-menu.557362/post-10121629 with the latest LibNX 4.4.2-8ce306b(2023_05_27-09_24), LibTesla-1.3.3-f766e9b(2023_05_27-07_26) and Atmosphere-libs-f4a966e(2023_05_14-05_116).

Sorry for be so late but lots of things at work.
Post automatically merged:

Moved it to the SD Root. With both nogc = 0 & nogc = 1 , I launch the game, then on EdiZon I toggle the Tesla sysmodule on. I go back to game, then input the L+down+R3 button combo, and a crash happens with the same error code.
Post automatically merged:

I finally figured it out! After digging around, I found out that the problem was due to macOS using "." to make files invisible. So, the .overlays didn't copy over as intended. This effected Atmosphere not being able to properly recognize the .overlays folder. The solution I came up with was to use Atmosphere's USB File Transfer and create an .overlay folder using Android File Transfer. I then transferred the overlays (olvEdiZon.ovl, ovlmenu.ovl, and ovlSysmodules.ovl) into the newly created .overlays folder, rebooted Atmosphere, and everything worked as it should!

Here is the link to the thread on GitHub that helped me figure out what was wrong:
https://github.com/WerWolv/Tesla-Menu/issues/62

Thanks everyone for your patience and help! I hope this is helpful to any Mac users out there who have also run into this issue.
Oh I see, a layer 8 problem! cool.
 
Last edited by impeeza,
hi guys I need help TT
I've read the post #1432 and updated all the ovl + nx-ovlloader but I can't open the tesla menu even after added the contents in SD:/CONFIG/TESLA. So I tried to download everything again and now even now whatever I do I kept having this error at reboot..
 

Attachments

  • Screen Shot 2023-07-12 at 00.43.03.png
    Screen Shot 2023-07-12 at 00.43.03.png
    738.9 KB · Views: 90
You might have a Tesla module that needs updated. So check inside sd:/switch/.overlays/ and make sure you update all of them
 

Site & Scene News

Popular threads in this forum