New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Slower performance on full screen Nvidia Optimus Laptop #1391
Comments
What emulator settings are you using, and what hacks do you have enabled (if any?) |
@Sarkie It is recognizing the Nvidia GPU without issue, and in newer builds I don't have to use d8tod9 anymore. |
Hack Run Xbox threads on all cores should be turned ofа - it brings instability and hangs. |
Ok, didn't know. But without it I can't get anywhere near full speed. Also, I'm getting the same issue with it off. Around 45 FPS on windowed mode, 35 FPS on full screen. |
Closing this as no response for a long time. |
Hello, I'm getting slower performance on full screen than on windowed mode. I have a Laptop with an Intel Core i5 6300HQ, 8 GB of RAM and a GTX 960M. The Laptop has Nvidia Optimus switchable graphics technology. The integrated GPU is an Intel HD 530. I'm using a 14 of August development build 0b0c342.
I added CXBX-R exe to the Nvidia Control Panel and selected the High Performance Nvidia GPU for it:
Testing Dead or Alive 2 Ultimate I get a locked 60 FPS gameplay on windowed mode. When on windowed mode the Nvidia GPU stays at around 30% utilization at 135 Mhz, while the Intel GPU stays at around 5% utilization (the first line in the overlay is the Nvidia GPU, the second line is the Intel GPU):
On full screen I get slower performance, around 10% to 20% less performance, dropping to the low 50s and high 40s FPS. When on full screen the Nvidia GPU stays the same at around 30% utilization at 135 Mhz, while the Intel GPU jumps to around 35% utilization:
I also tested Dead or Alive 3 and got similar results. I'm sure that this a very specific Optimus related issue, but I hope the cause can be identified and be fixed.
Thanks in advance.
The text was updated successfully, but these errors were encountered: