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

SDL2 X11 fullscreen regressions compared to SDL1 #2218

Closed
SDLBugzilla opened this issue Feb 11, 2021 · 0 comments
Closed

SDL2 X11 fullscreen regressions compared to SDL1 #2218

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: 2.0.4
Reported for operating system, platform: Linux, x86

Comments on the original bug report:

On 2016-07-08 16:46:35 +0000, Monsterovich wrote:

Created attachment 2529
Bug screenshot.

  • SDL_WINDOW_FULLSCREEN_DESKTOP works, but it isn't true fullscreen, resulting in severe performance loss (2-5x).
  • SDL_WINDOW_FULLSCREEN is bugged (see screenshot). But it doesn't look like the true fullscreen mode that was in 1.2, because the whole desktop behind my SDL window is drawn.

On 2016-07-08 20:03:52 +0000, Philipp Wiesemann wrote:

Is this only with SDL 2.0.0 (as selected above) or still with SDL 2.0.4?

On 2016-07-08 20:42:31 +0000, Monsterovich wrote:

I have 2.0.2, but it still happens in 2.0.4.

On 2016-07-11 04:07:10 +0000, Ryan C. Gordon wrote:

9 times out of ten, this is because SDL was built without XRandR support. It should be able to change the screen's hardware resolution when using SDL_WINDOW_FULLSCREEN, presuming the screen supports the requested resolution.

If you don't have XRandR support (either because SDL was built without it or your X server doesn't support it) SDL will fall back to something like the XVidMode extension, which is generally bad, and our code for it is buggy and hopefully being removed outright soon.

Can you verify your app is using XRandR for me?

--ryan.

On 2016-07-12 18:20:20 +0000, Monsterovich wrote:

Can you verify your app is using XRandR for me?

--enable-video-x11-xrandr
enable X11 Xrandr extension for fullscreen
[[default=yes]]

X11 libraries : xcursor xdbe xinerama xinput2 xinput2_multitouch xrandr xscrnsaver xshape xvidmode

Configure script says that xrandr was enabled by default. I recompiled SDL with this flag, this bug is still present.

If you don't have XRandR support

It's installed on linux mint by default too.

On 2016-07-13 03:51:26 +0000, Ryan C. Gordon wrote:

Are you setting a resolution that the hardware doesn't support? SDL 1.2 would center the game's window in a second black window that covered the desktop in this scenario, but SDL2 doesn't do this.

--ryan.

On 2016-07-13 13:24:03 +0000, Monsterovich wrote:

(In reply to Ryan C. Gordon from comment # 5)

Are you setting a resolution that the hardware doesn't support? SDL 1.2
would center the game's window in a second black window that covered the
desktop in this scenario, but SDL2 doesn't do this.

--ryan.

I have 1280x1024 on my screen, but if I use any resolution lower than this, this bug appears.

On 2016-08-27 10:18:14 +0000, Monsterovich wrote:

Is this bug fixed in the lastest SDL revision?

On 2018-08-06 21:20:25 +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