Skip to content

Instantly share code, notes, and snippets.

@Decclo
Last active May 31, 2024 14:33
Show Gist options
  • Save Decclo/da097b504ccbc61514926ae2d96350ef to your computer and use it in GitHub Desktop.
Save Decclo/da097b504ccbc61514926ae2d96350ef to your computer and use it in GitHub Desktop.
Burnout Paradise Remastered - Guide for ProtonDB

Burnout Paradise Remastered - Guide for ProtonDB

Feel free to add your own experiences in the comments!

Origin is being Origin, but that doesn't stop us! We'll need to do a few things to get Burnout Paradise working. This mostly boils down to Running the game using GE-Proton, disabling Origin ingame overlay, setting the -skipvideos argument, and using a savegame which skips the intro video.

0. Assumptions

  • This guide was written on EndeavourOS, but later tested to also work on Linux Mint.

  • The game is owned on and installed through Steam, It was not tested with a non-steam installation of Origin, but I assume it would work with some minor tweaks, such as changing the APP ID when selecting the compatdata environment.

  • Steams choice of Origin launcher was used.

  • We assume a clean work environment. If you made any modifications to the game directory or have any old Burnout Paradise compatdata directories, then please remove them. Please do make sure not to delete the wrong directories.

1. Downloading GE-Proton and BP Remastered

  1. Download the newest GE-Proton, possibly by using ProtonUp-QT. Don't forget to restart Steam.

  2. In steam: Download Burnout Paradise Remastered, right-click and go to "Properties->COMPATABILITY" and choose to force GE-Proton.

  3. In steam: Start the game once, it will most likely get stuck in a black screen, wait some seconds and then force close it.

2. Fixing overlay

  1. In Steam: Go to "Games->Add a non-steam game...", choose all files instead of only .desktop, and navigate to /home/$USER/.local/share/Steam/steamapps/compatdata/1238080/pfx/drive_c/Program Files (x86)/Origin/Origin.exe. Using $USER should work, but if in doubt then write in your own username.

  2. In Steam: Right-click the new Origin "game" and go to "Properties->SHORTCUT->LAUNCH OPTIONS" where you must paste STEAM_COMPAT_DATA_PATH="/home/$USER/.local/share/Steam/steamapps/compatdata/1238080" %command%.

  3. In Steam: Right-click the new Origin "game" and go to "Properties->COMPATABILITY" and force Proton Experimental.

  4. In Steam: Launch the new Origin "game", and login to your EA account.

  5. In Origin: Go to "Origin->Application Settings->ORIGIN IN-GAME" and disable "Enable Origin In-Game".

  6. In Origin: You can now close Origin by going to "Origin->Exit".

3. Setting -skipvideos launch argument

There are two ways to add -skipvideos, either inside or outside of Origin. Either one might work.

Inside Origin:

  1. In Steam: Launch the new Origin "game", and login to your EA account.

  2. In Origin: Go to "My Game Library->Burnout Paradise Remastered" and click on the "cogwheel->Game Properties->ADVANCED LAUNCH OPTIONS" and add -skipvideos to the command line arguments. Don't forget to click "save".

  3. In Origin: You can now close Origin by going to "Origin->Exit".

Outside of Origin:

Thank you for the discovery, Jademalo.

  1. Open the file /home/$USER/.local/share/Steam/steamapps/compatdata/1238080/pfx/drive_c/users/steamuser/AppData/Roaming/Origin/local_xxxxxx.xml, where xxxxxx is a semi-random string of numbers.

  2. Add the following string on line 14, righ above HotKeyString:

  <Setting key="GameCommandLineArguments" type="10" value="#//Origin.OFR.50.0002541_-skipvideos"/>
  1. Save and exit the file.

4. Skipping intro video

This will only have to be done once, as Steam will sync your savegames with future installations.

  1. Download the savegame. I'll try to add it to the gist, but alternatively download from >noderunner_'s GDrive (shamelessly stolen from >noderunner_).

  2. Paste the savegame into /home/$USER/.local/share/Steam/steamapps/compatdata/1238080/pfx/drive_c/users/steamuser/Local Settings/Application Data/Criterion Games/Burnout Paradise Remastered/Save/.

5. Running the Burnout Paradise Remastered

We should be good to go now, so try firing it up the game in Steam. Hopefully it'll just work.

@lucashmsilva
Copy link

so, I have done everything and still it crashes. it gets to the initial loading screen and then about 30 seconds or so into loading it crashes. I am on LM21.

