Rocket League (252950)

[Oliver-1xok]

Compatibility Report

• Name of the game with compatibility issues: Rocket League
• Steam AppID of the game: 252950

System Information

• GPU: GTX 970
• Driver/LLVM version: nvidia 440.59
• Kernel version: 5.3.0-28-generic #30~18.04.1-Ubuntu SMP Fri Jan 17 06:14:09 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
• Link to full system information report as Gist: https://gist.github.com/Oliver-1xok/1faf131563237060edc339a413646150
• Proton version: 5.0-1

LOGS

Here are the Proton logs from my system: steam-252950.log

Here is an output of the PS command for the corresponding processes which are created in the system: ps.log

Symptoms

When I start the experimental DX11 client from Rocket League the game does not work.

You can start this client with the launch option "-dx11". A window appears with the title: "Rocket League (64-bit, DX11, Cooked)".

The window does not disappear and is not updated after a while. No window with the game appears. The 32-bit DX9 client of the game runs on my system without major problems and the game starts after a short time. The experimental DX11 client no longer does this.

Reproduction

1. Follow these steps: https://steamcommunity.com/app/252950/discussions/0/1738889518180525789/
2. For additional Proton Log use the following launch options: "PROTON_LOG=1 %command% -dx11"
3. Click on Start

[kisak-valve]

Hello @Oliver-1xok, just to check, was PROTON_LOG=1 %command% -dx11 what you tried to use in the game's launch options to generate a log? Environment variables have to come before the command that's being run.

[Oliver-1xok]

Hello @Oliver-1xok, just to check, was PROTON_LOG=1 %command% -dx11 what you tried to use in the game's launch options to generate a log?

Of course not. :/

Thank you for the hint! Sorry, my mistake. The proton logs are generated without problems. I added them to the report and also recreated the output of the PS command.

(I also updated Steam Info again, because my Steam Client has been updated in the meantime.)

[doitsujin]

D3D11 GPU hangs should be fixed as of https://github.com/doitsujin/dxvk/commit/4aa6800e95b093f259123107190ca56dae24e3be.

Do note that the renderer seems to be quite buggy so there might be further issues.

[WernerAUT]

can confirm with https://github.com/doitsujin/dxvk/commit/4aa6800e95b093f259123107190ca56dae24e3be Rocket League runs without issues under D3D11, i played some rounds without any issues.

[Oliver-1xok]

can confirm with doitsujin/dxvk@4aa6800 Rocket League runs without issues under D3D11, i played some rounds without any issues.

Just for clarity: You tested it with a self-compiled version of DXVK that contains https://github.com/doitsujin/dxvk/commit/4aa6800e95b093f259123107190ca56dae24e3be ? And you also tested it with an Nvidia card?

