Link2ea ошибка стим

@Newbytee i was able to manually add origin into the proton prefix, still a no-go even after it then lets it skip the setup step.

@Newbytee i was able to manually add origin into the proton prefix, still a no-go even after it then lets it skip the setup step.

Were you able to get a log?

I already edited it into the OP.

I already edited it into the OP.

Ah, oops. Thank you.

Mind you people are having activation issues on Windows so I can see the extra stuff here as being a problem for Linux [Proton].

It really depends on if Valve or EA wants it working on Linux anytime soon. It will either be or it could be a long long time if ever. Time will tell.

There’s a good chance the link2ea error is due to you installing the regular variant of Origin. The Origin client shipped with Steam may have a protocol handler which handles the link2ea protocol request.

There’s a good chance the link2ea error is due to you installing the regular variant of Origin. The Origin client shipped with Steam may have a protocol handler which handles the link2ea protocol request.

This would be the Origin thin client right?

@Guy1524 true, but i’ve seen people mention on Steam they were able to just use their normal Origin install with the Steam version, as long as Origin was loaded it worked so I though that could possibly be an issue somewhere

Hopefully Valve/CodeWeavers/Wine hackers can do some testing and figure it out for sure. But until then, it’s a bust.

whats the status of Origin launcher on winedb/protondb?

you might need to run this through the .proton prefix making your own «launcher» similiar to how i have GOG and several other windows programs running through a seperate .proton pfx

whats the status of Origin launcher on winedb/protondb?

you might need to run this through the .proton prefix making your own «launcher» similiar to how i have GOG and several other windows programs running through a seperate .proton pfx

The problem with that is that with this game there’s a new communication with Origin. Nothing might work at all and older Origin hints in regards to Wine/Proton may not apply to the issue at hand.

It would be nice if Valve or EA would say specifically if it should work or not but I assume from their silence that its not supported at this time.

For the record, Lutris is now able to workaround the issue, through some scripts. Here is the official Lutris install script to set it up to play Jedi: Fallen Order on GNU/Linux : https://lutris.net/games/install/16926/view

Bought it through Origin and it’s working now with GloriousEggroll’s Proton 4.20. Can’t say if that also fixes the Steam version tho.

Has anyone tried running the game through the Windows version of Steam? I noticed that the steam client update log specifically talked about Installation support for STAR WARS Jedi: Fallen Order™.

Hi,

What does working mean exactly? Platinum level working? How’s performance?

…

Has anyone tried running the game through the Windows version of Steam? I noticed that the steam client update log specifically talked about Installation support for STAR WARS Jedi: Fallen Order™.

Seems like it was for the release on Steam (i.e. Windows), not for Steam Play.

Has anyone tried running the game through the Windows version of Steam? I noticed that the steam client update log specifically talked about Installation support for STAR WARS Jedi: Fallen Order™.

Seems like it was for the release on Steam (i.e. Windows), not for Steam Play.

I get that; I want someone to test the Windows version of steam through wine to see if this is a wine issue or a Steam Play issue.

@CuriousTommy I was able to install and launch this game via Lutris, using both Origin and Steam+Origin launchers (using the wine-jedi flavor of wine).

However, I won’t be playing until nvidia releases 441 drivers for linux as the performance is dreadful.

