Back
Status-Monitor-Overlay
by masagrator
|
| Version | 1.1.7a |
| Zip size | 194 KiB |
| License | GPLv2 |
| Updated | 21/12/2024 |
| Downloads | 118,147 |
| MD5 | afed450252d88d23d18863e6cc2e0d8f |
App Details
Monitor Your hardware in real time!
This is an overlay homebrew dedicated to Nintendo Switch. You need to have installed Tesla environment to use it.
Tool contains three modes to choose, each one is explained here : https://github.com/masagrator/Status-Monitor-Overlay/blob/master/docs/modes.md
You can exit from selected mode by pressing and holding Left Stick + Right Stick. To exit from main menu press B.
If it's not working in dock, you need to first start Status Monitor, then put Nintendo Switch to dock.
What is currently supported:
CPU Usage for each core (Cores #0-#2 are used by apps/games, Core #3 is used by OS, background processes and also Tesla overlays)
GPU Load
CPU, GPU & RAM actual frequency
Used RAM categorized to: (not supported by FWs <5.0.0)
Total
Application
Applet
System
System Unsafe
SoC, PCB & Skin temperatures (Skin temperature not supported by FWs <5.0.0)
Fan Rotation Level
PFPS and FPS (with help of NX-FPS, more info in repo. Not installing it results in not showing FPS counters on overlay)
Planned:
Add Graph mode
Requirements:
From 0.4.1 you need Tesla Menu >=1.0.2
Thanks to:
RetroNX channel for helping with coding stuff
SunTheCourier for sys-clk-Overlay from which I learned how to make my own Tesla homebrew
Herbaciarz for providing screenshots from HDMI Grabber
FAQ:
Q: This homebrew has any impact on games?
A: Negligible, you won't see any difference. Almost everything is done on Core #3, other cores usage is below 0.001%.
Troubleshooting:
Q: Game sometimes hangs when using Status Monitor Overlay. Why?
A: This is because of dmnt:cht nature. Some games don't like that it's peaking constantly at its memory and they stuck. This happens only if you are using NX-FPS plugin. Solution is to just close Status Monitor Overlay (you don't need to close Tesla Menu) and wait few seconds until game will resume.
Changelog
1.1.7a
Add support for SaltyNX 1.2.0+ (older versions are now unsupported when it comes to using FPS Graph)
Fix reading config issue for Mini mode #88
1.1.6
Small code refactor which resulted in slightly smaller size
Support SaltyNX 1.0.3+ display refresh rate update logic in FPS Graph to fix issue with graph randomly not adjusting height to refresh rate (if there is older SaltyNX used, overlay will use old logic)
1.1.4
Fix issue with overlay potentially crashing system on overlay's boot related to nv services
Fix potential issue with sleep mode at 19.0.0+ that was first discovered in sys-clk retronx-team/sys-clk#85
For some reason using tsSessionGetTemperature is enough to crash system while is in sleep mode
It was fixed by moving from ts service to i2c. Readings are not filtered, so reading output and behavior can be slightly different than what we were used to.
1.1.3
Switch reading fan rotation level from "fan" service to "pwm" service
This allows avoiding potential conflict with other homebrew/sysmodules (f.e. Nx-FanControl) because only one process can have fan controller session in "fan" service.
1.1.2
Fix Resolutions sometimes going out of bounds in Full Mode
Update SaltyNX to 0.9.2+ for better compatibility with games using Id Tech engines and Creation Engine
1.1.1
Added options to show 2 the best candidates for game's internal resolution in Mini and Full modes.
Added keys to config that can disable showing FPS and Resolutions in Full mode
Added value RES to show key in Mini mode that shows Resolutions.
Update SaltyNX to 0.9.1+ for better compatibility with games using Id Tech engines
1.1.0
Added "Game Resolutions" menu to "Other" category. More HERE.
SaltyNX 0.9.0+ is required for it to work properly
1.0.4
Moved from c++20 to c++23
With SaltyNX 0.8.0+ FPS Graph mode will adjust height according to received back display refresh rate.
1.0.3a
Fix compability issues with combos from Ultrahand and Tesla configs after implementing #72
1.0.3
Improved key combo and navigation handling #72 (thanks to @IrneRacoonovich )
Fixed an issue with battery readings not working after exiting Micro mode multiple times without rebooting Switch (this bug affected also other homebrew reading battery stats with PSM service)
Futureproofed for sys-clk IPC updates
1.0.2
Add new keys to config: battery_avg_iir_filter and battery_time_left_refreshrate, more in CONFIG
Changing battery_avg_iir_filter to true results in period time of average voltage being changed to 45s, and 11.25s for amperage
Removed whole logic behind PR #56 instead relying now on max17050 TTE register
Changed i2c communication code to avoid issues with wrong readings (thanks to ~lineon)
Move FPS Graph and FPS Counter to one subcategory "FPS"
1.0.1
Allow hiding real frequencies, deltas and target frequencies in Full mode (deltas are not showed if both real + target frequencies are hidden).
This release also includes 2 shadow updates for 1.0.0, which includes fixes for overflowing of real frequencies + deltas, and also fixed RAM positioning calculations in Micro and Mini modes.
0.9.2
17.0.0 FW issues fixed:
SoC and PCB temperatures showing 0
Charger Type, Charger Max Voltage and Charger Max Current showing wrong values
General changes:
SoC and PCB temperatures across all FWs are now showing decimals
Next to Battery Power Draw in Full, Mini and Micro modes you can see now also estimated time left before Switch will shutdown (thanks to rkuchkarov for PR #56)
In Micro instead of MB for RAM now you will see GB up to one decimal
In Micro now power draw shows only one decimal
Fan level will now render only one decimal across all modes
Miscellaneous now also shows NVENC and NVJPG clocks (thanks to averne for PR #57)
Since 17.0.0 audsnoop is not available, DSP Usage is not shown in Other -> Miscellaneous tab
0.9.1
Now filepath for Micro mode is not hardcoded, it is retrieved via Tesla Menu.
To use it with changed filename it is required to update Tesla Menu to version at least 1.2.3.
On older versions of Tesla Menu it behaves the same as 0.9.0 version.
0.9.0
Corrected Battery Power Flow calculation
Changed Battery Stats reading to 2 readings per second. Current, Voltage and Power Flow are calculated now via 10 last readings.
Changed FPS average calculation to 10 last readings instead of constant averaging
Added Graphs tab with currently only FPS available (Graphs tab won't show for now if you don't have SaltyNX installed)
Moved Battery/Charger + Miscellaneous tabs under "Other" tab
You can move now FPS Counter + FPS Graph to the bottom and top of screen by pressing ZR + R + D-Pad Down/Up
0.8.3
Add Battery Power Flow stat into Full, Mini, Micro modes and Battery/Charger tab
Add Battery Current Flow into Battery/Charger tab
Change Battery Voltage from 45s average to average of 5 to match better with Battery Current Flow and get faster responses to changes in voltage at the cost of slightly less accurate readings
Fix a random issue with allocing memory for reading Wi-Fi password and battery stats
0.8.2
Fix conditional handle leak
Fix memory leak
Workaround race condition causing random crashes in docked mode
0.8.1
Move reading FPS from dmnt:cht to SharedMemory. This fixes any stutterings, thread desyncing and cracking sounds you may have encountered when using NX-FPS in games.
Requires NX-FPS 0.4+ and SaltyNX 0.5.0+ to read FPS.
0.7.1
It adds support for 16.0.0.
0.7
New 2 tabs were added:
Battery/Charger
Miscellaneous
You can now check Battery temperature, max supported charger voltage and current, connected Wi-Fi password and few others.
0.6.4
Added support for 14.0.0 FW.
It removed function for reading SoC and PCB temperatures in milli Celsius. 0.6.3 was outputting 0.0C because of that. Now it reads temperature in Celsius without decimals on FW 14.0.0+
Fixed slow boot time by reimplementing fix from Breeze repository
0.6.3
Fixed button combo
0.6.1
Fix issue related to always forcing opening cheat process with dmnt:cht that sometimes resulted in conflicts with other tools.
Now it's checking first if cheat process is opened already.
0.6.0
If dmnt:cht is not detected, it's using svc calls to read FPS values for NX-FPS (now only if SaltyNX check failed, FPS Counter won't show).
Be aware that not using Atmosphere's dmnt:cht may introduce conflicts with other cheat engines, resulting in crashes or hangs.
0.5.4
Fix issue with CPU Core usage stuck at last value when core usage is at peak.
0.5.3
Updated to libnx 3.2.0, which helps with very rare case of crashing overlay if pl sessions are depleted.
Fixed wrong version inside overlay
0.5.2
Added version info for Tesla menu
Added support for SX OS (FPS Counter is not available)