(I haven't had time to test it yet.)

[WernerAUT]

correct, but i didn't compile it myself :) Philip has his buildbot :) https://git.froggi.es/doitsujin/dxvk/pipelines?scope=finished&page=1 I overwrote the 32bit and 64bit dll's in proton 5.0-2 (released some minutes ago) inside steam. Yes i use Nvidia it is a GTX 1070. Played again around 30 minutes without issues

[Oliver-1xok]

correct, but i didn't compile it myself :) Philip has his buildbot :)

Ah, it's easier, of course. Thanks for the advice!

[Oliver-1xok]

can confirm with doitsujin/dxvk@4aa6800 Rocket League runs without issues under D3D11, i played some rounds without any issues.

Can also confirm. I tested again with proton 5.0-2. With the release version of DXVK the game did not start. Then I used this build:

https://git.froggi.es/doitsujin/dxvk/pipelines/1068

I copied the libraries from "build/dxvk-release/x64" to "steamapps/common/Proton 5.0/dist/lib64/wine/dxvk".

Rocket League runs normally afterwards. It doesn't run as smooth as the D9 version due to the missing VSync in this experimental version. But this is another problem.

So I think Philip has fixed this problem.

[doitsujin]

Rocket League runs normally afterwards. It doesn't run as smooth as the D9 version due to the missing VSync in this experimental version

You can force vsync via dxvk.conf options, specifically dxgi.syncInterval = 1.

[WernerAUT]

hm in proton were should this dxvk.conf file go? i created one in my steam folder, and in Steam at the run options i added DXVK_CONFIG_FILE=/home/mine/Games/Steam/dxvk.config but it seems to get ignored

[doitsujin]

The environment variable should work fine, best double-check whether both the path and content of the file are correct.

[CSahajdacny]

What is the default location for the dxvk.conf file?

[Oliver-1xok]

What is the default location for the dxvk.conf file?

There is no default. Set the following launch option

DXVK_CONFIG_FILE=/your/dir/here/dxvk.conf %command%

Of course you have to replace /your/dir/here/ with the directory where your dxvk.conf is located.

You can download a commented dxvk.conf to your current directory with this command: wget https://raw.githubusercontent.com/doitsujin/dxvk/master/dxvk.conf

You then simply adapt this conf to your needs. It works fine. Just tested it.

[Oliver-1xok]

You can force vsync via dxvk.conf options, specifically dxgi.syncInterval = 1.

I did not know the VSync option yet. Great option. The game becomes very smooth again. Works better than the VSync implementation by the Nvidia driver, which almost always results in micro stutterers.

The only thing I notice with dxgi.syncInterval = 1 are regular yellow spikes for single frames in the frame time graph during gameplay. The max frame time doubles from 17 ms to most 34 ms. However, I do not notice any disturbing stuttering. I don't really notice anything. I just see it in the graph.

Without VSync my GTX 970 reaches 120 to 180 fps in the DX11 client of Rocket League. 120 fps constant in any case. (With all graphic settings at maximum.)

This just for feedback.

[Anupalabdhi]

Though the DX9 version seems to start up and work. Rocket League DX11 version has stopped working again. The logs are identical to the ones posted originally in the issue (at least to my untrained eye).

steam-252950.log

The log is generated with latest mesa-aco from Valveaur repo, but even with regular mesa 20.x the dx11 version of the game was not working

[chevalmuscle]

Works for me with the -dx11 flag

GPU: GTX 1050 Ti Driver/LLVM version: nvidia 435.21 Kernel version: 5.3.0-42 Proton version: 5.0-5

Don't forget to force the use of steam play because Psyonix is no longer supporting the game on linux

[Anupalabdhi]

After further testing, It seems that the Rocket League DX11 version does indeed start, but it does so after stalling at the startup logo for a good while (full 2 minutes as per my stopwatch). In the meanwhile the menu music is playing in the background even though the game is still showing the Psyonix start up logo. After two minutes when it finally reaches the menu, the "Press any button" starts blinking rapidly as if catching up to the amount of blinks it missed due to the delay. After a while it too settles down into the normal rhythm.

Something strange is going on, I must admit.

For completion's sake, I am attaching another log, after entering the game and closing it.

steam-252950.log

EDIT: For some reason (probably an update at my end), the game is now starting up properly.

[JoranDox]

AMD user here, I'm getting stutters after a few games, growing worse and worse. Restarting rocket league doesn't seem to have any effect, but restarting my pc does. This to me feels like some form of memory leak or something like that? Haven't tested if e.g. restarting steam works too, I'll try working out what the exact "refresh" trigger is in the following days (takes a few games (or X time?) for the stutters to get noticably bad).

I haven't experienced this issue with Monster Hunter World, the only other game I've really played on my new machine, so I'm guessing it has something to do with rocket league, but not very sure.

I'm not running anything else apart from discord as this is a fresh install of ubuntu 20.04 Proton: tried with both 5.0-6 and 5.6-GE-2 CPU: AMD Ryzen 7 3700X GPU: AMD Radeon RX 5700

other system details here: https://gist.github.com/JoranDox/ccc321a93a5f7105f698a9eaccd29e59 protonlog: steam-252950.log

[bgrnwd]

Seeing a similar issue here as well.

CPU: AMD Ryzen 5 3600X GPU: NVIDIA GeForce RTX 2070 Super Proton Version: 5.0.9 Kernel: 5.6.19-2-MANJARO Drivers: nvidia 440.100

I'm able to get Rocket League to launch to a black screen and then it quits.

Here's my `user_settings.py` and I am running Rocket League with `-dx11` as a launch option

#To enable these settings, name this file "user_settings.py".

#Settings here will take effect for all games run in this Proton version.

user_settings = {
    #Logs are saved to $HOME/steam-<STEAM_GAME_ID>.log, overwriting any previous log with that name.

    #Wine debug logging
    "WINEDEBUG": "+timestamp,+pid,+tid,+seh,+debugstr,+loaddll,+mscoree",

    #DXVK debug logging
    "DXVK_LOG_LEVEL": "info",

    #vkd3d debug logging
    "VKD3D_DEBUG": "warn",

    #wine-mono debug logging (Wine's .NET replacement)
    "WINE_MONO_TRACE": "E:System.NotImplementedException",
    #"MONO_LOG_LEVEL": "info",
    "PROTON_LOG": "1",
    #Enable DXVK's HUD
#    "DXVK_HUD": "devinfo,fps",

    #Use OpenGL-based wined3d for d3d11, d3d10, and d3d9 instead of Vulkan-based DXVK
    "PROTON_USE_WINED3D": "1",

    #Disable d3d11 entirely
#    "PROTON_NO_D3D11": "1",

    #Disable eventfd-based in-process synchronization primitives
#    "PROTON_NO_ESYNC": "1",

    #Disable futex-based in-process synchronization primitives
#    "PROTON_NO_FSYNC": "1",
}

The only error I see in my steam-252950.log is this:

245.965:00c8:00cc:err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution

Edit

Was able to get rid of the ntlm_auth issue but still the same result where I get to a black screen and then the game crashes

[kisak-valve]

Rocket League not launching

Issue transferred from https://github.com/ValveSoftware/Proton/issues/4257. @Owez posted on 2020-10-12T16:48:25:

Compatibility Report

• Name of the game with compatibility issues: Rocket League
• Steam AppID of the game: 252950

System Information

• GPU: RX580
• Driver/LLVM version: Mesa 20.0.8 (LLVM 10.0.0) (taken from vulkaninfo)
• Kernel version: 5.4.0-48-generic
• Link to full system information report as Gist: Info
• Proton version: Proton 5.0-9

I confirm:

• [x] that I haven't found an existing compatibility report for this game.
• [x] that I have checked whether there are updates for my system available.

steam-252950.log

Symptoms

I have tried to launch the game but it doesn't show anything and fails after ~5 seconds of a "cancel x" or "stop x" button. I have tried reinstalling steam and wiping all .steam/ along with reinstalling the game from my ext-4 partitioned external drive to root ssd (even though that shouldn't be a problem). Can't seem to get it to work apart, using the PROTON_USE_WINED3D=1 or leaving it out of the launch options.

