ATFx
Published
Ps4 controller will not be Detected by Default. Steam-Settings-Controller-Enable Playstation Configuration support. Game Properties-Controller-have it any of the 3 options won't matter with.
Won't detect only without General PsConfig support.
Will play Treyarch Intro then sit on a Black Screen,
ProtonGE 7.6-7.15
I've also left this sitting overnight to make sure was an issue.
For Raven Integrated Vega Graphics this is the Result
and my laptop also has a Descrete Rx560 (GFX8) gpu I force to use with launch command
DRI_PRIME=1 %command%
That results the same with the Rx560. Tested with ProtonGE 7.5-7.15, Proton 7.0-2, and Proton Experimental
With Fresh Compat Data's and Mesa Stable 22.0.1
Single Player, Multiplayer work flawless after shading compiling. Biggest issue is creating a private match in multiplayer will either crash the game or If lucky return an error message, "Invalid structure definition, stats group of type 3 named Z491056b8ad1e0039ae1af4b3163ff872d147bb90852667c95affe3c7 has empty data."
Game Crashes, no matter the tweaks on Proton 4.2-6 "for Singleplayer" Multiplayer works no problems no tweaks.
After I disable AMD SMT(Intel Hyper threading equivalent) on my Threadripper through My Bios I can launch and play the game flawlessly after signing into to Uplay, quiting then relaunching with no special flags/parameters through Steam etc. If I don't do this, the game will panic and crash instantly when it launches, Nonplayable/Borked.
Game runs pretty flawless after tweaking In game graphics settings. Just 2 Issues: Game doesn't fully quit on quiting. Cannot minimize or force quit once in game. Aggressive Fullscreen
Cannot Minimize once in Game (will black screen/break the game) if you try. Game does not fully quit when quiting, has aggressive fullscreen with no Native windowed mode options in Game. Other then this it runs out of the box (no special launch commands) very well.
Runs Perfectly out of the box No Tweaks. Fully quits now on this PV, Only issue is Crashes/Blackscreens when alt tabing out of the aggressive full screen.
Must set os compatibility to windows 7 for multiplayer to work.
For Multiplayer Functionality, New Features/Maps with Windows Version. Runs Beautifully.
Has Never Worked for me on Any Proton, Driver, or Kernel Version Variation
I tried this SIMPLE FIX: Create a dxvk.conf file in /home/USERNAME/.steam/steam/steamapps/common/STAR WARS Battlefront/ and write this into the file: dxgi.customDeviceId = 1C81 dxgi.customVendorId = 10DE still complained about the Driver Version. Mesa Stable makes no Difference in ability to Install. I use DRI_PRIME=1 %command% to use my Rx560 over my 3550h cpu graphics.
On startup when using AMD GPU: Error: Detected AMD Radeon driver version UNKNOWN Fix: Created a dxvk.conf file in /home/USERNAME/.steam/steam/steamapps/common/STAR WARS Battlefront/created a dxvk.conf file added: dxgi.customDeviceId = 1C81 dxgi.customVendorId = 10DE dxgi.customDeviceId = 10de dxgi.customVendorId = 1c06
any one of these lines may specifically Enable this Game to work for you. Hopefully it does, dxgi.customVendorId = 1c06 is what Enabled it for me. I use DRI_PRIME=1 to use Rx560 over Integrated Radeon Graphics.
Ps4 Controller did not Work with No matter Steam Input Disabled or Enabled or using an Xbox Controller Configuration
Yes a Typical Gamer would have an enjoyable experience If they could figure how to get it working the best like.
Must Disable Steam Input under the Game settings specifically and only have xbox controller configuration enabled under general settings. For Ps4 controller to work with Game.
Must use Latest Vanilla Proton 5.13-5. Does not work with any Proton GE I've tested 5.21+, even for Installing. I must use DRI_PRIME=1 %command% for game to use my gpu in this laptop over integrated. Major performance boost for this Game on 21.1 devel for my gpu. Platinum rating if on that. If on Mesa 20.3.4 I'd rate bronze. If not: worse.
Using a Ps4 Controller must specifically have general controller setting xbox configuration support(ONLY) and specifically under SWB2 properties>controller Disable Steam Input
Yes its very weird and shouldn't work but does for me. Having any other controller configs enabled or disabled with doesn't work.
No longer need specific controller configs it works correctly without.
Also Works Perfect with current Proton Experimental & 5.13-6 installing to playing with no tweaks.
Mistook conflicted compat data cache with another proton version for proper functionality on a fresh install.
Must | Disable Steam Input under SWB2 properties-controller |specifically and | only have xbox controller configuration enabled under general controller settings |. For Ps4 controller to work with Game.
