michal_229
Published
enabled wine virtual desktop
Flickering shadows, but rarely.
Problem with moving virtual desktop to another monitor:
* when moving wine virtual desktop from 16:9 monitor to 21:9 monitor, mouse cursor movement is restricted to area on the right part of the screen - can't click anything in menu,
* can't choose any option or close dialog by click/enter on 21:9 monitor in dual monitor setup.
Virtual desktop refresh rate before game launch is 200Hz (correct for my monitor), but when game launches it is reduced and feel laggy, possibly FreeSync issue.
Problem with game input when racing wheel is connected (Logitech G29):
* up/down cursor movement is controlled by clutch pedal
* left/right cursor movement is controlled by turning wheel
* game is switching constantly between keyboard/mouse and wheel
* unplugging the wheel helps
Stuttering when rotating camera while adaptive grahics quality and adaptive AA options were enabled. Performance could be a bit better overall, but it is playable after reducing graphical details.
Game crashes when using steam shortcut shift+tab while rendering in wine virtual desktop. Apart from that I didn't experience any other crashes.
Uplay hangs:
* uplay was hanging on checking patches
* it started working after a few restarts and allowed me to register and launch the game
Link to videos showing some mentioned bugs: https://drive.google.com/drive/folders/1eYFLz5OXL0ndy3YpeAdTK7grKV_Z5pWo?usp=sharing
/path/to/proton/GE-Proton7-42/proton waitforexitandrun /path/to/steamapps/common/assettocorsa/'Content Manager Safe.exe'; echo %command%
I installed some dependencies as in instructions found in earlier reports, not sure which ones helped to run it. Works fine on GE-Proton7-42.
Logitech G29 + FFB works nice, ~250fps on 6900XT (full detail, 8xMSAA. 4096 shadows, etc.), 2560x1080@200Hz screen.
It works fine, apart from freezes every few hours. It works better for me when Vulkan is chosen in the launcher.
gamescope -w 3840 -h 2160 -- %command%
My PC freezed a few times (needed hard reset) - similiar things happened before with Divinity: Original Sin 2.
No force feedback by default on Logitech G29. Fix is to use ffbwrap in custom launch options:
Performance is not the best initially. It gets a bit worse (stuttering appears) over time.
PROTON_NO_D3D10=1 gamescope -w 1920 -h 1080 %command% -refresh 120 -nomovies -window -fullwindow -forceactive
It may work without gamescope as well, but I generally prefer enabling it. Parameters after %command% were required, otherwise there was only black screen on gamescope or no window at all without it - https://steamcommunity.com/app/231430/discussions/3/3090011896384600038/
Main character can't stop walking, so it is impossible to proceed (tested on demo version)
Proton-5.8-GE-2-MF GloriousEggroll
Proton-5.8-GE-2-MF
Floor was flooding with solid black and red (some walls too), possibly something with screen space reflections and effects around items with which player can interact. It was quite entertaining to watch :P Also on 21:9 monitor and 2560x1080 resolution in settings, the game would render in 1920x1080 part of the screen at center - black rectangles on both sides of the screen. If the graphics artifacts would be the only problem, the game would be playable.
Walking down (S key/down arrow/down direction on left controller stick) + right direction on right stick (when using controller) were constantly active. Even when I disconnected/turned off every input device, main character would go into the camera and camera would rotate around (rotation was present only when controller was used). Proceeding was impossible, since I couldn't make any action while walking.
Tested on demo version.
Custom launch options (using ffbwrap to enable force feedback on Logitech G29):
/opt/michal/ffbtools/bin/ffbwrap --update-fix /dev/input/by-id/usb-Logitech_G29_Driving_Force_Racing_Wheel-event-joystick -- %command%
Lack of FFB on Lgitech G29, but fixed with ffbwrap.
There was a problem in default proton (5.0-9) regarding connecting to game servers. Anything else works on default proton. Proton-5.11-GE-1-MF fixes server connection issue.
After changing proton to older version and playing coop for titles other than Halo CE, it worked pretty nice. Halo CE is unplayable.
Had to change output device for H3 to pulseaudio to hear anything, worked fine without tweaks for other Halo games.
H1 has artifacts problems on older proton, but proton 5.0-10 is needed for coop to work. Halo games other than 1 looked properly.
H1 has freezing problems (old and new graphics, no difference). Halo games other than 1 worked flawlessly.
Had to change proton to 5.0-10 for online coop to work (proton prefixes had to be reset and initialized again after change!). I didn't check multiplayer modes other than coop.
Without tinkering the game works in singleplayer, but coop disconnects. Halo CE (H1) is still unplayable.
Some artifacts on planets/moons when viewed from space.
Worked pretty fine, nothing to complain about.
I couldn't make it run neither with default proton nor Experimental/GE. On PC with Ubuntu a launcher appears, which then enables you launching the game. On Steam Deck it did not show at all, checked in regular mode and in desktop mode.