Reproduction

Not sure how to reproduce, I can only find some errors regarding cryptic memory addresses and pid swaps once it crashes (which I assume is steam handling pid control, not the game). This started a week ago and it may be an issue with updated graphics drivers but a lot has been changed apart from a upgrade updating drivers near the time for my RX580. Running on linux mint 20, all stock with only steam and programming tools installed (e.g. vscode which shouldn't affect in any way).

[kisak-valve]

Hello @Owez, something's abnormal about your video drivers and : CommandLine Error: Option 'help-list' registered more than once! LLVM ERROR: inconsistency in registered CommandLine options in the log supports that impression. In particular, the extended diagnostic information says that you have mesa 20.1.5 / llvm 10.0.1 when testing OpenGL, and mesa 20.0.8 / llvm 10.0.0 for Vulkan. This version mismatch is unusual and I wouldn't be surprised if it's the root of the issue you're seeing.

[Owez]

Appreciate the response @kisak-valve , will try to fix the mismatch: does seem like that's the issue in retrospect.

[oblitum]

This game used to play pretty well until Proton 5.13. Now when trying to start it'll consume all available memory pretty fast (16GB) leading to OOM. Seems like a leak.

Sorry, my bad, false alarm. The game is running fine. After upgrading Proton to 5.13 I forgot to force this game to launch with Proton, so it was launching with its native linux version, it's this version that doesn't work, it's running fine on Proton 5.13.

[oblitum]

After latest recent game update, steam update, and proton update (so I ignore which update is the cause), the game or steam client is crashing when starting, both game and steam closes. This is the log.

[Zuchter]

I'm having this error when trying to launch the game

[kisak-valve]

Hello @Zuchter, Binaries/Linux/RocketLeague was the name of the native linux binary. If you want to test the game with Proton, go to the per-game properties and enable Proton in the Steam Play section.

[Zuchter]

Hello @Zuchter, Binaries/Linux/RocketLeague was the name of the native linux binary. If you want to test the game with Proton, go to the per-game properties and enable Proton in the Steam Play section.

I will try what you said but I found something else, I went into the game files and there was nothing there. The Rocket League folder was literally 8KiB. Seems like steam doesn't even download the game

edit: Nevermind, after trying what you said it started downloading the full game now. Thank you

[nurgasemetey]

as @kisak-valve said, click settings icon of game, then properties

Then, check option For the use ... and select Proton

[kescherCode]

I am using a dual-monitor setup. When launching Rocket League, when set to borderless or fullscreen, it will now choose my secondary monitor instead of my main one. Before Proton 5.13, it shows on my main monitor (which is a high-refresh rate monitor) correctly. I assume this has something to do with it now being in an isolated container...

[kescherCode]

I would like to note that this does NOT happen with all games! For instance, the game Ascent fullscreens on my main monitor correctly, regardless of Proton version.