You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried Super Mario 64 (U)! on M64P with MangoHud,it shows that it runs in 60FPS,but it doesn't,it runs in 30FPS. https://i.imgur.com/4vSlYl8.jpg
I limited the fps for MangoHud to 60,so I assume that it could be that it shows the max fps that are possible with the fps lock.
Btw another problem is that I have to spam the shortcut for MangoHud until it starts for that Emulator instead of pressing it once.
The text was updated successfully, but these errors were encountered:
If no 60 fps cheat is enabled,no 60 patch or the video plugin of the emulator can run it in 60 or something that could make it possible that it runs at 60fps,it's in 25 or 30 fps according to this reddit tread https://www.reddit.com/r/nintendo/comments/1c0c5y/what_is_the_resolution_and_frame_rate_of_super/
If you don't trust reddit because there are trolls sometimes,there are extra 60 fps patches like this for example: https://www.youtube.com/watch?v=L_pYhVo2mEo&t=167s
They look much smoother than the normal game,and to be clear that it runs in 30fps,the emulators fps counter says that it runs at 30fps: https://i.imgur.com/cjjvVYZ.jpg
So if it really runs in 60fps because the fps counter in the emulator lies to me and I have a patched rom or I am wrong with anything I said,I will eat my shorts.
For the problem with,that I have to spam the shortcut to open MangoHud,only was because I made screenshots in the Emulator with the same key lol
I tried Super Mario 64 (U)! on M64P with MangoHud,it shows that it runs in 60FPS,but it doesn't,it runs in 30FPS.
https://i.imgur.com/4vSlYl8.jpg
I limited the fps for MangoHud to 60,so I assume that it could be that it shows the max fps that are possible with the fps lock.
Btw another problem is that I have to spam the shortcut for MangoHud until it starts for that Emulator instead of pressing it once.
The text was updated successfully, but these errors were encountered: