Homebrew WIP NX-FPS - SaltyNX plugin collecting FPS data

[jnl1]

How does the exceptions.txt work?
Name of the game followed by version of the game followed by title id?

For example:
;Immortals: Fenyx Rising
;1.0.1
01006E60131B6000

Would this be correct?

 

[masagrator]

How does the exceptions.txt work?
Name of the game followed by version of the game followed by title id?

For example:
;Immortals: Fenyx Rising
;1.0.1
01006E60131B6000

Would this be correct?

Only what it needs is titleid.

; are used only to comment what this titleid is and what is the issue. It's not required to write comments.

01006E60131B6000 means that no plugin will be loaded, but still it will try to bootstrap and apply asm64 patches.

X01006E60131B6000 means SaltyNX won't do anything for this game, avoiding bootstrapping

 

[IZUNYA]

Thanks a lot , i can load it now , i had to edit the exception TXT with the TID :

;Immortals: Fenyx Rising
;1.0.1
X01004A600EC0A000

 

[LinkMaster130693]

I can confirm is not working on Immortals Fenyx Rising. The plugin crashes the game before loading it. Can the plugin be unabled only for that game? And if it can, how?

 

[masagrator]

I can confirm is not working on Immortals Fenyx Rising. The plugin crashes the game before loading it. Can the plugin be unabled only for that game? And if it can, how?

Add titleid [...] to exceptions.txt

Only what it needs is titleid.

; are used only to comment what this titleid is and what is the issue. It's not required to write comments.

01006E60131B6000 means that no plugin will be loaded, but still it will try to bootstrap and apply asm64 patches.

X01006E60131B6000 means SaltyNX won't do anything for this game, avoiding bootstrapping

 

[LinkMaster130693]

Thanks. Successfully unabled for that title

 

[protivakid]

So SX-OS user here. I'm seeing 254 fps on everything. Looked over the readme, my setup seems correct so not sure what I am doing wrong. Any advice?

 

[nwhiteman42]

I saw this same behavior in Atmosphere and reinstalling SaltyNX fixed it for me. Used on FW 11.0.1 Atmosphere 0.18.1 and Status-Monitor 0.6.3

 

[clianvXAi]

I saw this same behavior in Atmosphere and reinstalling SaltyNX fixed it for me. Used on FW 11.0.1 Atmosphere 0.18.1 and Status-Monitor 0.6.3

What version of tesla did you used? I tried 1.06 and 1.04 but couldn’t make it work for fps counter to show in tesla. I use fw 11.0.1 and Atmosphere 0.18.1.

 

[Brandon10075]

Im using SXOS 3.1 (11.0.0) it works then it will randomly stop working, stuck at 30 sometimes 254, is there a fix? Thanks
ovlloader & tesla SaltyNX 0.4.0 at latest build

 

[masagrator]

Im using SXOS 3.1 (11.0.0) it works then it will randomly stop working, stuck at 30 sometimes 254, is there a fix? Thanks
ovlloader & tesla SaltyNX 0.4.0 at latest build

https://github.com/masagrator/SaltyNX/blob/master/README.md

 

[Brandon10075]

https://github.com/masagrator/SaltyNX/blob/master/README.md

i use it with ur MHR mods, does it consider as cheats that is causing the issue?
Thanks for the reply

 

[vahnkaiser]

After enabling the overlay I can't enter Tesla Menu with L+Down+R3 anymore, how do I disable nx-fps/Status-Monitor-Overlay?

 

[1basti1]

After enabling the overlay I can't enter Tesla Menu with L+Down+R3 anymore, how do I disable nx-fps/Status-Monitor-Overlay?

Press both sticks down for 1-2 seconds.

 

[Chrisssj2]

This plugin doesn't seem to work for me. using latest atmosphere for FW13 and latest saltynx.
As soon as I go into the status monitor menu to show fps. my switch freezes.

 

[zex90fz]

hi. is it possible to change the key combo to disable the overlay?

 

[masagrator]

hi. is it possible to change the key combo to disable the overlay?

This is not status monitor overlay topic.

 

[sofakng]

I'm using the newest HWFLY chip for the OLED switch but I'm a bit confused. I'm always seeing "254" in the FPS counter and the full/mini displays of the Status Overlay do not show the FPS.

The SaltyNX github contains the following info:

For SX OS remember to rename atmosphere folder to sxos

Does this mean I should have \sxos\contents\0000000000534C56\... ?

I obviously can't rename my existing \atmosphere folder because that would break everything else.

It appears to be somewhat working because when I start WarioWare it generates \SaltySD\saltysd.log and saltysd_core.log (which I've attached to this post).

Thanks for any help!

 

[masagrator]

Does this mean I should have \sxos\contents\0000000000534C56\... ?

And you're using SX OS? Answer yourself.

saltysd_core.log

"SaltySD Core: Plugins not detected..."

Well, guess what? You didn't install NX-FPS or at least not properly.

 

[masagrator]

For last few days I was reworking NX-FPS, Status Monitor and SaltyNX to support passing FPS data via SharedMemory.
SaltyNX is the one hosting SharedMemory.
Status Monitor and NX-FPS are taking copy-handle from SaltyNX and mapping memory.

Pros of this solution:
- Debugger is not more needed to read data, so dmnt:cht and svcdebug are completely gone from Status Monitor. This solves issues with microstutterings (not visible in video, but hearable from audio) and using it in the same time with other debuggers
- NX-FPS plugin now is not writing anything to sdcard
- Status Monitor now is not reading anything from sdcard (detection is handled by using SharedMemory).

This won't change existing SaltyNX compability issues.
Now is going through test phase if there is no memory leak or mishandling system.

If you want to test it yourself, you must compile SaltyNX, Status Monitor and NX-FPS from those PRs.
https://github.com/masagrator/SaltyNX/pull/22
https://github.com/masagrator/Status-Monitor-Overlay/pull/22
https://github.com/masagrator/NX-FPS/pull/7

Only known issue is that SaltyNX is not handling at all issues with SharedMemory reserved offsets.
This will impact usage ONLY if somebody would like to take advantage of SharedMemory and it would use it in combination with other plugin using SharedMemory like NX-FPS since you won't be able to determine what offset should be used.
This is something I want to fix before releasing it officially.