Published a new update for Status Monitor Overlay, the tool allows players to monitor the system information of the Switch console during matches.
With this application, you can view the frequency of the CPU, GPU and RAM, as well as the temperature and level of rotation of the fan.
This information can be useful to keep track of system performance and monitor the temperature during intense gaming sessions.
The tool has six different modes to choose from the main menu, Full, Mini, Micro, FPS Counter, Battery and Miscellaneous.
The new version introduced the “Game Resolutions” menu in the “Other” category. This mode requires the installation of SaltyNX 0.9.0 or higher to work properly.
When a game is running, this mode displays resolutions that have been passed to the GPU using two functions: nvnCommandBufferSetRenderTargetsfor the deep and textures nvnCommandBufferSetViewportfor the areas of view.
The menu shows the first 8 resolutions passed to the GPU during the last rendering cycle, sorted by the number of calls.
The main purpose of this mode is to identify the rendering resolution of the game, but the user must interpret which resolutions are actually used. The captured resolutions are limited to those with a ratio of more than 1.70 and less than 1.90.
Note that the resolutions displayed can be used in different ways, such as in the case of Tokyo Xanadu Ex+, where the maximum dynamic resolution in handheld mode can be 1280×736, without actually being displayed on a 720p screen.
This mode is only compatible with games that use the NVN API and may not work with other APIs or 2D games. The default menu update frequency is 10 FPS, but can be changed in the configuration file config.ini. .
The output from the mode is via the same key combination used in other main modes.
What is currently supported
- Using the CPU for each core (cores
#0– –#2are used by apps/games, the core#3it is used by the operating system, background processes and even Tesla overlays). - Loading GPU.
- Effective frequency of CPU, GPU and RAM.
- RAM used classified in: (not supported by firmware ?5.0.0).
- Total.
- Application.
- Applet.
- System.
- System Unsafe.
- Temperatures SoC, PCB and skin (skin temperature not supported by firmware 5.0.0).
- The level of rotation fan.
- PFPS and FPS (with the help of NX-FPS 0.4+, more information within the repository. Failure to install involves not displaying FPS counters on the overlay).
- Battery temperature, raw charge, age and average voltage
- Type of charger, maximum voltage and maximum current.
- I use DSP.
- Clock frequency NVDEC.
- Network type + Wi-Fi password.
Full
This mode can be known from previous versions of Status Monitor. It contains all the information correctly described and supported with high precision.
Optional (only disgraduate when the NX-FPS plugin is installed)
It only works in 1 and 5 Hz + vsync signal. You can change it with + .
Mini
It contains most of the information supported with lower precision.
Optional (only disgraduate when the NX-FPS plugin is installed)
It only works in 1 and 5 Hz + vsync signal. You can change it with + .
Micro
It contains most of the information supported with less accuracy in one line.
Show only if you haven’t changed the name of the overlay file (so it should be Status-Monitor-Overlay.ovl).
This is because we need to reload the overlay to change the size of the framebuffer without taking more RAM, and Tesla Menu (and libtesla with it) does not provide information about the file name of the overlay that has been uploaded.
Optional (only disgraduate when the NX-FPS plugin is installed)
It only works in 1 and 5 Hz + vsync signal. You can change it with + .
FPS Counter
Shows only the FPS value in the 31Hz + vsync signal. If the game is not started, it will always show the value 254.0.
Mode available with SaltyNX installed only.
The battery
It only appears if the loader type is different from 0:
Miscellaneous
If the network type is “Wi-Fi”, you can press Y to show the password. Because the maximum password length is 64 characters, it can be displayed in up to 3 lines.
additional information
What is the skin temperature (tskin)?
This is the temperature calculated from the temperatures of the SoC and PCB which is mainly used to prevent overheating of the Switch console. The reading is not supported on firmware lower than version 5.0.0.
Explanation provided by CTCaer:
Calculation of temperature (tskin).
Console and handheld:
tsoc 84oC – Immediate sleep. No questions asked.
tpcb 84C – Immediate sleep. No questions asked.
Only console:
tskin 63oC – It resets both timers.
tskin: 63oC – Immediate sleep. No questions asked.
Only handheld:
tskin 58oC – It resets both timers.
58oC tskin 61oC – Starts the 60s timer and cancels the 10s timer.
61oC tskin 63oC – Starts the 10-second timer.
tskin: 63oC – Immediate sleep. No questions asked.
The two timers are separate. If 61oC is reached, the timer 10s is started immediately.
If a timer ends and the temperature is not lowered, it goes into sleep mode.
tskin is the specific calculation below:
soc_adj = (temps.iir_filter_gain_soc * (temps.soc - temps.soc_adj_prev)) + temps.soc_adj_prev;
pcb_adj = (temps.iir_filter_gain_pcb * (temps.pcb - temps.pcb_adj_prev)) + temps.pcb_adj_prev;
temps.soc_adj_prev = soc_adj;
temps.pcb_adj_prev = pcb_adj;
if (soc_adj >= 38000)
{
if (temps.handheld)
soc_adj = (temps.tskin_soc_coeff_handheld[0] * soc_adj) + (1000 * temps.tskin_soc_coeff_handheld[1]);
else
soc_adj = (temps.tskin_soc_coeff_console[0] * soc_adj) + (1000 * temps.tskin_soc_coeff_console[1]);
soc_adj = (soc_adj / 10000) + 500;
}
if (pcb_adj >= 38000)
{
if (temps.handheld)
pcb_adj = (temps.tskin_pcb_coeff_handheld[0] * pcb_adj) + (1000 * temps.tskin_pcb_coeff_handheld[1]);
else
pcb_adj = (temps.tskin_pcb_coeff_console[0] * soc_adj) + (1000 * temps.tskin_pcb_coeff_console[1]);
pcb_adj = (pcb_adj / 10000) + 500;
}
skin_adj = MAX(soc_adj, pcb_adj); //tskinCom to the latest
- Add a graphic mode.
Requirements
- From version 0.4.1 you need to use Tesla Menu ?1.0.2.
Troubleshooting
Question: When you open Full or Mini mode, the overlay shows that using the Core 3 is 100% while everything else shows 0, eventually leading to the crash. Why does this happen?
Answer: There are few possible explanations:
- You are using nifm service connection test patches (in short
nifm ctest patches) which are included in various packages. These patches allow you to connect to a network that doesn’t have an internet connection. But they make nifm randomly go out when it’s connected to the network. Find any folder inatmosphere/exefs_patchesthat it has in the folder namenifm,nfimand / orctest, delete this folder and restart the Switch. If you need to use it, the only solution is to use this overlay only in airplane mode. - You are using an untested custom system module that has not implemented the correct thread sleep. Discover in atmosphere/pleass any system module you do not need, delete it and restart the Switch.
- The Switch console uses sigpatch, is not a main device, uses a linked account and is connected to the network. Delete sigpatch, change your Switch to the main device, disconnect your account, or disable Wi-Fi.
Changelog
- Added the “Game Resolutions” menu to the “Other” category. More details HERE.
- Installation of SaltyNX 0.9.0 or higher is required for proper operation.
Download: Status Monitor Overlay v1.0.4
Download: Source code Status Monitor Overlay v1.0.4
Source: gbatemp.net