@FoxbitDreamtail did you managed to fix it? I'm having the same problem on the Steam Deck.

Fortunately the problem was fixed, but unfortunately, I don't know what I did that solved it. The only thing I can think of was a full system reboot. Right after I finished following the steps from the tutorial, the game force closed in first the loading screen. Some days after I opened the game again to show a friend the problem and it just worked.

@FoxbitDreamtail
Copy link

Fortunately the problem was fixed, but unfortunately, I don't know what I did that solved it. The only thing I can think of was a full system reboot. Right after I finished following the steps from the tutorial, the game force closed in first the loading screen. Some days after I opened the game again to show a friend the problem and it just worked.

As for me, I reached a tiny bit of progress, the game now launches and doesn't crash but it hangs on a black screen after the initial loading.

@Synthesthesia
Copy link

Synthesthesia commented Oct 30, 2022

I just get a blue rectangle when I try to launch, and no origin folder is in my program files (x86) folder. Any ideas what I can do? Thanks.
44785B9E-6279-4362-BBCE-A510E509DCD6

Fixed it myself by manually downloading origin, installing it and moving it to the correct folder. Hopefully that helps anyone else trying to do it.

@parkerlreed
Copy link

EA has a new launcher. This is the result... :(

@FoxbitDreamtail
Copy link

Unless steam comes up with some way of either bypassing the launcher or another means of getting the game working, it's hopeless.

@gbdrbob
Copy link

gbdrbob commented Nov 1, 2022

The new EA Launcher can work. I only own Burnout Paradise Remastered via EA (i.e it's not in my Steam Library) and have it working.

I needed to install some dependencies into the proton prefix to get up and running. Take a look at this guide and try using protontricks to install the dependencies it reccomends.

@parkerlreed
Copy link

Seemingly this comes up if Steam isnt linked to EA account on the web (Thats what the windiow is trying to ask)

Linking it on the EA account online should get you past this

@Decclo
Copy link
Author

Decclo commented Nov 1, 2022

That's good to know. I'll update the instructions as soon as I get time to try it out.

@tembrewn
Copy link

tembrewn commented Nov 7, 2022

Any idea on if this type of fix works now that Origin has been replaced? I've tried replicating this with the EADesktop.exe files that Steam now installs instead of Origin , as non-steam games added into Steam with both GE-Proton and the new experimental Proton build which supposedly fixed the issues with the new EA app, it does open an EA window but it just says there's an unresolvable error and prompts you to restart the app, which also does nothing.

@andres-asm
Copy link

in the new app there is no way to setup launcher arguments, and the xml file is no longer created so I can't find anyway to fix this...

@gbdrbob
Copy link

gbdrbob commented Nov 21, 2022

in the new app there is no way to setup launcher arguments,

That is not correct, at least for installs via the non-steam EA App version of the game. As per my first post upthread

set -skipvideos as an "Advanced Launch option" in the game properties window (My Collection->Ellipsis menu on the Burnout Paradise tile->"View Properties")

If you have the steam version you may be able to get it to work by launching just the EA app within the game's proton prefix, as per step 2 in the guide above, except the exe you'll want to launch as a non-steam game will probably be: /home/$USER/.local/share/Steam/steamapps/compatdata/1238080/pfx/drive_c/Program Files/Electronic Arts/EA Desktop/EA Desktop/EALauncher.exe

@andres-asm
Copy link

I tried that but I can't find were to set the options, the three buttons ellipsis doesn't have view properties

image

image

image

@gbdrbob
Copy link

gbdrbob commented Nov 21, 2022

Well, shit. It seems the properties menu is locked out when the licence for the game comes from steam. This is what I see, with access to the game via EA Play:

image

image

@gbdrbob
Copy link

gbdrbob commented Nov 21, 2022

OK, Using Process Monitor on Windows I was able to find where the EA App saves the launch options. It's in:

AppData\Local\Electronic Arts\EA Desktop\user_**long unique id**.ini

for the steam version on a deck look in:

/home/deck/.steam/steam/steamapps/compatdata/1238080/pfx/drive_c/users/steamuser/AppData/Local/Electronic Arts/EA Desktop

try adding this line to the ini file and it might enable skipping the launch videos:

user.gamecommandline.origin.ofr.50.0002535=-skipvideos

Though it may not work if the steam version has a different ID internally within the EA app, if the ID is different you may be able to find what it is within the EADesktop.log file in AppData/Local/Electronic Arts/EA Desktop/Logs

EDIT: Just found this reddit post which states that the Steam version game ID is Origin.OFR.50.0002541, however even with the correct ID, the EA App ignores launch settings in the ini file for steam games :-(

@gbdrbob
Copy link

gbdrbob commented Nov 21, 2022

One final idea. Apparently launch options was not originally a feature in the EA App. This post on the EA forums details how people worked round that issue on Windows. You'll need access to a windows PC for the iexpress.exe needed to convert a batch file to an exe, but in theory it should work, unless the passing of command line options is completely broken under Proton.

@andres-asm
Copy link

Odd, I just confirmed on windows -skipvideos as a steam launch argument works...

@parkerlreed
Copy link

Weird, still not working here as a Steam launch argument. About to try the ini edit

@parkerlreed
Copy link

parkerlreed commented Nov 21, 2022

I do NOT have an EA Launcher in Local but do have a Origin under Roaming...

/home/deck/.steam/steam/steamapps/compatdata/1238080/pfx/drive_c/users/steamuser/AppData/Roaming/Origin/

Maybe this is from them switching back? (I never loaded the game when the EA Launcher was pushed)

EDIT: Okay I'm out of ideas... Mine's still using Origin and crashes shortly into the loading screen of the game.

I have NO user*ini file

(deck@steamdeck ~)$ find /home/deck/.steam/steam/steamapps/compatdata/1238080/pfx/drive_c/ -name "user*ini"
(deck@steamdeck ~)$ 

EDIT2: Forgot Origin's was an XML file. Will retry the edits.

/home/deck/.steam/steam/steamapps/compatdata/1238080/pfx/drive_c/users/steamuser/AppData/Roaming/Origin/local_xxxxxxxxxxxxxxxxxxxx.xml

EDIT3: Already had the file edited so I'm crashing with the -skipvideos (assuming that's working)

  <Setting key="GameCommandLineArguments" type="10" value="#//Origin.OFR.50.0002541_-skipvideos"/>

EDIT4: Wiped the compatdata and NOW it's using EA App. Go figure. Will update if anything changes.

@parkerlreed
Copy link

Fresh compatdata, new launcher. Doesn't crash but stays on black with white cursor with and without -skipvideos in the Steam launch args.

Confirmed -skipvideos as a launch arg is not making it to the exe as far as I can tell

deck       31679  0.1  0.0  27160  4680 ?        Ss   13:48   0:00 /usr/lib/pressure-vessel/from-host/bin/pressure-vessel-adverb --generate-locales --fd 23 --regenerate-ld.so-cache /run/pressure-vessel/ldso --add-ld.so-path /usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu --add-ld.so-path /usr/lib/pressure-vessel/overrides/lib/i386-linux-gnu --set-ld-library-path /usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/aliases:/usr/lib/pressure-vessel/overrides/lib/i386-linux-gnu/aliases --exit-with-parent --subreaper --shell=none --terminal=none --ld-preload=/home/deck/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so --ld-preload=/home/deck/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so -- /home/deck/.local/share/Steam/steamapps/common/SteamLinuxRuntime_soldier/pressure-vessel/bin/steam-runtime-launcher-interface-0 container-runtime /home/deck/.local/share/Steam/steamapps/common/Proton - Experimental/proton waitforexitandrun link2ea://launchgame/1238080?platform=steam&theme=bprm -skipvideos
deck       31703  0.3  0.1  44260 19076 ?        S    13:48   0:00 python3 /home/deck/.local/share/Steam/steamapps/common/Proton - Experimental/proton waitforexitandrun link2ea://launchgame/1238080?platform=steam&theme=bprm -skipvideos
deck       31709 17.3  0.1  47084 20540 ?        Rs   13:48   0:06 /home/deck/.local/share/Steam/steamapps/common/Proton - Experimental/files/bin/wineserver
deck       33104  0.0  0.0   6564  2488 pts/1    S+   13:49   0:00 grep --color=auto -i proton
(deck@steamdeck ~)$ ps aux | grep -i burn
deck       32861  3.7  1.1 2911888 169760 ?      Sl   13:48   0:02 C:\Program Files\Electronic Arts\EA Desktop\EA Desktop\EASteamProxy.exe Z:\home\deck\.local\share\Steam\steamapps\common\BurnoutPR\BurnoutPR.exe?
deck       32951  116 13.8 3381568 2096376 ?     Rl   13:48   1:06 Z:\home\deck\.local\share\Steam\steamapps\common\BurnoutPR\BurnoutPR.exe

@parkerlreed
Copy link

parkerlreed commented Nov 21, 2022

The ID IS different but still doesn't work with the newer ID

Origin.OFR.50.0002541

image

@andres-asm
Copy link

yeah I'm on the same boat, at this point I may try to install mfplat to see if it fixes video playback instead

@gbdrbob
Copy link

gbdrbob commented Nov 23, 2022

Odd, I just confirmed on windows -skipvideos as a steam launch argument works...

Are you sure about that? On my Windows 10 system if I add the non-steam version to Steam, setting -skipvideos as a launch option in the Steam shortcut properties doesn't work; i.e I can only get -skipvideos to work by setting it as a launch option within the EA App.

@andres-asm
Copy link

andres-asm commented Nov 23, 2022

yup 100% on the steam versions
that's the thing, you get a "manage on steam" thing instead of the properties, and it works

image

This is enough on the steam version while running under windows

@Firestorm7893
Copy link

yeah this sucks a lot. I tried installing origin separately but since the game is from steam, when I click download on origin steam opens and installs the Ea Launcher. Looks like there's really nothing we can do about it, unless there is a way to inject the argument when the process starts :(.

@singularity8
Copy link

I just get a blue rectangle when I try to launch, and no origin folder is in my program files (x86) folder. Any ideas what I can do? Thanks. 44785B9E-6279-4362-BBCE-A510E509DCD6

Fixed it myself by manually downloading origin, installing it and moving it to the correct folder. Hopefully that helps anyone else trying to do it.

I can confirm that this works for me as well

@andres-asm
Copy link

it works to install the game.
does it work to play?

@stratusfear
Copy link

EDIT: Just found this reddit post which states that the Steam version game ID is Origin.OFR.50.0002541, however even with the correct ID, the EA App ignores launch settings in the ini file for steam games :-(

Oh hey...that was me...

One final idea. Apparently launch options was not originally a feature in the EA App. This post on the EA forums details how people worked round that issue on Windows. You'll need access to a windows PC for the iexpress.exe needed to convert a batch file to an exe, but in theory it should work, unless the passing of command line options is completely broken under Proton.

The process detailed at the link worked for me (finally!!), just did it on my Windows box and scp'd over to the deck, renaming BurnoutPR.exe first of course. I used the following inside the batch file:

start E:\steamapps\common\BurnoutPR\BurnoutPR.orig.exe -skipvideos

Dunno how different the path is between installing the game on internal storage vs the SD card (I used the latter), and probably entirely different for Proton on Linux users. But it does appear that passing command line options is specifically broken for the EA app on Proton, and not in general. WTG EA...

@kyudongkim
Copy link

Get exe files.
install note

  1. re name file on your Steam deck : BurnoutPR.exe -> BurnoutPR.orig.exe
  2. copy BurnoutPR.exe same folder.
  3. Finish!! fun play!
    https://github.com/kyudongkim/SteamDeck.BurnoutParadiseSave

@kamisenpai
Copy link

This post on the EA forums

Ok guys so... I did it. It works on the steamdeck right now. I followed the suggested guide for the forum link but with a twist. I don't know if the exe from kyudongkim works since I try not to download random exes, but I will tell you how I did it for my steam deck. You'll have to use windows and do mostly the same steps, but with a few different details.

  1. You can make the .bat file in windows wherever you want but inside of it put:
    start Z:\home\deck\.local\share\Steam\steamapps\common\BurnoutPR\BurnoutPR.orig.exe -skipvideos
    That seems to be the location to access the game exe on the steam deck from within the proton virtual folders. You can check it yourself with protontricks and browse folders, but you also have to type .local in the explorer path since it's hidden by default and I didn't find a way to show hidden folders.
  2. Follow the forum post and make your own exe file. You should have now a exe file called "BurnoutPR.exe"
  3. Copy that exe in your burnout folder from the steam deck and make sure the original exe is named BurnoutPR.orig.exe otherwise it won't work
  4. Enjoy the game!

Not sure if it matters but I use GE proton for the game and Proton experimental for the EA App. I also disabled the overlay in the EA app. And I also used the save game provided in this post. Hope that helps!

@lolgzs
Copy link

lolgzs commented Jan 22, 2023

Thanks, works on the deck ! As I don't have windows I've managed to build an BurnoutPR.exe from the .bat file using wine and a bat to exe converter (several exist on github). Here's the BurnoutPR.exe that I use : https://www.dropbox.com/s/h7f1tt0gb6sjrr7/BurnoutPR.exe?dl=0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment