It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
I've put together a Wine wrapper for Clive Barker's Undying, allowing it to be played on Linux almost like a native game & with no Wine knowledge required.

Simply run the build script to create the wrapper. If the installer files are not alongside the wrapper build files then the path to them will need to be specified either by passing it as an argument to the build script with -respath="<path>" or by setting an environment variable named WINEWRAP_RESPATH containing it. You can change the path to build the wrapper in and the name of the wrapper directory with the -buildpath= and -dirname= arguments. The build path can also be set with the WINEWRAP_BUILDPATH environment variable.

The output will be a directory containing the game set up within a preconfigured Wine prefix, along with its own copy of Wine, extracted game icons, documentation, and start script(s). From there simply run the start script to play. The start script also includes options for creating a shortcut, configuring the wrapper etc.

(to uninstall simply delete the game directory and any shortcuts you created, and the game's user data directory in ~/.local/share if you don't want to keep your saves & settings)

User data is stored under ~/.local/share/undying

Full details are in the readme.txt and release notes. Here is the download link:

undying_wine.tar.xz
(3.2 MB, SHA256: 0b0ffd688a2be81a1c1c6ba7ceb390fbb88a2cfc2c5ac7d9430621ca9350d70b)

Updated 2019/09/28: Updated winewrap.shlib.

The wrapper uses Wine 4.0. Wine and Winetricks will be downloaded automatically if not present; to avoid redownloading for other scripts the downloaded Wine package will be stored in ~/.cache/winewrap

This wrapper also includes the widescreen fix created by drennan. For more information see this thread: https://www.gog.com/forum/clive_barkers_undying/widescreen_working_correctly/post14

If anyone encounters any problems then post in this thread, Adamhm's Linux Wine Wrappers - News, FAQ &amp; Discussion and/or The "Judas&trade; does this run in Wine" thread v1.173.

For more of my Linux Wine wrappers check out post 3 in this thread: Adamhm's Linux Wine Wrappers - News, FAQ &amp; Discussion
Post edited September 28, 2019 by adamhm
Works like a charm, thanks!

Ubuntu 18.04.1 Mate / Linux kernel 4.15.0-42
Pentium 3550M @2.3GHz / 4GB RAM / Intel HD Graphics
Attachments:
undying.jpg (292 Kb)
undying2.jpg (427 Kb)
Unfortunatelly the wrapped game does not work correctly for me. The screen is messed up and displaced, and when the New Game is launched, the game starts for a second and crashes (with the error as shown on the attached screenshots).

Changing nGlide settings does nothing to the resolution, the in-game video options show some ludicrous data. Changing the device to Direct3D makes the game work, but only in small resolutions up to 1024x768, however the game still forces widescreen which makes it look stretched.

EDIT: The crashed game still runs in the background despite closing the terminal in which it was launched. It has to be killed manually through the system monitor or terminal.

Linux Mint 19 x86-64, Ryzen 2400G with integrated Vega gpu, 16 GB RAM, Mesa 18.2.3, Kernel 4.19.8. I have 2 screens attached (Primary: 2560x1440 Secondary: 1920x1080), The game was started on the primary wqhd display.
Attachments:
Post edited December 15, 2018 by valgaav
avatar
valgaav: Changing nGlide settings does nothing to the resolution, the in-game video options show some ludicrous data. Changing the device to Direct3D makes the game work, but only in small resolutions up to 1024x768, however the game still forces widescreen which makes it look stretched.

Linux Mint 19 x86-64, Ryzen 2400G with integrated Vega gpu, 16 GB RAM, Mesa 18.2.3, Kernel 4.19.8. I have 2 screens attached (Primary: 2560x1440 Secondary: 1920x1080), The game was started on the primary wqhd display.
From the sounds of things it could be due to your iGPU (AFAIK the drivers for those are still a bit broken) or the game might be getting confused by the multi-monitor setup. You could try running the game inside a virtual desktop & seeing if that helps - run the start script with the argument "desktop=2560x1440", e.g.:

./start.sh play desktop=2560x1440
avatar
valgaav: EDIT: The crashed game still runs in the background despite closing the terminal in which it was launched. It has to be killed manually through the system monitor or terminal.
You can also use the start script to kill all processes that are running using the wrapper: ./start.sh kill
(this should also ensure that the wineserver is properly terminated)
Just tried using a virtual desktop (although I used a 1920x1080 resolution for comfort) following your advice. The behavior is exactly the same (screenshots attached).

Currently Raven Ridge is 99,9% stable under Linux with the 4.19 kernel and the 18.2+ mesa drivers. I run multiple Wine games on it (including games based on the Unreal engine, and games using nGlide like Star Wars Racer, all worked perfectly in 2560x1080 when having two screens attached). In fact, I finished Undying on this machine a couple of months ago after installing it using Play On Linux (it worked out of the box on Wine 3.0 using 4:3 resolutions).

I strongly suspect it's the widescreen fix that is braking the compatibility. If you'll need any logs or additional info, I'm ready to provide those.
Attachments:
It works fine on the systems I've tested it on here:

- Main system: Linux Mint 19, Ryzen 1700, 16GB RAM, RX 480 8GB, Mesa 18.3 (via Padoka stable PPA), kernel 4.15.0-42 (I fully played through the game on this system using my wrapper without any issues)
- Old system: Linux Mint 18, i7-2600k, 16GB RAM, GTX 750 Ti, Nvidia proprietary drivers, kernel 4.15.0-42
- Intel test system: Linux Mint 19, i3-6100, 4GB RAM, using HD 530 integrated graphics, Mesa 18.3 (via Padoka stable PPA), kernel 4.15.0-42 (this is basically a clean install with little more than updates and my common dependencies meta-package installed)

(all are single display setups though - 1920x1200, 1600x900, 1680x1050 respectively)

Another thing you can try is running the start script like so and monitoring the terminal output to look for any errors:

WINEDEBUG="" ./start.sh play

It's possible that you may be missing one or more dependencies - PlayOnLinux bundle a lot of libaries with their Wine builds, which I remove as they have been known to cause conflicts and breakages on some systems. That might explain why it worked with PlayOnLinux but not my wrapper.

If you still want to try disabling the widescreen fix then go to the game's System directory (<wrapper path>/gamedir/System) and rename GlideDrv.dll and UndyingShellPC.u to something else then remove .bak from the filenames of the original non-widescreen versions (GlideDrv.dll.bak and UndyingShellPC.u.bak).
Post edited December 16, 2018 by adamhm
I installed it on Play on Linux without any installation scripts (as an unlisted program) so there shouldn't be any dependencies installed. Just chose wine version.

That's the output of the WINEDEBUG command (virtual desktop and fullscreen respectively):

WINEDEBUG="" ./start.sh play desktop=1920x1080
Current desktop resolution: 4480x1682
Detected 4 display output(s). Connected outputs:
HDMI-A-0: 2560x1440
DisplayPort-1: 1920x1080
Gamma (R/G/B) = 1.000 / 1.000 / 1.000
Userdata directory: /home/ /.local/share/undying
Running: Undying.exe
Working directory: /home/ /Pobrane/CB UND/undying_wine/Undying/prefix/drive_c/Undying/System
Using virtual desktop with resolution: 1920x1080
wine: cannot find L"C:\\windows\\system32\\winemenubuilder.exe"
000b:err:wineboot:ProcessRunKeys Error running cmd L"C:\\windows\\system32\\winemenubuilder.exe -a -r" (2)
0027:err:module:load_builtin_dll failed to load .so lib for builtin L"winebus.sys": libudev.so.0: nie można otworzyć pliku obiektu dzielonego: Nie ma takiego pliku ani katalogu
0027:err:winedevice:async_create_driver failed to create driver L"WineBus": c0000142
002d:fixme:process:GetProcessWorkingSetSizeEx (0xffffffff,0x33f6cc,0x33f6c4,(nil)): stub
002d:err:winediag:wined3d_dll_init Setting multithreaded command stream to 0x1.
002d:fixme:win:EnumDisplayDevicesW ((null),0,0x33f268,0x00000000), stub!
002d:fixme:win:EnumDisplayDevicesW ((null),0,0x336838,0x00000000), stub!
002d:fixme:d3d:debug_d3dformat Unrecognized 0x36314644 (as fourcc: DF16) WINED3DFORMAT!
002d:fixme:d3d:wined3d_get_format Can't find format unrecognized (0x36314644) in the format lookup table.
002d:fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24) WINED3DFORMAT!
002d:fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the format lookup table.
002d:err:ole:CoGetClassObject class {92fa2c24-253c-11d2-90fb-006008a1f441} not registered
002d:err:ole:CoGetClassObject no class object {92fa2c24-253c-11d2-90fb-006008a1f441} could be created for context 0x1
002d:err:ole:CoGetClassObject class {d8f1eee0-f634-11cf-8700-00a0245d918b} not registered
002d:err:ole:CoGetClassObject no class object {d8f1eee0-f634-11cf-8700-00a0245d918b} could be created for context 0x1
-> Red 1.181, Green 1.181, Blue 1.181
<- Red 1.000, Green 1.000, Blue 1.000

WINEDEBUG="" ./start.sh play
Current desktop resolution: 4480x1682
Detected 4 display output(s). Connected outputs:
HDMI-A-0: 2560x1440
DisplayPort-1: 1920x1080
Gamma (R/G/B) = 1.000 / 1.000 / 1.000
Userdata directory: /home/ /.local/share/undying
Running: Undying.exe
Working directory: /home/ /Pobrane/CB UND/undying_wine/Undying/prefix/drive_c/Undying/System
Not forcing virtual desktop
wine: cannot find L"C:\\windows\\system32\\winemenubuilder.exe"
000b:err:wineboot:ProcessRunKeys Error running cmd L"C:\\windows\\system32\\winemenubuilder.exe -a -r" (2)
0025:err:module:load_builtin_dll failed to load .so lib for builtin L"winebus.sys": libudev.so.0: nie można otworzyć pliku obiektu dzielonego: Nie ma takiego pliku ani katalogu
0025:err:winedevice:async_create_driver failed to create driver L"WineBus": c0000142
0009:fixme:process:GetProcessWorkingSetSizeEx (0xffffffff,0x33f6cc,0x33f6c4,(nil)): stub
0009:err:winediag:wined3d_dll_init Setting multithreaded command stream to 0x1.
0009:fixme:win:EnumDisplayDevicesW ((null),0,0x33f268,0x00000000), stub!
0009:fixme:win:EnumDisplayDevicesW ((null),0,0x336838,0x00000000), stub!
0009:fixme:d3d:debug_d3dformat Unrecognized 0x36314644 (as fourcc: DF16) WINED3DFORMAT!
0009:fixme:d3d:wined3d_get_format Can't find format unrecognized (0x36314644) in the format lookup table.
0009:fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24) WINED3DFORMAT!
0009:fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the format lookup table.
0009:err:ole:CoGetClassObject class {92fa2c24-253c-11d2-90fb-006008a1f441} not registered
0009:err:ole:CoGetClassObject no class object {92fa2c24-253c-11d2-90fb-006008a1f441} could be created for context 0x1
0009:err:ole:CoGetClassObject class {d8f1eee0-f634-11cf-8700-00a0245d918b} not registered
0009:err:ole:CoGetClassObject no class object {d8f1eee0-f634-11cf-8700-00a0245d918b} could be created for context 0x1
-> Red 1.181, Green 1.181, Blue 1.181
<- Red 1.000, Green 1.000, Blue 1.000
Post edited December 16, 2018 by valgaav
I did some more experiments. I've installed it using PlayOnLinux with WINE 3.0.3 without any addtional installations. Works out of the box. Looks best when nGlide is set to the desktop resolution and to preserve the original aspect ratio.

I also installed the widescreen "fix" and it... works. Although this fix is more of a gimmick (like most widescreen "fixes"). Large parts of the weapon and player model are hidden by the screen which changes the look and feel of the game. I would propose to not include this in the wrapper by default and just allow the installation in your start menu.

The two things that are wrong are a strange bug with screen saturation and performance under nGlide. The game leaves the desktop stuck on this awkward saturation bump (to get rid of it I have to restart x). Furthermore, launching the game again will bump the saturation more again and ad infinitum with every launch. This happens only with nGlide. nGlide also has some performance problems (the frame rate drops dramatically when thunder hits, but works perfect otherwise).

Direct 3d works very good and and looks ok in 1600x1200 4:3 resolution. The performance is far better than on nGlide.

That said, the bug when running the game with your wrapper is not caused by the fix nor my gpu. It's exclusive to your wrapper (maybe it's a Proton problem?).

This is the debug output when using the widescreen fix:

