Open frostworx opened 4 years ago
a steam log from another user: https://github.com/ValveSoftware/Proton/issues/3937#issuecomment-640875228
Hello @frostworx, looks like this game would benefit from support for Media Foundation maturing.
More specifically: fixme:mfplat:MFTEnumEx ({d6c02d4b-6833-45b4-971a-05a4b04bab91}, 51, 21F6FB9C, 21F6FBBC, 21F6FB90, 21F6FB8C): stub
lead to an access violation and wine: Unhandled page fault on read access to 00000000 at address 058C5B9A (thread 0bb4), starting debugger...
hi @kisak-valve thought so too, but the known dirty hack didn't fix it (maybe I applied it at the wrong testing state though). No big deal for me personally, pretty sure the game is almost the same as the ultimate box version. just wanted to open a "proper" bug report
hm, I'm afraid I was wrong with the "-skipvideos" commandline parameter working on steam. so likely the change directly in origin is the only option: https://github.com/ValveSoftware/Proton/issues/3937#issuecomment-641121544 updating initial post as well...
yes, with skipvideos correctly applied you get further. it crashes when you select "start game" in the main title. attached is the new log steam-1238080.log
sorry for the noise...
How do you get origin open long enough to set launch options for a game in it? When I click play in steam, it just railroads in to opening origin, then the game and crashing.
there might be an easier way, but I used PROTON_DUMP_DEBUG_COMMANDS to get a runfile, and adjusted it to just launch the launcher instead of the game.
Burnout Paradise Remaster can't run in Debian 10.4
Issue transferred from https://github.com/ValveSoftware/Proton/issues/4012. @SandHilt posted on 2020-06-22T04:02:48:
Origin install but can't open game like this guys https://www.protondb.com/app/1238080
1, Install origin setup.
After trying the -skipvideos parameter, the game still gets stuck on the loading screen and never loads. The newer proton versions fix the origin crash but the game still refuses to start
Here is a log from proton 5.0-9 with WINEDEBUG="+timestamp,+pid,+tid,+seh,+debugstr,+module" %command%
-skipvideos
is set in origin launcher, game gets passed the loading screen, and up to press and key to start/continue
(Log is 88Mb uncompressed) steam-1238080.log.tar.gz
@dantob Maybe I'm looking at this wrong, but I can't really find what the cause of the crash is from the log:
Would you mind sending a full log? (WINEDEBUG=+all,-heap
) Hopefully it will shine more light on this
I created a new prefix and can no longer get origin to 'wait' long enough to add the -skipvideos
option (so the game doesn't make it passed the into video atm)
WINEDEBUG=+all,-heap %command%
just crashes right away and wont even launch origin
here's what it logged though (157Mb uncompressed) steam-1238080.log.tar.gz
With Proton 5.9-GE-5-ST i managed to get past the loading screen. Then i was presented with a mouse pointer and a black screen. No sound. steam-1238080.log
I managed to make this work via Lutris and I have Origin version of the game. You need to have -skipvideos
option and copy your save game post initial intro video (may be copy from a windows machine if you have one). Apparently -skipvideo option doesn't skip the intro video and the game crashes.
I managed to make this work via Lutris and I have Origin version of the game. You need to have
-skipvideos
option and copy your save game post initial intro video (may be copy from a windows machine if you have one). Apparently -skipvideo option doesn't skip the intro video and the game crashes.
Every solution that entails borrowing a savefile from Windows is not a solution at all. Still i'm glad to hear that mf is the only issue with the game.
I've noticed recently that the game has stopped working with any version of proton newer than 5.13-6. It gets to the loading screen with the spinning icon but then freezes and crashes to desktop before it gets to the "start" screen.
Hello @gigabz666, please add PROTON_LOG=1 %command%
to the game's launch options, reproduce the regression, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy your system information from Steam (Steam
-> Help
-> System Information
) and put it in a gist, then include a link to the gist in this issue report.
Hello @gigabz666, please add
PROTON_LOG=1 %command%
to the game's launch options, reproduce the regression, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy your system information from Steam (Steam
->Help
->System Information
) and put it in a gist, then include a link to the gist in this issue report.
https://gist.github.com/gigabz666/3dd732807d0d684f24a919d7ac3e710e steam-1238080.log
Hope this helps. I guess two things I should add. I try to run native and also I run the games from an NVME SSD rather than my home directory. I don't know if that's possibly causing issues.
@gigabz666 I'm getting the same crash with 5.13-6 as with 6.3-2. Could you confirm if there is a Proton version that is currently working, and if so, which version? Otherwise, it is possible the game updated in a way that broke with Proton :/
@gigabz666 I'm getting the same crash with 5.13-6 as with 6.3-2. Could you confirm if there is a Proton version that is currently working, and if so, which version? Otherwise, it is possible the game updated in a way that broke with Proton :/
The game still works fine for me on 5.13-6. I have --skipvideos set within Origin and I also had a save file in place from when I briefly played it on Windows (although funnily, last time I tried to play it on Windows it won't run, so win for Linux). It also crashes if I have OBS open and it's using my webcams so there is also some weird thing going on with webcams too.
@gigabz666 I think --skipvideos is probably the key. Do you have a trick for getting that into the origin settings before origin closes?
@alasky17 There is probably a better method to this but I wasn't able to find it or figure it out but I stumbled across this post on the steamcommunity forums that I was able to work with which let me change options within Origin before actually running the game.
https://steamcommunity.com/app/221410/discussions/0/3104638636521148019/
Just wanted to add that the game now runs again with the latest version of Proton Experimental.
Just wanted to add that the game now runs again with the latest version of Proton Experimental.
With -skipvideos
within Origin, I guess?
edit: tested and it crashes on the first screen with "Loading".
Just wanted to add that the game now runs again with the latest version of Proton Experimental.
With
-skipvideos
within Origin, I guess?edit: tested and it crashes on the first screen with "Loading".
Correct, I hadn't changed any of my options in Origin so I still had that flag.
The game runs with Proton Experimental or Proton 6.3 but crashes at the Loading screen after a while. I tried to add a save file downloaded from here but still didn't work. Could someone provide another Save file so I can test?
Finally runs !
To verify, run Steam via Terminal, run the game and see output.
If having libv4l2: error setting pixformat: Device or resource busy
Unplug your webcam !
This should be the game's bug itself preventing it to load if webcam is detected (not Proton's bug).
I got the game working on my Steam Deck by adding -skipvideos to the launch options in the EA App beta (installed within steam as a non-steam app). On first launch for a new player even with skipvideos configured the game plays an unskippable video that crashes the game (black screen with white mouse pointer, no way to progress). That can be worked around by using a save game file from just after the video has played, as described here.
I can only play by launching the game from within the EA App. When trying to launch the game exe directly it seems to ignore the -skipvideos setting in the EA Play app and I get a hang on a blank screen.
I would like to note you will have issues with doing the -skipvideos workaround if you're on a steamdeck and you have the game installed to the microsd card. Origin will refuse to find the game files. Reinstalling the game on the internal storage allows you to go through the process as expected.
Finally once you get past the video issue I've found that online doesn't work, as soon as you try to drop into an online lobby the game freezes. Audio keeps playing but it seems like the main game thread just gets frozen.
Finally once you get past the video issue I've found that online doesn't work, as soon as you try to drop into an online lobby the game freezes. Audio keeps playing but it seems like the main game thread just gets frozen.
I can confirm this. I've also once had it crash on just opening the quick menu for on-line play (D-Pad right in the default controller layout). Other times the menu load and I've been able to view leaderboards, but actually dropping into a game results in a frozen screen with audio continuing to play. This is with GE- Proton-7-24 and Proton Experimental
I would like to note you will have issues with doing the -skipvideos workaround if you're on a steamdeck and you have the game installed to the microsd card.
This isn't the issue I had, game is installed on the internal SSD, however -skipvideos only works when launching the game manually from within the EA App (with -skipvideos set as an "Advanced Launch Option"). Launching BurnoutPR.exe directly with -skipvideos set as a launch option in the Steam shortcut settings doesn't work.
Slightly easier way of getting -skipvideos
where it needs to be;
Go into compatdata/1238080/pfx/drive_c/users/steamuser/AppData/Roaming/Origin/
, and there should be a file local_xxxxxx.xml
, with a string of numbers that I believe corresponds to your user ID.
Edit this file, and add
<Setting key="GameCommandLineArguments" type="10" value="#//Origin.OFR.50.0002541_-skipvideos"/>
to line 14, directly above HotKeyString
. This is where Origin saves it's launch args, so you can just edit it in manually there. This saves having to mess around launching origin with a different shortcut to set the arg.
Backtrace of all threads of the hang before the menu.
According to reports here users with a Steam licence to the game cannot set launch arguments within the EA app, which means the -skipvideos workaround is unavailable to them.
Users with a non-steam licence can successfully run the game by setting the launch argument within the EA app.
There are also reports that setting -skipvideos as a launch option in Steam works under Windows for the Steam version of the game,
However I have found that on my Windows 10 system with a non-steam version launch options set within Steam are not passed to the exe. So it's unclear to me whether the problem lies with the EA app or Proton.
Yes I can confirm this. Thing is, when you run the non-steam version, you can add the skip videos on the EA app When you run the steam version, that option is missing on the EA app
But for some reason the parameter isn't forwarded from steam to the game.
I tried many things, including mfplat to no avail.
Replying to https://github.com/ValveSoftware/Proton/issues/3960#issuecomment-864568160
I have exactly the same error - but how would I unplug my camera on a laptop. It's built in :-P Is there any way to make it "invisible" to the game via launch options?
Replying to #3960 (comment)
I have exactly the same error - but how would I unplug my camera on a laptop. It's built in :-P Is there any way to make it "invisible" to the game via launch options?
Try using this Ask Ubuntu answer. Should work on other Linux distros, too, both modprobe and uvcvideo seem common.
Disabling the camera with sudo modprobe -r uvcvideo
made the game crash after the Loading screen faded out as opposed of it doing it before that. Installing Media Foundation with protontricks did nothing. I can't access launch options on the new EA App, unfortunately.
I can't access launch options on the new EA App, unfortunately.
If it’s the steam version the only known workaround is to rename BurnoutPR.exe (e.g to BurnoutPR.orig.exe
), create a batch file that calls it with the -skipvideos option (i.e start E:\steamapps\common\BurnoutPR\BurnoutPR.orig.exe -skipvideos
) and then convert the batch file to an exe which you name BurnoutPR.exe
Full details in the comments here . You’ll also need the save file from there to skip an otherwise unskippable video that plays when you start the game for the first time.
Online play will still be broken but you should be able to get in-game for single player.
I can confirm that trying to join a game online still causes the main thread to completely halt. It does not seem like blacklisting the module helps.
Hello, I used the option to verify the authenticity of files, in all games, a while after going to proton rc.
In Burnout Paradise Remastered (EA Play) the main menu is not reaching, and the Ea play app is freezing, the screens have no information, only once it appeared correctly for login, etc. And Steam always restarts after the game does not open
The EA application also does not appear on the desktop.
When using the delete proton files option, in the big picture, restart the system. Check the authenticity of the files, restart the system, using the big picture, and then try to start the game, the app does not install and the game does not start. (Kubuntu 23.04, wayland)
Proton rc 8.0-4 Kubuntu lts Steam .deb
👍😄
The changelog for the latest Proton Experimental update says that this game is now playable, but for me it still crashes if I don't use any tricks to skip videos or whatever, so what's supposed to be improved with the latest update? Or is it referring to a different game?
My system has a Ryzen 7 6800H APU, with both a Radeon 680M iGPU and a Radeon RX 6650M dGPU, running Arch Linux with kernel 6.5.7 and Mesa 23.2.1. Using either GPU (switching using the DRI_PRIME environment variable) doesn't change anything.
I'd attach the log file but it's over 600MB of trace:unwind:dump_unwind_info
type stuff, even zipped it's still 44MB (which is above the 25MB size limit GitHub has).
I'd attach the log file but it's over 600MB of
trace:unwind:dump_unwind_info
type stuff, even zipped it's still 44MB (which is above the 25MB size limit GitHub has).
You can probably upload it to something like Google Drive and link it here. Or maybe pastebin or a similar service, but idk if they support 600+ MB files
@X-m7 The bug that was blocking it until now has been fixed. The problem is that the game is running out of address space now. It does work on the Steam Deck though, presumably because the smaller screen resolution requires less memory for the video decoding.
Oh yeah, I just got around to trying it on my Deck, even after having wiped the savegame I was able to see the intro videos and get into the gameplay part, neat!
It did crash once after dropping the graphics settings down and applying it, but otherwise it worked for the short time I tried it.
Doesn't work on my deck unfortunately, and I'm using bleeding edge.
For what it's worth my Deck is running SteamOS 3.5.1 preview, with no CryoUtilities or anything like that (I don't even have a root password set on it), and the Proton version selected was already Experimental so I didn't have to change it myself.
Got on my Desktop and tested it, works but I had to unplug my index as it has a V4l2 camera which crashes it during the loading screen, so that bug still exists.
On my desktop PC (R5 2600, RX 570 8GB, 16GB RAM, Fedora 39, single 1920x1080 display) at least the singleplayer works well as long as you unplug the camera. However, on my laptop (MSI Modern 14 C12M-233XRU: i3-1215U, no discrete GPU, 8GB RAM, Fedora 39, single 1920x1080 display) the EA App outright refuses to install. The installation window pops up for a second and disappears, and no other window pops up again, after which other dependencies are installed and the game refuses to start. It might be me using mobile internet instead of home Wi-Fi, though. Both setups were using the latest Proton Experimental version.
UPD: tested on my laptop on my home Wi-Fi, the app still doesn't install.
Maybe D9 driver problem with no native D9 hw on modern intel gpu...
Compatibility Report
System Information
I confirm:
steam-1238080.log
Symptoms
The game fails to start. this has multiple sources 1) origin fails to start correctly and crashes: https://github.com/ValveSoftware/Proton/issues/3937 ( current workaround is to remove kernel32.dll in the games wineprefix in either system32 or syswow64 - depends on the game) 2) the game still would crash because of the intro video. this can be workarounded by adding "-skipvideos" parameter to the game from within origin: see post from above issue 3937 for the workound: https://github.com/ValveSoftware/Proton/issues/3937#issuecomment-641121544
with both workarounds you see a loading screen which crashes as well maybe changing some settings in .....1238080/pfx/drive_c/users/steamuser/Local Settings/Application Data/Criterion Games/Burnout Paradise Remastered/*.ini could fix that as well