Skip to content
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

Windows: SDL_WINDOW_FULLSCREEN_DESKTOP + OpenGL broken for non-native desktop resolutions #2061

Closed
SDLBugzilla opened this issue Feb 11, 2021 · 0 comments
Labels
abandoned Bug has been abandoned for various reasons

Comments

@SDLBugzilla
Copy link
Collaborator

This bug report was migrated from our old Bugzilla tracker.

These attachments are available in the static archive:

Reported in version: HG 2.1
Reported for operating system, platform: Other, x86_64

Comments on the original bug report:

On 2016-01-04 00:06:31 +0000, Eric Wasylishen wrote:

OS: Windows 10 version 1511
SDL2 version: d91a2c45825e (Jan 3, 2016)
Nvidia driver: 353.62

Steps to reproduce:

  • Set your Windows desktop resolution to a non-native resolution for your LCD panel. Tested with a MacBook Pro (native 2880x1800, set to 1920x1200), and a BenQ LCD (native 1920x1080, set to 1680x1050)
  • Launch the testgl2 SDL sample
  • Press ALT+Enter to enter fullscreen desktop mode

Expected:

  • Spinning cube appears in fullscreen

Actual:

  • The spinning cube is visible but the screen flickers solid black.

Workarounds:

  • The bug doesn't happen with samples that use the renderer api like testdraw2
  • The bug doesn't happen if I switch Windows to use the monitor's native resolution first.

On 2017-07-14 20:37:18 +0000, Eric Wasylishen wrote:

Still reproduces on current SDL HG,
Windows 10 version 1703 build 15063.447

On 2017-07-21 18:09:47 +0000, Eric Wasylishen wrote:

It seems to be specific to the nVidia OpenGL driver.

If I extract the opengl32.dll and other .dll's from this software GL renderer in the same directory as testgl2, the bug is no longer reproducible:
https://github.com/pal1000/mesa-dist-win/releases/tag/17.1.5.401-1

On 2017-08-12 21:48:47 +0000, Sam Lantinga wrote:

I don't think we can fix this if it's really a bug in the NVIDIA driver. Given that it's specific to non-native LCD resolutions it sounds like that is the case.

Can you try with the latest NVIDIA driver? If you can still reproduce it, can you attach a full test case that I can pass on to NVIDIA's driver team?

Thanks!

On 2017-08-13 00:11:31 +0000, Eric Wasylishen wrote:

Created attachment 2830
Build of testgl2.exe from cbc9323b7167

Yeah - it's got to be some kind of driver bug. I reproduced on 384.94 (latest stable driver for my GT 650m) as well 385.12 (latest beta).

The weird thing is if you set the resolution in the NVIDIA Control Panel, the bug doesn't happen, it's only when the non-native resolution was set in the Windows display settings.

For a test case I just attached testgl2.exe compiled from this revision (from today): https://hg.libsdl.org/SDL/rev/cbc9323b7167

the steps to reproduce are:

  • Windows 10 Home, version 10.0.15063 Build 15063
  • GT 650m 1024MB
  • NVIDIA driver 384.94 or 385.12
  • the laptop is a macbook pro retina, the native res is 2880x1800. I can also reproduce it with an external monitor 1920x1080 connected over displayport.
  1. Right-click on the Windows desktop and choose "display settings"
  2. Choose a non-native resolution (e.g. choose 1920x1080 for the 2880x1800 lcd), and 100% scaling.
  3. Run testgl2.exe, press alt+enter. Expected: the spinning cube fills the screen, observed: a black screen.

Setting the resolution in step 2 via NVIDIA Control Panel will cause the bug to no longer reproduce, i.e. step 3 works as expected.

On 2018-08-06 21:20:18 +0000, Ryan C. Gordon wrote:

Hello, and sorry if you're getting dozens of copies of this message by email.

We are closing out bugs that appear to be abandoned in some form. This can happen for lots of reasons: we couldn't reproduce it, conversation faded out, the bug was noted as fixed in a comment but we forgot to mark it resolved, the report is good but the fix is impractical, we fixed it a long time ago without realizing there was an associated report, etc.

Individually, any of these bugs might have a better resolution (such as WONTFIX or WORKSFORME or INVALID) but we've added a new resolution of ABANDONED to make this easily searchable and make it clear that it's not necessarily unreasonable to revive a given bug report.

So if this bug is still a going concern and you feel it should still be open: please feel free to reopen it! But unless you respond, we'd like to consider these bugs closed, as many of them are several years old and overwhelming our ability to prioritize recent issues.

(please note that hundred of bug reports were sorted through here, so we apologize for any human error. Just reopen the bug in that case!)

Thanks,
--ryan.

@SDLBugzilla SDLBugzilla added abandoned Bug has been abandoned for various reasons bug labels Feb 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
abandoned Bug has been abandoned for various reasons
Projects
None yet
Development

No branches or pull requests

1 participant