@NRG-R9T
Hi, sorry for the off-topic, but would you please share some information on your overlay in the top left corner? Thanks a lot!

@H34dl3ss It's mangohud 🙂 Hope that is enough info hehe.

Additionally to the absolutely annoying problem with unpredictable Game crashes, that still exists, there is also a Steam Cloud Error happening since about a week. This is the Steam Log-File to download: https://mega.nz/file/ZEAAyTgI#b4LltDAb25VV9xnej8lQGg19dtt0EJGmGJUUpTzpTv8 (56MB is apparently too big for Github or Gist)

Another Problem: EA Origin does not recognise, that I bought the game and starts more often than not with a browser window to EA Origin's Platform and a prompt "Trial Version ended" and shows "Buy Game", which I click (having bought it already), then Origin recognises, that it was at fault and shows a "start game" button. All this happens inside the Launcher Window, which normaly just shows the 3 buttons to play, settings and exit.

I've played the Game for over 300 hours by now, and while it can be played well, it is impossible for me to play it seriously competitive, as the game crashes the competitive matches in about 1 in 3 cases. So in FUT Champions I've often got 19 of 20 points needed to qualify for Play-offs (Weekend League), with about 3-4 games effectively played out of 8 possible ones. The rest crashed me out before it started.

I have faced the same issue.

Huge ea servers problems was present today. Officialy it's fixed now according to official Twitter ea direct communication account.

The connection problems where temporary for all players and solved. The original issue of FIFA22 (running with Proton) with FUT Games that are crashing at random (in the match loading screen) is still present.

I seem to have an issue whenever I start the game I get a black screen, and I've tried multiple things but I still can't seem to get it to work. No custom launch options, and using latest Proton, my system specifications should be listed in the given text file.

Whenever I click Play on the Game Screen I get a Black Screen Window before it crashes later.

Black Screen:

This is what I got when I ran Steam in the terminal:

steam.log

Hello @kisak-valve, are there any plans by Valve to stop allowing third party launchers like this one in the future, which break perfectly playable offline games that require a older Proton version?

The only thing that invasive third party launchers like this achieve, is that people will start pirating those games when they get screwed by shady companies that break their games on purpose. These self-updating always online launchers make game preservation basically impossible without pirating.

@puxplaying Have you checked the "game settings" in the launcher to see if you have it set to be capped to 30fps or 60fps? Due to the specific situation you described, I wonder if somehow it is set to 30fps for you right now?

Also - how have you been checking the FPS? It looks like the steam overlay fps counter doesn't work for this one :( And what part of the game are you playing? I keep getting warnings that the servers have been turned off, so I'm not able to test any cutscenes etc.

Hello @alasky17!

Have you checked the "game settings" in the launcher to see if you have it set to be capped to 30fps or 60fps? Due to the specific situation you described, I wonder if somehow it is set to 30fps for you right now?

I made sure to set it to 60fps in the settings app and also confirmed it by checking the fifasetup.ini in /compatdata/1506830/pfx/drive_c/users/steamuser/My Documents/FIFA 22 - WAITFORVSYNC = 1

Also - how have you been checking the FPS? It looks like the steam overlay fps counter doesn't work for this one :( And what part of the game are you playing? I keep getting warnings that the servers have been turned off, so I'm not able to test any cutscenes etc.

The best way to check this without any FPS counter is in the career mode on a 60Hz monitor. Simply start a match with your player and make sure the Pro Cam is used. It will immediately start stuttering with this cam and set the frame rate to half of the screen refresh rate, while the traditional cams work fine on 60 fps. (This issue is also affecting Windows with AMD GPU's, maybe because it's a console port)

Here a reddit post about it: https://www.reddit.com/r/FIFA22/comments/pw0ep7/fifa_22_30fps_lock_also_pro_camera_issue_solved/?rdt=45957

My guess is, that proton 7 is either spoofing the actual refresh rate, or somehow forcing 60fps, while newer versions don't do that. Which makes Proton 7 the only option in my case. I've tested that also on a RX580 with the same result. So it seems to be a AMD GPU issue, I don't think that Nvidia GPU's are affected.

I could work around this issue with newer Proton versions by using a 120Hz monitor, which then will be internally set to 60fps in Pro Cam - career mode.

@puxplaying Ah I see - so it looks like the FPS getting set to 1/2 of the refresh rate is a game bug? I'm assuming the refresh rate of your monitor is 60fps and Proton versions newer than 7.0 are reporting that correctly? (just making sure I'm understanding this correctly).

If the issue is with AMD GPUs, you could try using WINE_HIDE_AMD_GPU=1 or PROTON_FORCE_NVAPI=1. You could also potentially try adding a file called "dxvk.conf" in the game directory with the following content:
dxgi.customDeviceId = 10DE
dxgi.customVendorId = 1C02

I'm not 100% confident in these options to hide your AMD GPU, maybe someone else has better advice in that regard :)

@alasky17

Ah I see - so it looks like the FPS getting set to 1/2 of the refresh rate is a game bug? I'm assuming the refresh rate of your monitor is 60fps and Proton versions newer than 7.0 are reporting that correctly? (just making sure I'm understanding this correctly).

Absolutely right!

If the issue is with AMD GPUs, you could try using WINE_HIDE_AMD_GPU=1 or PROTON_FORCE_NVAPI=1. You could also potentially try adding a file called "dxvk.conf" in the game directory with the following content:
dxgi.customDeviceId = 10DE
dxgi.customVendorId = 1C02

The "dxvk.conf" file with the content you posted seems to solve it completely. The launch options when tried one by one, don't seem to have any effect without the "dxvk.conf".

You my friend just solved years of mystery (for me) in a single post. Thank you very much for that!