TASEmulators / TASEmulators/BizHawk
There is no "true" fullscreen
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.8k
- Forks
- 468
- PR merge metrics
- No merged PRs in 30d
Description
Apologies if this isn't the correct place to post something like this. This is more of a suggestion/enhancement.
I'm using BizHawk version 1.12.0, on Windows 10
There are 2 reasons I'd like to have fullscreen. One reason is for lower latency (fullscreen programs avoid Windows' vsync with aero enabled), and the other reason is a little silly...
I have a monitor with Nvidia G-sync support, which synchronizes the refresh rate of your monitor to the FPS of whatever fullscreen program is running. The NES runs at slightly below 60fps, and I'd like to use G-sync with BizHawk to avoid small framerate hitches caused by the NES framerate not matching my monitor refresh rate.
Within Nvidia control panel, there is a setting to enable G-sync for fullscreen as well as windowed programs. But even with that enabled, I've had no success getting my monitor to sync with bizhawk.
In BizHawk's display configuration, within the "Window" tab, there's a setting called "Enable Windows Fullscreen Hacks", and a description that explains that it prevents the program from going into "actual fullscreen". Even with that setting enabled or disabled, I still can't achieve real fullscreen.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in BizHawk's display configuration, specifically the Window tab and the "Enable Windows Fullscreen Hacks" setting. Reproduce the behavior on Windows 10 with the setting enabled and disabled, then investigate how each mode affects actual fullscreen, latency, and G-Sync. Done means BizHawk can enter true fullscreen and provide the requested synchronization behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop, operating-systems, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100