Yeah, I heard. I need to know what is the main reason - being 32-bit (dunno if all exefs are 32-bit) or because of framework in NRO.
- Thread starter masagrator
- Start date
- Views 90,054
- Replies 222
- Likes 32
About resolution monitoring, Can someone explain why its impossible? not to be rude or anything just curious
There are no plans.
Because we have three resolutions to discuss here:
- Window resolution. Set by using system calls. It can be hooked globally, but only resolutions you will see are 1280x720 and 1920x1080
- Game main rendering resolution. It's done in each engine differently and it's managed internally, it's not possible to make something universal checking that, but there is s high chance it will match window resolution.
- Game camera rendering resolution. It's done in each engine differently and it's managed internally, it's not possible to make something universal checking that. This is what dynamic resolution changes in most cases.
To check camera rendering resolution you need to make plugin for each game different.
Last edited by masagrator,
Hello guys im installed what i need but doesnt open the overlay why ? pls help me
--------------------- MERGED ---------------------------
Hello guys, maybe you can help me, I installed "status-monitor-overlay", sys-clk, tesla and more on my atmosphere 11.0 switch. Until now, I could always call up hud with the key combination button left + right + y. But then when I opened sys-clk I got two three bluescreen now the hud no longer works, no matter how often I remove the apps from the app store and install it, it just doesn't open anymore. Do you know what I can change, which files do I have to delete so that I can get my hud back?
thanks for any help
--------------------- MERGED ---------------------------
Hello guys, maybe you can help me, I installed "status-monitor-overlay", sys-clk, tesla and more on my atmosphere 11.0 switch. Until now, I could always call up hud with the key combination button left + right + y. But then when I opened sys-clk I got two three bluescreen now the hud no longer works, no matter how often I remove the apps from the app store and install it, it just doesn't open anymore. Do you know what I can change, which files do I have to delete so that I can get my hud back?
thanks for any help
- Joined
- Aug 18, 2019
- Messages
- 8
- Trophies
- 0
- Age
- 32
- Location
- Santiago, Metropolitana de San
- Website
- miguelangelg.herokuapp.com
- XP
- 104
- Country
I got these currently instaled on my Atmosphère 0.19.4 on 12.0.3 version and not only crash, literally the console shutdown when i've try to active the Status monitor Overlay, (all my tesla overlay it's working perfectly but not this)
Exist anywhere a .log that could help me or other to investigated what's happened ?
got installed:
Status Monitor 0.6.3
NX-FPS 0.3
SaltyNX 0.4.0a hotfix
Tesla Menu v1.1.3
Sigpatches 12.0.3-0.19.4 fusee
Exist anywhere a .log that could help me or other to investigated what's happened ?
got installed:
Status Monitor 0.6.3
NX-FPS 0.3
SaltyNX 0.4.0a hotfix
Tesla Menu v1.1.3
Sigpatches 12.0.3-0.19.4 fusee
Last edited by newkey_sky,
For this there is no log that can help with that.
Shutdown without any error screen?
What hardware are you using?
I had this issue before but it was related to old FW using different id for fan controller.
I would need to reproduce this issue first, so give me everything you know. Step by step how to reproduce it with every detail.
- Joined
- Aug 18, 2019
- Messages
- 8
- Trophies
- 0
- Age
- 32
- Location
- Santiago, Metropolitana de San
- Website
- miguelangelg.herokuapp.com
- XP
- 104
- Country
Luckily, I'm amazed searching very well i've found this:
https://gbatemp.net/threads/tesla-the-nintendo-switch-overlay-menu.557362/page-40#post-9195781
I've found this folter on content, 010000000007E51A aside with 420000000007E51Am I've deleted 010000000007E51A restart the console and it's working now, i'm really don't know where is come from 010000000007E51A old version ?
Thanks anyway ! may be we need to add this possible issue with oldest version conflicts ?
https://gbatemp.net/threads/tesla-the-nintendo-switch-overlay-menu.557362/page-40#post-9195781
I've found this folter on content, 010000000007E51A aside with 420000000007E51Am I've deleted 010000000007E51A restart the console and it's working now, i'm really don't know where is come from 010000000007E51A old version ?
Thanks anyway ! may be we need to add this possible issue with oldest version conflicts ?
Hi everyone !
I've just installed Status-Monitor-Overlay, NX-FPS and SaltySD on my Nintendo Switch to get an FPS counter.
But on the HOME screen, and every games (SM3DAS, MK8D, BOTW...), it just show 254.0 value and only in "FPS Counter", "Full" and "Mini" don't show any FPS counter.
Did I missed something ? Incompatibility with the last Atmosphere version ?
Versions are just bellow.
Thanks!
emuNAND: 11.0.1
Atmosphere: M.19.4
hekate: 5.5.7
nx-ovlloader: 1.0.6
Status-Monitor-Overlay: 0.6.3
SaltyNX: 0.4.0a hotfix
NX-FPS: 0.3
I've just installed Status-Monitor-Overlay, NX-FPS and SaltySD on my Nintendo Switch to get an FPS counter.
But on the HOME screen, and every games (SM3DAS, MK8D, BOTW...), it just show 254.0 value and only in "FPS Counter", "Full" and "Mini" don't show any FPS counter.
Did I missed something ? Incompatibility with the last Atmosphere version ?
Versions are just bellow.
Thanks!
emuNAND: 11.0.1
Atmosphere: M.19.4
hekate: 5.5.7
nx-ovlloader: 1.0.6
Status-Monitor-Overlay: 0.6.3
SaltyNX: 0.4.0a hotfix
NX-FPS: 0.3
Last edited by Reshiban,
This means your SaltyNX is working, but nx-fps is not injected. Probably wrongly installed plugin or conflicting with something else.Hi everyone !
I've just installed Status-Monitor-Overlay, NX-FPS and SaltySD on my Nintendo Switch to get an FPS counter.
But on the HOME screen, and every games (SM3DAS, MK8D, BOTW...), it just show 254.0 value and only in "FPS Counter", "Full" and "Mini" don't show any FPS counter.
Did I missed something ? Incompatibility with the last Atmosphere version ?
Versions are just bellow.
Thanks!
emuNAND: 11.0.1
Atmosphere: M.19.4
hekate: 5.5.7
nx-ovlloader: 1.0.6
Status-Monitor-Overlay: 0.6.3
SaltyNX: 0.4.0a hotfix
NX-FPS: 0.3
Don't bother with MK8. SaltyNX doesn't support 32-bit games and MK8 is 32-bit.
Last edited by masagrator,
Ah yes, I just putted NX-FPS.elf in
Code:
sd:/SaltySD/patches/Changed to
Code:
sd:/SaltySD/plugins/(Btw you propose some sysmodules, but I don't see their utility : p)
Thanks for your reply and your work
PCB and SoC temperature in milliC is unsupported since 14.0.0 FW. So in case of using Status Monitor on 14.0.0+ with version 0.6.3 you will see those temperatures outputting 0.0C
I need to update Status Monitor to take integer Celsius for 14.0.0+ FW + update it to support newest libnx.
I expect it to be done in 24h.
I need to update Status Monitor to take integer Celsius for 14.0.0+ FW + update it to support newest libnx.
I expect it to be done in 24h.
0.6.4
0.6.4 is now released.
At the top of adding support for 14.0.0 it also fixes slow boot by using fix from Breeze repo.
https://github.com/masagrator/Status-Monitor-Overlay/releases/tag/0.6.4
At the top of adding support for 14.0.0 it also fixes slow boot by using fix from Breeze repo.
https://github.com/masagrator/Status-Monitor-Overlay/releases/tag/0.6.4
Is there a way to configure the button combination for closing the overlay? Sometimes I use a controller which doesn't have sticks that can be pressed, like the Wii Classic Controller for example, or sometimes pressing sticks can be a bit finicky. If not, is there any other way to close Status Monitor than pressing both sticks? Like putting the console to sleep or something? Any suggestions would be welcome!
Similar threads