Running wine-3.0.3 Undying.exe (Working directory : /home/ /.PlayOnLinux/wineprefix/Undying/drive_c/GOG Games/Clive Barkers Undying/System)
0026:err:module:load_builtin_dll failed to load .so lib for builtin L"winebus.sys": libudev.so.0: nie można otworzyć pliku obiektu dzielonego: Nie ma takiego pliku ani katalogu
0026:err:winedevice:async_create_driver failed to create driver L"WineBus": c0000142
000f:fixme:service:scmdatabase_autostart_services Auto-start service L"WineBus" failed to start: 31
0009:fixme:process:GetProcessWorkingSetSizeEx (0xffffffff,0x33f6cc,0x33f6c4,(nil)): stub
0009:fixme:win:EnumDisplayDevicesW ((null),0,0x33f268,0x00000000), stub!
0009:fixme:win:EnumDisplayDevicesW ((null),0,0x336838,0x00000000), stub!
0009:fixme:d3d:debug_d3dformat Unrecognized 0x36314644 (as fourcc: DF16) WINED3DFORMAT!
0009:fixme:d3d:wined3d_get_format Can't find format unrecognized (0x36314644) in the format lookup table.
0009:fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24) WINED3DFORMAT!
0009:fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the format lookup table.
0009:err:ole:CoGetClassObject class {92fa2c24-253c-11d2-90fb-006008a1f441} not registered
0009:err:ole:CoGetClassObject no class object {92fa2c24-253c-11d2-90fb-006008a1f441} could be created for context 0x1
0009:err:ole:CoGetClassObject class {d8f1eee0-f634-11cf-8700-00a0245d918b} not registered
0009:err:ole:CoGetClassObject no class object {d8f1eee0-f634-11cf-8700-00a0245d918b} could be created for context 0x1

This is without the widescreen fix:

Running wine-3.0.3 Undying.exe (Working directory : /home/ /.PlayOnLinux/wineprefix/Undying/drive_c/GOG Games/Clive Barkers Undying/System)
0025:err:module:load_builtin_dll failed to load .so lib for builtin L"winebus.sys": libudev.so.0: nie można otworzyć pliku obiektu dzielonego: Nie ma takiego pliku ani katalogu
0025:err:winedevice:async_create_driver failed to create driver L"WineBus": c0000142
000f:fixme:service:scmdatabase_autostart_services Auto-start service L"WineBus" failed to start: 31
0009:fixme:process:GetProcessWorkingSetSizeEx (0xffffffff,0x33f6cc,0x33f6c4,(nil)): stub
0009:fixme:win:EnumDisplayDevicesW ((null),0,0x33f268,0x00000000), stub!
0009:fixme:win:EnumDisplayDevicesW ((null),0,0x336838,0x00000000), stub!
0009:fixme:d3d:debug_d3dformat Unrecognized 0x36314644 (as fourcc: DF16) WINED3DFORMAT!
0009:fixme:d3d:wined3d_get_format Can't find format unrecognized (0x36314644) in the format lookup table.
0009:fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24) WINED3DFORMAT!
0009:fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the format lookup table.
0009:err:ole:CoGetClassObject class {92fa2c24-253c-11d2-90fb-006008a1f441} not registered
0009:err:ole:CoGetClassObject no class object {92fa2c24-253c-11d2-90fb-006008a1f441} could be created for context 0x1
0009:err:ole:CoGetClassObject class {d8f1eee0-f634-11cf-8700-00a0245d918b} not registered
0009:err:ole:CoGetClassObject no class object {d8f1eee0-f634-11cf-8700-00a0245d918b} could be created for context 0x1
Post edited December 16, 2018 by valgaav
avatar
valgaav: I installed it on Play on Linux without any installation scripts (as an unlisted program) so there shouldn't be any dependencies installed. Just chose wine version.
That's not the kind of dependency I was referring to. PlayOnLinux bundles a number of Linux libraries with their Wine builds which I remove for my wrappers due to them causing problems with some distros - it's possible that your system may be missing some of those libraries, which would be a problem if the game depends on any of them.

There are only a limited number of possibilities that I can see causing this issue. The wrapper works completely fine on all of my systems, but not on yours... however the game does work with PlayOnLinux on your system. The only difference between running the game using my wrapper and with PlayOnLinux that I can see that might cause this kind of issue are the inclusion of the widescreen fix and the removal of the additional libraries included with the Wine package used by my wrapper (which is exactly the same as the one PlayOnLinux is using, sans those extra libraries).

