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

Does not restore proper screen resolution after fullscreen #17

Closed
Brottweiler opened this issue May 22, 2020 · 9 comments
Closed

Does not restore proper screen resolution after fullscreen #17

Brottweiler opened this issue May 22, 2020 · 9 comments

Comments

@Brottweiler
Copy link

I have had this issue playing both Sims 1 with Wine/Lutris, but also Faster Than Light when I set it to "fullscreen native". When quitting the game, majority of my screen is black. I only have like... a square in the top left corner which I can see my desktop. I think that area is 720p large.

I cannot see the wallpaper or taskbar, but I can see the cursor if I move it to the black area. To fix this I just relog.

@gijsbers
Copy link
Contributor

Is this perhaps related to bbidulock/icewm#427 ?
Is it possible to make a screenshot of what it looks like?
Best would be to make a screencast and give a link to a vid.

@Brottweiler
Copy link
Author

@gijsbers might very well be. Here is a video https://streamable.com/y1idct

I recorded my screen, but for whatever reason the actual game didn't show up in the video when I launched it the 2nd time. The second part obviously shows the issue I am referring to, and it happens after I quit the game when it is in native fullscreen mode (not borderless).

@gijsbers
Copy link
Contributor

Thanks for the vid. It's not clear that it is actually a window manager issue.
Could it be a display setting problem?
If you do xrandr before and again xrandr after, does that show differences?

@Brottweiler
Copy link
Author

xrandr seems to be identical before and after

Before

Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
DVI-D-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 531mm x 299mm
   1920x1080     60.00*+
   1680x1050     59.95
   1600x900      60.00
   1280x1024     75.02    60.02
   1280x800      59.81
   1280x720      60.00
   1024x768      75.03    60.00
   800x600       75.00    60.32
   640x480       75.00    59.94
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
VGA-1-1 disconnected (normal left inverted right x axis y axis)
HDMI-1-2 disconnected (normal left inverted right x axis y axis)
HDMI-1-3 disconnected (normal left inverted right x axis y axis)
HDMI-1-4 disconnected (normal left inverted right x axis y axis)

After

Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
DVI-D-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 531mm x 299mm
   1920x1080     60.00*+
   1680x1050     59.95
   1600x900      60.00
   1280x1024     75.02    60.02
   1280x800      59.81
   1280x720      60.00
   1024x768      75.03    60.00
   800x600       75.00    60.32
   640x480       75.00    59.94
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
VGA-1-1 disconnected (normal left inverted right x axis y axis)
HDMI-1-2 disconnected (normal left inverted right x axis y axis)
HDMI-1-3 disconnected (normal left inverted right x axis y axis)
HDMI-1-4 disconnected (normal left inverted right x axis y axis)

@gijsbers
Copy link
Contributor

So we can rule that out.
Does it matter what values you have set in preferences for:
LimitSize=1 # 0/1
LimitPosition=1 # 0/1
i.e. setting them to zero?

@Brottweiler
Copy link
Author

Setting those values to 0 does not seem to make any difference, no.

@gijsbers
Copy link
Contributor

The video shows that only part of the screen is drawn. There is some framebuffer or viewport restriction still active, which was used by the game. But icewm has no knowledge about that.

@gijsbers
Copy link
Contributor

This may well be fixed since 1.6.6.

@gijsbers
Copy link
Contributor

Fixed by commit 0973513 which was released in 1.7.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants