Homebrew WIP NX-FPS - SaltyNX plugin collecting FPS data

  • Thread starter Thread starter masagrator
  • Start date Start date
  • Views Views 104,069
  • Replies Replies 160
  • Likes Likes 20
Works for me with SX OS 2.9.5 beta, NX FPS 0.3, Status Monitor Overlay 0.6.0, Tesla Menu v1.1.3, NX-Ovlloader v1.0.6, Salty NX 0.3.1a
I have the same files. How do you use it? put fps counter on before game or ingame? I tried both. And it seems always stuck at 255 for me.
 
I have the same files. How do you use it? put fps counter on before game or ingame? I tried both. And it seems always stuck at 255 for me.
If you have 255, either you have old status monitor or game not compatible with NX-FPS.
Update all stuff and try again.
 
  • Like
Reactions: Chrisssj2
If you have 255, either you have old status monitor or game not compatible with NX-FPS.
Update all stuff and try again.
I did that 3 times already. Put all latest versions over it... Im not joking lol. Guess im either trying games that are just not compatible then? Thats why I asked which game is known to be compatible.
 
I did that 3 times already. Put all latest versions over it... Im not joking lol. Guess im either trying games that are just not compatible then? Thats why I asked which game is known to be compatible.
I tried it in gear club unlimited 2 and in super pixel racers. Both worked fine
 
  • Like
Reactions: Chrisssj2
I was playing borderlands and it was working fine. Then I played it later the same day and the FPS was stuck on the 250 error. It's maybe just wonky with TXOS?
If you will run Status Monitor when game is booting, FPS counter may glitch and you need to restart game.
Open status monitor before or after game boot.
 
  • Like
Reactions: Purple_Shyguy
I have a Homebrew Launcher Game tile (so I don't have to press R when launching a game). Sometimes it crashes and NX FPS/SaltyNX isn't working anymore, till I restart the system. (SaltyNX is still injected) It don't happen all the time, but 1 in 10 maybe. Is this normal? :wacko:


10.0.2
Atmosphere 0.12.0

It was never a problem, I don't know when it started, maybe with Switch OS 10, but I don't know.
 
Last edited by 1basti1,
I have a Homebrew Launcher Game tile (so I don't have to press R when launching a game). Sometimes it crashes and NX FPS/SaltyNX isn't working anymore, till I restart the system. (SaltyNX is still injected) It don't happen all the time, but 1 in 10 maybe. Is this normal? :wacko:

10.0.2
Atmosphere 0.12.0

It was never a problem, I don't know when it started, maybe with Switch OS 10, but I don't know.

If your launcher Has titleid in game range, then yes - this may happen.
Add titleid of your launcher to exceptions.txt or change titleid of your launcher.
 
Last edited by masagrator,
  • Like
Reactions: 1basti1
Ok, I'll try to add it to exceptions.txt
On that note, FIFA 18 also crashes when trying to connect online. I added it to exceptions.txt but it still crashes.
Can you tell if I did something wrong here?

exceptions.txt

;Darksiders II Deathnitive Edition
;1.0.0 has double speed gameplay
010071800BA98000

;GRID: Autosport
;1.4.0RC9 and 1.5_46790 crash, 1.4.1_45339 stucks in infinite loop
0100DC800A602000

;Luigi's Mansion 3
;1.0.0-1.3.0 crash
0100DCA0064A6000

;Tesla Menu
;Just in case (old titleid, new one is blacklisted by internal titleid validating)
X010000000007E51A

;YouTube
;Stucks in infinite loop
X01003A400C3DA000

;Alien: Isolation
;1.1_46609 - 1.1.2_47610 crashes on first loading
010075D00E8BA000

;FIFA 20
;1.0.0 - 1.0.3 after checking Nintendo servers abruptly closes and doesn't close all services, which results in game crash and high chance of OS crash at boot of next title
01005DE00D05C000

;FIFA 18
;Crashes then trying to connect online
0100F7B002340000

;Homebrew Menu
;Crashes sometimes on startup
0104444444441001

edit: FIFA 18 has 2 titleids (I guess it changed with an update...?) The titleid I used was shown to me in tinfoil. My version is 1.07
 
Last edited by 1basti1,
If it crashes only when SaltyNX is enabled, then something must be wrong with your titleid. If you will add X before titleid, it will not even run Core. If after adding X it will still crash, your titleid must be wrong. You can confirm that by looking at log.
 
  • Like
Reactions: 1basti1
If it crashes only when SaltyNX is enabled, then something must be wrong with your titleid. If you will add X before titleid, it will not even run Core. If after adding X it will still crash, your titleid must be wrong. You can confirm that by looking at log.
Ok, the X helped. Thanks again. HBmenu also crashed again, I added an X there as well.
You are so helpful. I really appreciate it! :)
 

Site & Scene News

Popular threads in this forum