Ah, almost forgot to mention, this game requires Media Foundation for cut-scenes to work (#1464).

@CuriousTommy I was able to install and launch this game via Lutris, using both Origin and Steam+Origin launchers (using the wine-jedi flavor of wine).

Could you explain how you proceed to launch it with Steam+Origin launcher?

@julienbenjamin In my case, I’ve installed Steam via Lutris (I believe it’s called Wine Steam runner or something). Then linked my existing game files to the directory where Wine Steam’s game files were supposed to be (must be done before Steam starts installing the game for it to discover existing files, otherwise it just starts downloading whole game again). After I did that, I installed Star Wars and launched as usual.

Once your origin account is tied to your Star Wars game, you no longer need Steam — install Origin via Lutris, link game files like before, validate game files and you’re good to go.

Keep in mind that you’ll be limited to 5 game launches per 24 hours, as denuvo kicks in and thinks you’re on a different PC :/ . Steam’s proton somehow solves this, but Lutris and other Proton distributions don’t.

Finally, it takes some time for origin to start the game itself — in my case origin would minimize and then would immediately pop up again, but after some time the game launches. Keep this in mind as you’re limited to 5 games launches as I’ve mentioned before.

P.S. Game, might not work with ESync enabled, haven’t tested this myself, but other people keep saying this.

I have managed to run this game with GloriousEggroll’s proton 4.21 build. It’s not perfect, but at least it works for now.

These steps should work for anyone who already has Steam account tied to Origin via Wine Steam or just regular Window’s Steam:

1. Install Star Wars and get greeted by «Try relaunching your game to continue linking accounts» error when launching.
2. Launch regedit for your prefix. For ex. type
   WINEPREFIX=~/.steam/steam/steamapps/compatdata/1172380/pfx/ ~/.steam/steam/compatibilitytools.d/Proton-4.21-GE-1/dist/bin/wine64 regedit
3. Navigate to HKEY_CLASSES_ROOTlink2eashellopencommand and change default value to "C:Program Files (x86)OriginOrigin.exe"
4. Install Media Foundation workaround (normal version) manually.
5. Launching Star Wars via Steam, this will now open Origin client (Origin might not work with ESync enabled, however FSync seems to work).
6. Actually launch the game from Origin.

I have managed to run this game with GloriousEggroll’s proton 4.21 build. It’s not perfect, but at least it works for now.

These steps should work for anyone who already has Steam account tied to Origin via Wine Steam or just regular Window’s Steam:

1. Install Star Wars and get greeted by "Try relaunching your game to continue linking accounts" error when launching.

2. Launch regedit for your prefix. For ex. type
   `WINEPREFIX=~/.steam/steam/steamapps/compatdata/1172380/pfx/ ~/.steam/steam/compatibilitytools.d/Proton-4.21-GE-1/dist/bin/wine64 regedit`

3. Navigate to `HKEY_CLASSES_ROOTlink2eashellopencommand` and change default value to `"C:Program Files (x86)OriginOrigin.exe"`

4. Install Media Foundation workaround (normal version) manually.

5. Launching Star Wars via Steam, this will now open Origin client (Origin might not work with ESync enabled, however FSync seems to work).

6. Actually launch the game from Origin.

I’ve been trying to launch the game using these steps but it always crashes saying that it can’t load DirectX.
I followed the advice on the lutris wiki, but now it keep saying that there’s something wrong with my install and it won’t launch.

Ran into the same thing.

Says something wrong on install and won’t launch via Origin.

…

I have managed to run this game with GloriousEggroll’s proton 4.21 build. It’s not perfect, but at least it works for now.

These steps should work for anyone who already has Steam account tied to Origin via Wine Steam or just regular Window’s Steam:

1. Install Star Wars and get greeted by "Try relaunching your game to continue linking accounts" error when launching.

2. Launch regedit for your prefix. For ex. type
   `WINEPREFIX=~/.steam/steam/steamapps/compatdata/1172380/pfx/ ~/.steam/steam/compatibilitytools.d/Proton-4.21-GE-1/dist/bin/wine64 regedit`

3. Navigate to `HKEY_CLASSES_ROOTlink2eashellopencommand` and change default value to `"C:Program Files (x86)OriginOrigin.exe"`

4. Install Media Foundation workaround (normal version) manually.

5. Launching Star Wars via Steam, this will now open Origin client (Origin might not work with ESync enabled, however FSync seems to work).

6. Actually launch the game from Origin.

When I did that, the game didn’t show up on Origin.

You need to add non Origin game on Origin but it just says error when you
try to launch it after that.

…

Good writeup kakra. I peeked very slightly into this one time over in the dxvk issue

I can confirm that setting lower (sometimes much lower) resolutions usually works around the problem… like there’s only a few MB of mis-alignment for the memory budget as seen by the games. A full-res 4k screen buffer probably needs almost 32 MB of VRAM (if we calculate 32 bit per pixel), multiply that for double buffering or triple buffering, or whatever amount of frames the game renders ahead, let’s say this makes up to 128 MB in total. Now compare that with Full HD which only takes 32 MB for the same number of frames, so all frame buffers fit into one single 4k frame. 1024×768 would need only 12 MB of frame buffers. We need to keep in mind that fshack usually scales that up back to the native resolution, I’m not sure how this plays into the budget but it probably adds an overhead of two additional native-res frame buffers.

Each window on your desktop that is not minimized will probably also use some amount of VRAM for its intermediate render surface before the compositor renders that to the desktop, minimizing windows before running the game can thus free a lot of VRAM (almost 0.5 GB the last time I tried and measured that, browsers and Steam usually run fullscreen for me, so minimizing each one will free around 32 MB, in KDE you may need to disable window previews, other desktops may have a similar setting). But I’m not sure if all the intermediate render surfaces have to be in VRAM, YMMV. Disabling compositing can work around this because window backbuffers should be backed by sysmem then, and the CPU will compose the desktop directly to the frame buffer.

Doing all of that helps a lot for this game but it usually doesn’t completely fix it.

Origin not using 300-400 vram on it’s own would also help maybe 😁

And with Mass Effect it’s even more stupid since there origin takes up 300-400 and then the launcher takes up around the same and they both run in the background while game is running hehe. Also they both go through dxvk 🤔
But that is offtopic ofc 👀

Edit: i saw your comment in the dxvk issue about origin 👍

@Blisto91 I discovered on GOG forums that it’s possible to run the game without Origin and even without Steam, apparently the executable SwGame/Binaries/Win64/SwGame-Win64-Shipping.exe is completely DRM-free! But for me personally it didn’t help with the lags.

@Blisto91 I discovered on GOG forums that it’s possible to run the game without Origin and even without Steam, apparently the executable SwGame/Binaries/Win64/SwGame-Win64-Shipping.exe is completely DRM-free! But for me personally it didn’t help with the lags.

How up to date is that info?

How up to date is that info?

It is up to date and it works. On the same forum page you can scroll a little down to find the checksums of the DRM-free executable, and my latest executable from Steam matches them.

Maybe a stupid question, but I’m absolutely new to steam. I bought the game yesterday and it is really unstable, more than 30min play are not possible, than it crashes.
How can I play Fallen Order without origin and steam, directly over wine? Or can I set SwGame-Win64-Shipping.exe to start from steam?

Maybe a stupid question, but I’m absolutely new to steam. I bought the game yesterday and it is really unstable, more than 30min play are not possible, than it crashes. How can I play Fallen Order without origin and steam, directly over wine? Or can I set SwGame-Win64-Shipping.exe to start from steam?

Do you use Lutris or something like that?

no, steam with proton GE7.16, debian sid.

I bought the game yesterday and it is really unstable, more than 30min play are not possible, than it crashes.

Could you share your hardware info and video driver version?

How can I play Fallen Order without origin and steam, directly over wine? Or can I set SwGame-Win64-Shipping.exe to start from steam?

You can point a Wine prefix manager like Lutris or Bottles to this executable. Or just run it directly with Wine, but you’ll need to manually install DXVK in your prefix, otherwise performance will be terrible or the game won’t start at all.

  Model: "ATI Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT]"
  Vendor: pci 0x1002 "ATI Technologies Inc"
  Device: pci 0x731f "Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT]"
  SubVendor: pci 0x1da2 "Sapphire Technology Limited"
  SubDevice: pci 0xe409 
  Revision: 0xc1
  Driver: "amdgpu"
  mesa-vulkan-drivers:amd64                      22.0.3-1

I have yesterday replaced pulseaudio with pipewire, now it seems better, game not crashed yesterday evening. Would be great to get rid of origin.

Playing on the steamdeck, embedded videos stopped working (that video test screen shows now). Worked fine yesterday, not sure if the used Proton version changed.

I’m wrong. It seems like they are using different video formats for the skill videos, some work, some don’t. Got confused, cause the ones for the skills you get in the start work, while the later ones do not work.

Video problem seems gone now with the latest versions

This game doesn’t run anymore for me on latest Proton 7. It appears that it’s not even able to start Origin anymore. Can someone confirm?

EDIT: My lib32/i686 Vulkan drivers were lacking and are necessary of the Origin installer at least.

This comment has been hidden.

This game doesn’t run anymore for me on latest Proton 7. It appears that it’s not even able to start Origin anymore. Can someone confirm?

EDIT: My lib32/i686 Vulkan drivers were lacking and are necessary of the Origin installer at least.

Can confirm.Game not installable / playable with Proton 7.0.3 on Steam Deck.

Did some digging on the issue too. Had game working before just fine with rx480. «Upgraded» just few days ago to nvidia gtx1080 and issues started with origin specificly for some reason. Thou think this is not related to gpu cause i am able to launch the game with commandline with protontricks following:
protontricks -c 'WINEFSYNC=1 wine /path_where_game_installed/steamapps/common/Jedi Fallen Order/__Installer/Origin/redist/internal/OriginThinSetup.exe' 1172380

Command installs origin just fine inside 1172380-«proton bottle» and im able to login etc.

After that running the executable directly with:

protontricks -c 'VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/nvidia_icd.json DXVK_ASYNC=1 WINEFSYNC=1 wine /path_where_game_installed/steamapps/common/Jedi Fallen Order/SwGame/Binaries/Win64/SwGame-Win64-Shipping.exe' 1172380

Im able to start game directly with origin enable. But not under steam. So in short:

• Game seems to work technically just fine with origin launcher.
• Steam Install script seems to be broken atm and game fails to launch every time during pre-scripts that tries enable/install origin. Even it is installed/enabled/linked inside the bottle manually via protontricks.
• No difference for me trying between different proton versions to progress origin install process on preinstall scripts.

P.S on previous working «Steam install» with rx480 i had origin disabled by renaming igo64.dll and it caused no issues what so ever. Also non of the previous install files are anymore present as i did fresh install on game (with deleting all directories related, including bottle) with gtx 1080 upgrade.

**Got it working! ** Thanks for @troytjh comment i read after writing previous. Installed lib32-nvidia-utils (which i was missing for some reason) and game launched without issues. Apparently installer/steam/origin needs lib32 installed.

Game crashes with latest experimental (same with GE what is based on that) — 7.0-3 seems to work. Origin seems to crash and so to entire process. Seems Origin compatibility is regressed with experimental now?

Hello @spaghetticodez, please add PROTON_LOG=1 %command% to the game’s launch options, reproduce the crash, 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.

The game stopped working for me. It was working great last week and when I tried today, it just stop during launch. I think it’s a problem with Origin since Burnout Paradise Remastered and Need for Speed Most Wanted are not working either.
I tried 7.0-4 and axperimental and it’s the same.

If I add PROTON_USE_WINED3D=1 the game launches, even if it runs like crap, as expected. It is very strange. Is it a Vulkan issue?

It also worked for NFS Most Wanted but not for Burnout Paradise Remastered.

Opting out of the steam client beta solved the problem.

It also worked for NFS Most Wanted but not for Burnout Paradise Remastered.

In my experience Burnout Paradise Remastered is broken even on Windows.

For Burnout Paradise, I noticed that it wasn’t associated with any Proton version. When I was on the game page and unfold the information part, there wasn’t a «Run on this computer via Steam Play…». So I forced a version of Proton and it works great. And I unchecked the specific version of Proton and now, it is associated with the default one. Anyway, Burnout Paradise Remastered works great on linux.

Opting out of the steam client beta solved the problem.

THIS IS IT! I was opted into the beta and for some reason that keeps Origin from launching with Vulkan. You could bypass this by using WINED3D, but in the case of Mirror’s Edge Catalyst, the shaders were all messed up and every time you’d boot the game, the colors would be radically different from intended. Opting out of the beta allows Origin to boot using Vulkan and everything works good!

Anyone else having issues with controller detection in this game? I’m using an Xbox Series controller and the game just won’t detect it like it should. This seems to be an issue with all EA games right now and is more than likely caused by the EA app running in the background

more

Weird one but have you tried alt tabbing out and back into the game? I found that sometimes kicks it into line

more

I’ve tried that and while the controller does do something in game (I’m able to look around with the right joystick), Steam input doesn’t seem to be loading the correct controller configurations for the game

For me, the game just won’t launch. I get «something went wrong» asks me to relink the account or something in the st*pid EA App but no way of doing it, i can only close the window and then the game quits. Tried several Proton versions to no avail. Anyone has a fix?

after installing, it pops up like this and i just cannot run the game.

Here’s a log in case somebody can help:

steam-1172380.log.zip