Homebrew WIP Status Monitor Overlay - Tesla Overlay to monitor your hardware

[[Truth]]

The graph is really an incredible feature!
Reminds me of my PC gaming days and the endless hours if tweaking graphics settings to get that straight line. 😂

Would be even cooler if there was a mix of graph and Micro/Mini/Full.
Like a toggle to switch between FPS number and graph in those.

 

[masagrator]

The graph is really an incredible feature!
Reminds me of my PC gaming days and the endless hours if tweaking graphics settings to get that straight line. 😂

Would be even cooler if there was a mix of graph and Micro/Mini/Full.
Like a toggle to switch between FPS number and graph in those.

For graph to be usable it must be refreshed at around 30 Hz minimum which is heavily taxing on Core #3 when it also must render many texts. We are talking about 20% of Core 3 usage in worst case. Tesla is working fully on CPU, so I cannot merge many taxing things at once if I want for performance stats to be as close to real values as possible.

 

[cucholix]

0.9.0 version is now available.

Changelog:

After few years I have finally tackled graph. So we are close to 1.0.0 release.
If you have any ideas for another graphs I can implement, give me a tip with proper explanation how this should work.

Finally at least one equation I have learned in middle school was useful.

The graph feature adds more memory usage than previous versions? I ask because in 16.0.0 the pool is really constrained, I've already given up on 3 sys-modules because the constant crahes

 

[masagrator]

The graph feature adds more memory usage than previous versions? I ask because in 16.0.0 the pool is really constrained, I've already given up on 3 sys-modules because the constant crahes

I have upgraded my FW to 16.0.0 to play Final Fantasy collection. I'm running Tesla, SaltyNX and sys-clk and have no issues related to memory exhaustion.
RAM usage is adjusted to mode that is used. Only static RAM usage is how much space executable itself take.

So 0.9.0 takes 389120 B vs 0.8.3 380928 B

~8kB increase

Now we can compare Full Mode which obviously should be the most RAM hungry vs FPS Graph. Since we cannot separate ovlloader heap and stack mappings from overlay mappings, this includes every mapping of the same type.
I'm testing Full Mode when game is running vs FPS Graph that is rendering graph with all positions busy.
First we can compare heaps (Graph vs Full):

5 599 232 B vs 5 562 368 B

so technically Graph takes more RAM?

Full Mode runs more threads. So now we check how much of RAM stacks and ThreadLocal are taking:

241 664 vs 282 224

So Full Mode needs more RAM to run threads.

So in total we have:
5 840 896 vs 5 844 592

So as you can see, FPS Graph actually takes 4 kB of RAM less than Full Mode.

 

[masagrator]

Uh, accidentally released 0.9.0 without libnx fix.

Download it again to get release that's not crashing randomly in docked mode.

 

[jnl1]

i get "inf" when enabling the FPS counter with the new 0.9 version of the status monitor overlay.
I use salty nx 0.5 and nx fps 0.4.

 

[masagrator]

i get "inf" when enabling the FPS counter with the new 0.9 version of the status monitor overlay.
I use salty nx 0.5 and nx fps 0.4.

Read changelog of 0.9.0 version carefully

And you can update SaltyNX too

 

[penna]

Maybe I'm a bonehead, but I absolutely cannot get the FPS counter working. I have your fork of SaltyNX 0.5.2 as well as NX-FPS 1.4.0. No matter what game I launch, the FPS Counter overlay always shows 254.0, and the Mini and Full menus don't show any of the FPS related data at all. I've restarted into emuNAND twice now and it's still the same.

Edit:

I am a Bonehead. Earlier in the day I updated all of my Sysmods but neglected to update Status Monitor, so I was still running an old version. Updating fixed it.