Mass Effect™ Legendary Edition (1328670)

[dennis1248]

Compatibility Report

• Name of the game with compatibility issues: Mass Effect™ Legendary Edition
• Steam AppID of the game: 1328670

System Information

• GPU: AMD RX 5700
• Driver/LLVM version: Mesa 21.0.3 | LLVM 12.0
• Kernel version: 5.11.19
• Link to full system information report as Gist: System information gist
• Proton version: 6.3-3

I confirm:

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

Proton log

steam-1328670.log

Origin error log

pfx/drive_c/ProgramData/Origin/Logs/MassEffectLauncher_OnlineActivation_Log.html

Missing DLL: api-ms-win-core-psapi-ansi-l1-1-0.dll  Function: K32GetModuleBaseNameA

Symptoms

Origin client installs, after install when it attempts to launch the game it shows the following error "There is a problem with your game's setup. Please reinstall your game." afterwards nothing happens.

Any subsequent launch will show the same behaviour.

Reproduction

1. Launch game
2. Let Steam install deps and wait for Origin client install to appear
3. Follow on-screen instructions to complete Origin client install
4. Wait for the error to show after the Origin client has launched and it attempts to start the game

[fardragon]

System Information

• GPU: RX 5700XT
• Driver/LLVM version: 21.0.3-3
• Kernel version: 5.12.1-zen2-1-zen
• Link to full system information report as Gist: https://gist.github.com/fardragon/ad3cc29c8698b94bf0c396c9545bbc36
• Proton version: experimental-6.3-20210512b

steam-1328670.log

Same behaviour here

[YamiYukiSenpai]

Same here. I tested other games that require Origin, like Jedi Fallen Order, and it's the same thing.

I tried to install Origin manually and that failed, too, with error 3:0, and another time with 9:0

[garpu]

New Proton update a few minutes ago. Any change?

[NTMan]

steam-1328670.log

system information

[YamiYukiSenpai]

New Proton update a few minutes ago. Any change?

Nope

[YamiYukiSenpai]

Currently looking into 9:0 error. Does Proton install the latest .NET?

[YamiYukiSenpai]

Has anyone experienced 3:0 error when they manually install the full Origin using the script?

[YamiYukiSenpai]

Latest Proton update says that Origin has crashed, so I guess that's progress.
I'm currently watching my System Monitor, and I can see that EALink is working...It's slow, though. Trying to remember if it ever was this slow.

Edit: just logged into my Origin account and Legendary Edition definitely got linked.

[synlic]

I'm installing latest .NET (https://dotnet.microsoft.com/download/dotnet-framework/net48) rigth now in the prefix. On slow internet connection though, so it takes a while. Will update when I have tried it.

Using the command:

STEAM_COMPAT_DATA_PATH="/mnt/storage/SteamLibrary/steamapps/compatdata/813780" WINEPREFIX=$PWD "/mnt/storage/SteamLibrary/steamapps/common/Proton - Experimental/proton" run ~/Downloads/ndp48-web.exe

Edit: I had to install it via Protontricks due to otherwise failing. It however does not start properly. Same error message. I'll continue testing installing other windows components using protontricks.

[YamiYukiSenpai]

Proton 6.3 - "Try relaunching your game to continue linking your accounts".

Proton Experimental - "There's a problem with your game's setup."

[Aralakh]

The game is linked in my Origin account as well, but I can't download it through Origin to try installing/playing that way (not sure if that's as expected, never tried that with a Steam-linked Origin game). Tapping the download button in Origin does nothing (works for other non-Steam-linked games). Tried running through Steam again with the latest proton update and get the same message as before, "There is a problem with your game's setup. Please re-install your game."

[synlic]

I keep getting pop ups saying "Try relaunching your game to continue linking your accounts".

Try deleting (rename the folder named pfx) the prefix: /path/to/steamlib/common/compatdata/1328670

[YamiYukiSenpai]

Origin launched once, but the game wouldn't

[R8YsDcYwuy3]

Has anyone experienced 3:0 error when they manually install the full Origin using the script?

I had that error when using older Proton versions

[garpu]

https://steamcommunity.com/app/1328670/discussions/0/5002914669818221672/ Possibly not just us having the problem?

[bundyo]

Interesting, so changing the locale should help?

[YamiYukiSenpai]

Interesting, so changing the locale should help?

How would we do that in Proton? Is that possible?

[garpu]

Interesting, so changing the locale should help?

I'm not certain? I think it may be an issue with windows 7.