We can rule out the widescreen fix being the cause (at least by itself) since that works on all of my systems here, and we can rule out the graphics driver on your system (at least by itself) as the game works with PlayOnLinux there but not my wrapper. However it's possible that the widescreen fix is exposing a bug in the drivers on your system - did you test the wrapper with the widescreen fix disabled?

As for the dependencies, you could try installing my common dependencies meta-package and seeing if that fixes it: https://www.dropbox.com/s/r7w90qyhp7n6197/common-libs-meta.deb?dl=0
avatar
valgaav: I also installed the widescreen "fix" and it... works. Although this fix is more of a gimmick (like most widescreen "fixes"). Large parts of the weapon and player model are hidden by the screen which changes the look and feel of the game. I would propose to not include this in the wrapper by default and just allow the installation in your start menu.
I don't think it makes that big of a difference, but I'll add a toggle for it in a future release (although it'll remain enabled by default).
avatar
valgaav: The two things that are wrong are a strange bug with screen saturation and performance under nGlide. The game leaves the desktop stuck on this awkward saturation bump (to get rid of it I have to restart x). Furthermore, launching the game again will bump the saturation more again and ad infinitum with every launch. This happens only with nGlide. nGlide also has some performance problems (the frame rate drops dramatically when thunder hits, but works perfect otherwise).
A lot of games do this (even with Direct3D) - restarting X is unnecessary; you can correct it by using xgamma. Unless you've altered your system's gamma settings (in which case use the value you've set it to - if R/G/B have different values use -rgamma / -ggamma / -bgamma with their respective values instead), this should fix it:

xgamma -gamma 1

My wrapper scripts work around this by reading the setting on startup and restoring it on exit.
avatar
valgaav: Direct 3d works very good and and looks ok in 1600x1200 4:3 resolution. The performance is far better than on nGlide.
I use nGlide for three reasons:
- It's how GOG set it up by default
- It allows me to configure it to prevent the system's display resolution from being changed
- (at least on my main system) In Direct3D mode the game speed is insanely fast and there are stability issues
avatar
valgaav: That said, the bug when running the game with your wrapper is not caused by the fix nor my gpu. It's exclusive to your wrapper (maybe it's a Proton problem?).
This wrapper uses the Wine 3.0 build provided by PlayOnLinux with the only difference being the removal of the additional libraries that they bundle with it, so it's most likely that the issue you're having is a dependency issue.

Actually, there is *one* other thing I can think of, but it's unlikely: my wrapper has CSMT enabled by default. This wasn't enabled by default with Wine until Wine 3.5 or so, so unless you enabled this yourself your POL install has been running without CSMT. It's easy enough to check this: run the start script, then do Advanced options... --> Advanced Wine options and set CSMT to disabled then apply changes.
Post edited December 16, 2018 by adamhm
I posted the second reply before you posted your first reply. I will install the common libs meta package and report back.
Installing dependencies does not change anything.

However removing the Widescreen patch does help. The game launched in 4:3 aspect ratio which was a little puzzling. The setting in nGlide is to preserve the native resolution. I think something might be wrong with the default setting. Shouldn't the widescreen patch achieve the needed effect when nGlide is set to widescreen?

If you will look at the logs, you will see the game reporting a very strange resolution of 4480x1682.

This doesn't happen at all on the POL installation.
avatar
valgaav: Installing dependencies does not change anything.

However removing the Widescreen patch does help. The game launched in 4:3 aspect ratio which was a little puzzling. The setting in nGlide is to preserve the native resolution. I think something might be wrong with the default setting. Shouldn't the widescreen patch achieve the needed effect when nGlide is set to widescreen?

If you will look at the logs, you will see the game reporting a very strange resolution of 4480x1682.

This doesn't happen at all on the POL installation.
That's the desktop resolution as reported by xrandr. If it's incorrect then there could be another issue somewhere... Anyway, the game starts at some low resolution by default but my wrapper script attempts to set the desktop resolution on first run... it might be failing due to that. Try this:

- Delete the wrapper and $HOME/.local/share/undying/System.ini
- Rebuild the wrapper and run the start script but don't start the game
- Edit $HOME/.local/share/undying/System.ini - find the lines starting with FullscreenViewportX= and FullscreenViewportY= and change them to manually set the display resolution.

Then try starting the game (it's probably a good idea to set a virtual desktop too).

Edit: I'm pretty confident that this is the issue. I was just able to recreate it on my system by manually setting some stupid resolution and trying to play. Since nGlide will prevent display resolution changes I'll probably leave it at the default resolution setting & just let users change it themselves. I'll try to get an updated wrapper out tonight or tomorrow.
Post edited December 16, 2018 by adamhm
Update is ready - try the new version (removing the original System.ini from $HOME/.local/share/undying if you haven't already) & let me know if that works :)

(also could you post the output of "xrandr -q" please?)
Post edited December 17, 2018 by adamhm
Ok. So I updated the wrapper and found out some really interesting things. You should definitely take a look at the following:

1) The mysterious resolution your wrapper detected in the previous version is the combined resolution of BOTH my screens including the placement offset. A fix for this would be detecting the resolution of the screen not the resolution of the entire Desktop. (see the first attached file).

2) When starting Undying after the update, I've set 2560x1440 resolution in the Video menu. The game worked for a couple of seconds and crashed with the same error as before. It didn't happen under 1920x1080.

3) After the above, I checked the behavior of the version installed on PlayOnLinux - perfectly stable in any given resolution if set only in nGlide. BUT when I've installed the widescreen fix and reproduced the exact starting state form your wrapper I was able to reproduce the same behavior. (when set to 1920x1080 - works ok. 2560x1440 - crashes).

Which means this is a problem with the widescreen fix which I believe does not work great in the first place.
I'm certain this will also happen in 4k and on any screen that exceeds 1920x1080.

Furthermore, I'm not sure if your wrapper should have tried to detect the screen resolution and try to set it in the in-game resolution settings AT ALL.

(VERY IMPORTANT) Whatever resolution you will set in the video menu will be set only for the menu. nGlide will override this setting either way. The only things that are affected in-game is the size of the fonts and the size of the crosshair, but the 3D graphics is always as set in the nGlide settings (see the second attached file). The performance drop during thunder is also ONLY present when setting some resolutions in the video menu.

CONCLUSION:

I think, the optimal default setting that should work on all 16:9 widescreen monitors (when widescreen fix applied) is 1280x720 in the Video menu, and "By desktop" + "Preserve original" (aspect ratio) in nGlide. If you set anything above that in the Video menu the crosshair and font is absurdly small eitherway. "Preserve original" will allow the user to set a 4:3 aspect ratio on fullscreen widescreen if that would be preferred.

For 16:10 it would be 1280x800. For 4:3 monitors, the resolution should be 1280x1024, and to avoid interface issues the widescreen fix might be removed completely.

I suggest menu entries: "Set for 16:9 widescreen (default)", "Set for 16:10 widescreen" and "Set for 4:3", that apply the above presets. This should eliminate all issues with high DPI screens and other issues related to the widescreen fix.

Some problems may still happen on 21:9 screens (2560x1080), though (I'm not sure if the widescreen fix allows 21:9 aspect ratio resolutions, as there is no such resolution available in the menu - tested this in 2560x1080 virtual desktop, and could not set to anything like 1280x540 in the Video settings). Found this, athough seemingly for Direct3D http://www.wsgf.org/forums/viewtopic.php?p=170350#p170350

I hope the above helps you deal with the problem:)

xrandr -q output:
Screen 0: minimum 320 x 200, current 4480 x 1682, maximum 16384 x 16384
HDMI-A-0 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 527mm x 296mm
2560x1440 59.95*+
1920x1200 59.95
1920x1080 60.00 50.00 59.94
1600x1200 59.95
1680x1050 59.88
1600x900 60.00
1280x1024 75.02 60.02
1440x900 59.95
1280x800 59.91
1152x864 75.00
1280x720 60.00 50.00 59.94
1024x768 75.03 60.00
832x624 74.55
800x600 75.00 60.32
720x576 50.00
720x480 60.00 59.94
640x480 75.00 60.00 59.94
720x400 70.08
DVI-D-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-1 connected 1920x1080+2560+602 (normal left inverted right x axis y axis) 477mm x 268mm
1920x1080 60.00*+
1680x1050 59.95
1280x1024 75.02 60.02
1440x900 60.00
1280x800 60.00
1152x864 75.00
1280x720 60.00
1024x768 75.03 60.00
800x600 75.00 60.32
640x480 75.00 59.94
720x400 70.08
Attachments:
Post edited December 17, 2018 by valgaav