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

Huge black bar on right side of screen when running in 4:3 #3817

Open
mxaddict opened this issue Aug 10, 2024 · 16 comments
Open

Huge black bar on right side of screen when running in 4:3 #3817

mxaddict opened this issue Aug 10, 2024 · 16 comments
Labels

Comments

@mxaddict
Copy link

Your system information

  • System information from steam:
Computer Information:
Manufacturer: Gigabyte Technology Co., Ltd.
Model: X670 AORUS ELITE AX
Form Factor: Desktop
No Touch Input Detected
Processor Information:
CPU Vendor: AuthenticAMD
CPU Brand: AMD Ryzen 9 7950X 16-Core Processor
CPU Family: 0x19
CPU Model: 0x61
CPU Stepping: 0x2
CPU Type: 0x0
Speed: 5881 MHz
32 logical processors
16 physical processors
Hyper-threading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Supported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Supported
AVX512F: Supported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Supported
AVX512VNNI: Supported
SHA: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
Operating System Version:
"Arch Linux" (64 bit)
Kernel Name: Linux
Kernel Version: 6.10.3-arch1-2
X Server Vendor: The X.Org Foundation
X Server Release: 12401002
X Window Manager: Hyprland :D
Steam Runtime Version: steam-runtime_0.20240610.91380
Video Card:
Driver: AMD AMD Radeon RX 7900 XTX (radeonsi, navi31, LLVM 18.1.8, DRM 3.57, 6.10.3-arch1-2)
Driver Version: 4.6 (Compatibility Profile) Mesa 24.1.5-arch1.1
OpenGL Version: 4.6
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 179 Hz
VendorID: 0x1002
DeviceID: 0x164e
Revision Not Detected
Number of Monitors: 1
Number of Logical Video Cards: 2
Primary Display Resolution: 2560 x 1440
Desktop Resolution: 2560 x 1440
Primary Display Size: 23.62" x 13.39" (27.13" diag), 60.0cm x 34.0cm (68.9cm diag)
Primary VRAM: 24576 MB
Sound card:
Audio device: ATI R6xx HDMI
Memory:
RAM: 63433 Mb
VR Hardware:
VR Headset: None detected
Miscellaneous:
UI Language: English
LANG: en_US.UTF-8
Total Hard Disk Space Available: 937291 MB
Largest Free Hard Disk Block: 399051 MB
Storage:
Number of SSDs: 3
SSD sizes: 4000G,1000G,1000G
Number of HDDs: 0
Number of removable drives: 0

  • Have you checked for system updates?: Yes

Please describe your issue in as much detail as possible:

Should get 4:3 resolution when running 4:3 resolution, instead get a huge black bar on the right of the screen

Steps for reproducing this issue:

  1. Launch CS2
  2. Change resolution to 4:3
  3. Apply Changes

image

@mxaddict
Copy link
Author

Tested DOTA2 and this is not an issue in DOTA2

@mxaddict
Copy link
Author

Running 4:3 that is not same height as my native resolution seems to work fine!

image

@polluxau
Copy link

polluxau commented Aug 18, 2024

Using gamescope can fix this also

https://github.com/ValveSoftware/gamescope

@mxaddict
Copy link
Author

mxaddict commented Aug 18, 2024 via email

@polluxau
Copy link

polluxau commented Aug 18, 2024

Replying to #3817 (comment)

Is the resolution the same in game with the nested resolution you have specified?

Can i have your launch command so i can test it aswell :)

@mxaddict
Copy link
Author

gamescope running at native res, in game res and nested res set to 1920x1440

gamescoperun -W 2560 -H 1440 -w 1920 -h 1440 %command% -w 1920 -h 1440

@mxaddict
Copy link
Author

When running in gamescope, the bars are gone, but sensitivity for mouse input is half when moving left and correct speed when moving right.

@mxaddict
Copy link
Author

And steam overlay does not work when using gamescope, even when setting --steam/-e

@mxaddict
Copy link
Author

When running gamescope with auto backend it freezes when changing focus
Running gamescope with backend sdl works
Running gamescope with backend wayland it crashes

@polluxau
Copy link

polluxau commented Aug 18, 2024

And steam overlay does not work when using gamescope, even when setting --steam/-e

yes that is currently a bug with gamescope

if you instead just use the nested res and specify the 4:3 res and use the -S stretched variable this should work

so here is what it would be
gamescope -w 1920 -h 1440 -S stretch -f -e --force-grab-cursor %command%

then change it to the res in game also, there isnt a sens issue that i can see

@mxaddict
Copy link
Author

Yes, I have scaler set to stretch, but can't play due to sense issue.

Currently I just play without gamescope and just set my desktop display res to 4:3 before playing.

@mxaddict
Copy link
Author

Then reset my display res after playing

@polluxau
Copy link

Yes, I have scaler set to stretch, but can't play due to sense issue.

Currently I just play without gamescope and just set my desktop display res to 4:3 before playing.

hm ok nvm then, if that works for you then no problems

@mxaddict
Copy link
Author

This issue seems to also be specific to just cs2's implementation of source2 game engine, as dota 2 does not have this issue.

Running dota2 in 4:3 works perfectly (Not really a reason to run the game at this res, but it works 😄 )

@ilievi187
Copy link

This issue seems to also be specific to just cs2's implementation of source2 game engine, as dota 2 does not have this issue.

Running dota2 in 4:3 works perfectly (Not really a reason to run the game at this res, but it works 😄 )

same issue mentionet since CS:GO and DXVK ...

@Bookaj
Copy link

Bookaj commented Sep 10, 2024

This issue seems to also be specific to just cs2's implementation of source2 game engine, as dota 2 does not have this issue.

Running dota2 in 4:3 works perfectly (Not really a reason to run the game at this res, but it works 😄 )

Running Garuda XFCE4, black bars and sensitivity scaling issue can be fixed simply by changing the native resolution to whatever you want to run the game at for the session.

I am however experiencing some form of input lag, but can't really put my finger on it just yet.

I think raw input is a general issue for the game regardless of the OS.

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

No branches or pull requests

5 participants