[YamiYukiSenpai]

Interesting, so changing the locale should help?

I'm not certain? I think it may be an issue with windows 7.

Apparently not. The locale thing works on 10 only

[DistantThunder]

From this:

• https://answers.ea.com/t5/Mass-Effect-Legendary-Edition/Mass-Effect-Legendary-Edition-on-Origin-does-not-start/td-p/10339434/page/6

gez1122

3m ago
@EA_Mako I found a solution that seems to work for a lot of people.
go to control panel- region- change date time or number formats- administrative- change locale- and then check the box >that says
BETA: use unicode UTF 8

Rather than the locale, it appears to be a option that enables UTF-8 (Codepage 65001) support for Win10.
Don't know how Wine deals with that, I doubt it's implemented / exposed since if I understand correctly Wine has a whole logic to re-implement Windows codepage into Unicode which is natively supported on Linux:

https://source.winehq.org/git/wine.git/blob/HEAD:/tools/make_unicode

Not sure if just adding the registry keys that option implement would be enough or if this needs proper Wine patching.

[SebiTimeWaster]

i doubt it has to do with utf-8 support. i presume it is one of the usual windows bugs that solve them selfs as soon as something is changed.

[R8YsDcYwuy3]

https://steamcommunity.com/app/1328670/discussions/0/5002914669818221672/?ctp=4#c5002914669818808341 Latest reply on this thread says UTF-8 is causing the issue and fixing it makes the game work

[mmatis]

I tried adding LANG=en_US.UTF-8 to the launch params for the heck of it. No effect. I assume wine/proton sets this in the prefix based on the host system anyway, but maybe there's some obscure windows-specific reg key that isn't set/created by this.

[YamiYukiSenpai]

Here's a response from an EA Community Manager about this. Does Wine do some special characters that appear normal in Linux?

[Plagman]

Yes, Proton game paths contain a . by default if they're located in your default Steam Library. Can you check with PROTON_SET_GAME_DRIVE=1 set, maybe?

[synlic]

My game, prefix and Proton version are all located in /mnt/storage (not in home folder), so I don't think it matters that there is a "." in i file path.

[ThisNekoGuy]

To add-on to my earlier report, the Trilogy Save Editor fails to finish installing because of a dependency on "Microsoft Edge Webview2 Runtime," which has what appears to be an upstream regression(?). It apparently used to run with upstream Wine, but either an update to the runtime installer itself or Wine (and by extension Proton) had some regression that causes it to infinitely load. Waiting for a bit, it seems to download (a window for downloading it appears), but it stalls on actually installing it:

The Trilogy Editor is required for some circumstances where the game has long-standing quest bugs related to saving and exiting the game before they've been completed. If someone, like me, has been unfortunate enough to only use one save slot and find this out too late, this can set the player back hours of playtime to solve an issue that the save editor can fix in just a few clicks. I hope someone will be willing to consider helping fix this. Also note that using the GUI to cancel its failing installation doesn't work either: you actually have to kill the process.

Log (before clicking cancel):
steam-1328670.log

Log (after clicking cancel):
steam-1328670.log

[syberphunk]

@ThisNekoGuy Could you try using an older version of the WebView2 installer? You can find 110221-MicrosoftEdgeWebView2RuntimeInstallerX64_109.0.1518.61.exe available in https://archive.org/details/patches_2023-01 as there's a comment in https://www.reddit.com/r/Lutris/comments/rpomzv/you_do_not_have_the_microsoft_webview2_runtime/hwivkgo/ saying it should work from a year ago.

[kisak-valve]

Mass Effect Legendary Edition doesn't launch. Warning about optional parameter "-locale {locale}"

Issue transferred from #7587.
@gnusuari0 posted on 2024-03-20T01:42:55:

Compatibility Report

• Name of the game with compatibility issues: Mass Effect Legendary Edition
• Steam AppID of the game: 1328670

System Information

• GPU: Radeon VII

• Video driver version: Mesa 23.3.6 (radv)
  steam-1328670.log

• Kernel version: 6.7.9

• Link to full system information report as Gist: https://gist.github.com/gnusuari0/c7700e7fff6453818e72eb902d09a339

• Proton version: Proton 9.0 (beta)

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.

Symptoms

It suddenly stopped working. I only wanted to restart a playthrough and I removed the old saved profiles. I can't launch the game anymore. I have tried with STEAM_RUNTIME=0 but doesn't work either.

Sometimes it crashes like in this issue: #7543
Other times Steam warns about the app trying to launch with optional parameter "-locale {locale}" and advises to cancel if I don't understand that. If I click on continue it launches again the EA App, it closes and shows the same message of optional parameter with one extra "locale", that is, "-locale {locale} -locale {locale}".
Other times EA App shows up and closes itself without further notice.
Other times nothing shows up at all.

Tried with Proton 7 which worked while Proton 8 didn't. But it also shows the same message about optional parameter. So does Proton 8. If you wait enough time with the dialog about optional parameter, the EA App may show its crash message window. Steamwebhelper is running in the background.

Reproduction

Try to launch the game. It doesn't start. EA App can crash, closes itself or Steam show a message about optional parameter.

---

@gnusuari0 commented on 2024-03-20T02:24:55:

Tried restarting the computer and verifying installation files. Nothing.

[gnusuari0]

In reply to #4823 (comment), I managed to apply a workaround. Remove the game folder inside the compatdata folder of your Steam library. Before doing so backup your save files (/compatdata//drive_c/users/steamuser/Documents/BioWare) in case you want to preserve them.

After deletion launch the game. Steam will reconstruct the prefix. Now if you want you can restore your save files.

Somehow EA App broke by playing with savefiles. And because it's not a proper game file it is installed in /compatdata with the installation scripts instead of being included in the game distribution folder (/common). I previously had problems with the EA App by deleting save files, showing up a dialog about that it could not find save files but it let me continue and launch the game.

Guess that it's not resilient enough. And that it does more things than being a mere launcher. AFAIK it does not synchronize game saves with EA servers.

[Plarpoon]

Compatibility Report

• Name of the game with compatibility issues: Mass Effect Legendary Edition
• Steam AppID of the game: 1328670

System Information

• GPU: AMD Radeon RX 7900 XTX
• Video driver version: Mesa 24.0.7
• Kernel version: 6.8.9-300 Fedora 40 (KDE)
• Link to full system information report as Gist:
• Proton version: Experimental, 9 and 9.4 GE

I confirm:

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

Proton logs while doing first installation of EA App
(INSTALLING EA_APP) steam-1328670.log

Actual Proton Log when trying to execute the game
steam-1328670.log

Hey everyone, hey Kisak, long time no see.
I wanted to say that Mass Effect LE doesn't really launch at all pretty much confirming the above issue written by @gnusuari0. Perhaps it would be best to really look into this one as it seems to be hitting multiple systems.

I have also completely deleted the Proton prefix for this game and that's how I tested the first installation of the launcher again but with no good success. If any of you happens to know of an old version of Proton that actually makes it work perhaps we can look at what change over the years because I have very clear memories of running this on my system before. I am now on Fedora 40 KDE btw, please ping me if you want me to do any further testing and debugging, I am your guinea pig!

Reproduction

1. Press play
2. The button becomes pressed for a few seconds then it goes back to being the green "PLAY" button like nothing has happened

[kisak-valve]

Hello @Plarpoon, there's a known kernel regression in 6.8.9 that was tracked and fixed in https://gitlab.freedesktop.org/drm/amd/-/issues/3343. You could try rebooting into an older kernel and see if that has an effect.

[Plarpoon]

Hey man, nice to see you again,
I am currently testing it with Kernel 6.8.8 which according to the FreeDesktop issue you linked me is one of the "good" kernel versions but the issue still persists.

This is the log captured with 6.8.8.
steam-1328670.log

Also I saw in that thread they suspect it might be an issue so I double checked and I have both "Above 4G decoding" enabled and also "Resize BAR Support".

[Plarpoon]

Ah, forgot to mention, when I say it does not launch at all I actually means it won't launch Mass Effect launcher.

Mass Effect LE on Steam has effectively three launcher to be executed in sequence:

1. Steam (well that one works obviously)
2. The EA App, which in my case I can see the popup of it updating and launching but it never actually opens its window
3. The Mass Effect Launcher where you can select between the three games, I never reached this step in these recent days (I did about a year ago with this very same hardware)

[Plarpoon]

I am actually curious, is there anyone subscribed to this issue that can test this game and tell me if it works with the most recent Proton version? - Because I am starting to believe this game might just be borked

[Wedge009]

It seems to me that, unfortunately, anything tied to EA's or other third-party DRM inherently has difficulties working with Steam/Proton. Consequence of the current walled garden approach to distribution.

[Plarpoon]

