libretro / parallel-n64

Optimized/rewritten Nintendo 64 emulator made specifically for Libretro. Originally based on Mupen64 Plus.
310 stars 128 forks source link

Low framerate in standard mode yet crazy high framerate in fast forward mode #665

Open HelicopterP opened 4 years ago

HelicopterP commented 4 years ago

I'm runnig Win10 64bit+i7 8700+GTX1070+ Retroarch 1.8.7+ Vulkan driver

I will use Conker's Bad Fur Day as an example, but this issue affects other demanding games. During intro cutscene (the one with chainsaw and Nintendo logo) I get drops to 48 fps, but if I press Fast Forward key the framerate will go up to 160-200FPS. I tested it with both angrylion and parallel renderers. (To see the issue with Parallel i need to use fullspeed mode because original mode is fast enough. On the other hand there is a bug with Conker - original mode reports 60 FPS (VIs), but the game is clearly runnig with lower framerate/bad framepacing, like way below slowdowns on real N64. Anyways, this is unrelated).

I think this isue is unrelated to Vsync, as I don't see any tearing with FF enabled.

Similar bug affects Muppen64Next maintained by m4xw

victordg-github commented 4 years ago

I'm running Linux (5.5, 5.6, 5.7), Ubuntu and Manjaro, RetroArch 1.8.8 and Vulkan, with nvidia-prime-440-82 Intel+MX150.

I confirm this also happens with Conker and other typically difficult-to-emulate games. FF can go up to 200FPS but at normal rate there are occasional hiccups and it's not always smooth. It's also very noticeable on Body Harvest, continuous audio stutter despite FF is able to reach 160FPS. Same goes for Indiana Jones, Star Wars Racer, and the usual Factor5 games. I suppose is due to the special usage of the N64 hardware they did.

bluelightzero commented 2 years ago

I have this with both Zelda 64 games OOT and MM.

I find some busy areas drop to about 58fps and the audio sounds garbled.

I can run the game just fine at 250fps otherwise with Fast forward.

GitMoDu commented 2 years ago

If you're on Nvidia GPU, try going into Nvidia Control Panel 3D settings, and for RA specifically, switch power mode to "performance".

I think this is becomming a common issue, and sadly I believe the best way to counter it is by integrating the Nvidia Reflex SDK calls, to keep the GPU from throttling down between frames.

Immersion95 commented 7 months ago

Same thing here with AMD :(