http://bugs.winehq.org/show_bug.cgi?id=60532 Bug ID: 60532 Summary: Black Desert Online: starting in borderless fullscreen leaves frame-sized insets until switching fullscreen modes Product: Wine Version: 11.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@list.winehq.org Reporter: ax+3lzp806u@fxzx.ident.com.es Target Milestone: --- Distribution: --- Created attachment 82394 --> http://bugs.winehq.org/attachment.cgi?id=82394 winedebug log ## Steps to reproduce 1. Configure Black Desert Online to start in borderless fullscreen mode. 2. Exit and launch the game again. 3. Observe the empty black strip at the top of the game window. The game image occupies a smaller area; its contents appear compressed into that area rather than cropped. 4. In the game settings, switch to fullscreen, then back to borderless fullscreen. 5. The image now fills the window. Restarting directly in fullscreen also displays correctly. ## Expected behavior Starting directly in borderless fullscreen fills the window, as it does after switching from fullscreen back to borderless fullscreen. ## Window geometry The top-level X11 window is at `(0,0)`, has size `1536×960`, and has zero X11 border width in both states. Its XID remains the same across the mode switch. Its single child also retains the same XID, but its geometry changes: | State | Child size | Child position relative to the top-level window | |---|---|---| | Started in borderless fullscreen, black strip visible | 1528×926 | +4+30 | | After fullscreen → borderless fullscreen | 1536×960 | +0+0 | In the first state, this leaves 4 pixels on the left, 4 on the right, 30 at the top, and 4 at the bottom. ## Observed Wine trace The following excerpts are from one logged run. In that run, the game HWND is `0x701dc`, the top-level XID is `0x3400005`, and the client XID is `0x3c0006a`. During startup, the trace first reports style `84cf0000` and client rectangle `(4,30)-(1532,956)`. It then records `GWL_STYLE` and `GWL_EXSTYLE` being set to zero: ```text 72433.563:0acc:0ad0:trace:win:set_window_long_internal 0x701dc -16 0 W 72433.563:0acc:0ad0:trace:win:set_window_long_internal 0x701dc -20 0 W ``` The subsequent `calc_winpos` entry requests `1536×960` with flags `00001a00` (without `SWP_FRAMECHANGED`). The style reported there is `04000000`. The following `X11DRV_WindowPosChanged` entry still reports: ```text window (0,0)-(1536,960) client (4,30)-(1532,956) visible (0,0)-(1536,960) flags 80001a0b ``` The client X11 geometry request is then: ```text 72434.402:0acc:0ad0:trace:x11drv:client_surface_update_geometry client window 0x701dc/3c0006a, requesting position 4,30 size 1528,926 mask 0xf ``` During the manual fullscreen switch, a `calc_winpos` entry for the same HWND requests `1536×960` with flags `00001870`, which include `SWP_FRAMECHANGED`. The next entries show the client rectangle and child geometry changing: ```text 72548.891:0acc:0ad0:trace:win:calc_ncsize hwnd 0x701dc old win (0,0)-(1536,960) old client (4,30)-(1532,956) new win (0,0)-(1536,960) new client (0,0)-(1536,960) 72548.891:0acc:0ad0:trace:x11drv:client_surface_update_geometry client window 0x701dc/3c0006a, requesting position 0,0 size 1536,960 mask 0xf ``` After switching back to borderless fullscreen, the client rectangle remains `(0,0)-(1536,960)` and the black strip is absent. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.