Yeah, just by scrolling back up to over a year ago I can notice people with all sorts of distros having the same issues as me and not being able to reach past the EA App launcher. I was concerned it might have something to do with my Fedora installation due to its native SELinux integration but it seems this issue was existing already in the Proton 7 era even with people using Ubuntu.. so that is clearly not the case.

As said if anyone can at this very moment in time run the game please write it here, I am seriously convinced it might be borked for everyone

[Plarpoon]

I have good news, the game somehow works on my Steam Deck. So something must be missing on my PC I guess, if anyone has any clue on how I could check the differences let me know.

Again, please if anyone can run this game on PC let me know.

[NextGenRyo]

I don't use it often but you might try PROTON_LOG and see the difference there. For anyone having issues with the EA app crashing. That's kinda become a thing with the app. I just launched the game again and hope it works that time. I usually don't need to launche the game more than twice. Once I'm in the game, everything works great. I'm even using mods in game and no issues. I'll mention that I think when using proton 9 the ea app crashes more often. I haven't tested it long enough to be sure. I then set it to use its own recommended proton (experimental) and I'm happy with that.

…

On Mon, 20 May 2024, 10:15 Alessandro Suha, ***@***.***> wrote: I have good news, the game somehow works on my Steam Deck. So something must be missing on my PC I guess, if anyone has any clue on how I could check the differences let me know. Again, please if anyone can run this game on PC let me know. — Reply to this email directly, view it on GitHub <#4823 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABHOYDAEME7XKISWKX5YWJTZDG5LJAVCNFSM444VIDT2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMJSGAYDENZWG44A> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Plarpoon]

I took your tip, this is the extracted PROTON_LOG from the Steam Deck
(Steam-Deck)steam-1328670.log

And this is one taken from my Fedora 40 KDE installation
steam-1328670.log

As you can see the Steam Deck one actually failed to launch the launcher the first time I tried with PROTON_LOG enabled, I had to launch again for it to actually properly boot the third launcher, which in my opinion is rather odd. But other than that I must be blind but I cannot see major differences between the two logs.

[Plarpoon]

Small Update:
As much as I try several times in a row to launch with different Proton versions I never manage to execute it successfully, not even once. Unlike with the Steam Deck Proton 9 version which might fail once or twice but it will without a doubt work after some attempts.

I actually managed to get a window from the EA App on Fedora but it doesn't render and remains completely black on Proton 6.3:
(Proton6.3-Crash)steam-1328670.log

This is the most I managed to achieve until now on PC

[NextGenRyo]

Did you try removing the proton prefix of the game? Sometimes that has an affect.

…

On Mon, 20 May 2024, 11:15 Alessandro Suha, ***@***.***> wrote: Small Update: As much as I try several times in a row to launch with different Proton versions I never manage to execute it successfully, not even once. Unlike with the Steam Deck Proton 9 version which might fail once or twice but it will without a doubt work after some attempts. I actually managed to get a window from the EA App on Fedora but it doesn't render and remains completely black on Proton 6.3: (Proton6.3-Crash)steam-1328670.log <https://github.com/ValveSoftware/Proton/files/15375823/Proton6.3-Crash.steam-1328670.log> This is the most I managed to achieve until now on PC — Reply to this email directly, view it on GitHub <#4823 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABHOYDEKQ2W2OJMNPNMGYDLZDHENVAVCNFSM444VIDT2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMJSGAYTGNJXHA3Q> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Plarpoon]

Yup.. Once I completely uninstalled and reinstalled the game, other times just deleted the related compatdata directory which as far as I know contains the entire prefix.

[Plarpoon]

Also probably unrelated to the actual crash but I noticed on Steam Deck the EA App doesn't save its login token. So each time you turn off the "console" and start the game again you have to input newly your OTP to log in with your EA account.

[NextGenRyo]

Yea I done think that ea app issue has anything to do with it. Unfortunately I don't have many more ideas. Do other EA app games work? If I knew something worked before but doesn't now for a none obvious reason, I would back-up my files and install the OS again. If that didn't work then I would select another, because maybe the OS has done some changes 🤔

…

On Mon, 20 May 2024, 11:24 Alessandro Suha, ***@***.***> wrote: Also probably unrelated to the actual crash but I noticed on Steam Deck the EA App doesn't save its login token. So each time you turn off the "console" and start the game again you have to input newly your OTP to log in with your EA account. — Reply to this email directly, view it on GitHub <#4823 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABHOYDB5CSGASKEVSWM3KHLZDHFOXAVCNFSM444VIDT2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMJSGAYTKMBZHEZA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Plarpoon]

Unfortunately I do not think this has much to do with Fedora 40 specifically. If you scroll up you can read that even as late as a year ago people were experiencing the same issues on distros like Ubuntu which are very different from the RHEL builds.

I repeat again, this game worked before for me with the same hardware combination and various different distros too.

[Plarpoon]

I tried running the game with the experimental Proton version again
(EXPERIMENTAL)steam-1328670.log and I think I discovered the issue (if anyone else can confirm it too I would be very happy).

I think the internal launcher crashes simply because there is no way to properly open the window on screen, particularly with these lines:

11378.435:0128:012c:fixme:uiautomation:UiaRaiseAutomationPropertyChangedEvent (000000000F0C25F8, 30005, 00000000001158D0 {VT_EMPTY}, 00000000001158B0 {VT_BSTR: L"Critical Error Event"}): stub

11378.451:0128:012c:fixme:uiautomation:UiaRaiseAutomationPropertyChangedEvent (000000000EFFBA88, 30005, 0000000000111D90 {VT_EMPTY}, 0000000000111D70 {VT_BSTR: L"Critical Error Event"}): stub

I tried forcing the game launch from Gamescope since as mentioned before the game works properly on my Steam Deck (which is using Gamescope by default) but unfortunately this issue still persists as it can be seen here:
steam-1328670.log

I now have two questions for everyone who reads this issue:

1. Can you actually boot the game?
2. If the answer to the first question is yes, do the two errors I mentioned above still present themselves in your logs?

[rkfg]

If it helps, for me the game runs flawlessly on the stock Proton 9.0-1. I didn't run the actual gameplay but I installed it, clicked Play and it just works. It installed EA App, then launched the launcher, I chose ME1, and it started just fine. I clicked various menu items, then exited. My system info: https://gist.github.com/rkfg/efaebb4f111f7dd1cbfde34e5b381abb

I have lines in the log similar to what you mentioned:

1137500.654:037c:0380:fixme:uiautomation:UiaRaiseAutomationPropertyChangedEvent (000000000F0FB978, 30005, 0000000000111DD0 {VT_EMPTY}, 0000000000111DB0 {VT_BSTR: L"Toggle Internet"})
: stub
wine: setpriority -10 for pid -1 failed: 3
1137500.663:037c:0380:fixme:uiautomation:UiaRaiseAutomationPropertyChangedEvent (000000000F127228, 30005, 0000000000115910 {VT_EMPTY}, 00000000001158F0 {VT_BSTR: L"Critical Error Event"}): stub
wine: setpriority -10 for pid -1 failed: 3
1137500.680:037c:0380:fixme:uiautomation:UiaRaiseAutomationPropertyChangedEvent (000000000F14BFB8, 30005, 0000000000111DD0 {VT_EMPTY}, 0000000000111DB0 {VT_BSTR: L"Critical Error Event"}): stub
1137500.680:037c:0380:fixme:uiautomation:UiaRaiseAutomationPropertyChangedEvent (000000000F1D0278, 30005, 0000000000115910 {VT_EMPTY}, 00000000001158F0 {VT_BSTR: L"Major Error Event"}): stub

Nevertheless, everything works fine. I suppose it's an AMD-specific issue.

[Plarpoon]

Yeah but it works on my Steam Deck and it has an AMD chip on it so it cannot be AMD related either... It must be something else but I cannot understand yet what

[Plarpoon]

I managed to fix it thanks to this comment written by Intelligentgaming #2143 (comment)

Installing the EA App as a non-steam application allows the game to actually be executed every single time successfully with no failures.

Ehi @kisak-valve since this issue with the EA App keeps on popping up once every so often across the years do you think it's possible to either pin that solution somewhere? It seems to be a common solution across many type of games which require a third party launcher to work.

[mackal]

Replying to #4823 (comment)

What exactly do you mean by this? I was playing perfectly fine until yesterday and I've been trying to figure out how to get it working again ... the EA App starts up and the game never ends up launching now :/ (tried a few different proton builds too)

[mackal]

I renamed my pfx folder under commondata and relaunched the game which set up the EA App etc and I can play the game again. Running a diff on the 2 folders looks like EA App ran an update in my old prefix. Maybe the update process breaks it? (but fresh install of the updated version works as expected?)

[garpu]

This is something (deleting and recreating the pfx) one has to do every few months with the EA app and Sims 4. Then again I've heard of Windows users having to reinstall the EA app when something goes wrong, too.