Forum Discussion

New Rookie

Re: Command line arguments not working with EA Play version

I'm reviving it because this is still an issue. It worked perfectly fine with Origin but now that we have EA app it does not.

I can't say much about Steam - I've heard it also doesn't work - but I made some tests with EA app.

If you set the command line args in EA app and run the game from EA app - it works. The game gets the command line args.

If you set the command line args in EA app and run the game from a shortcut or by opening the game exe - it doesn't work, no matter if EA app is running or not before starting the game.

And finally, if you set the command line args in a shortcut - it never works.

So please, fix it, it's really annoying.

Some technical info - when you start the game from a shortcut with some parameters, the game runs Origin or EA app by opening this:

origin2://game/launch/?offerIds=<some IDs>&cmdParams=<command line parameters>

The program that opens "origin2://" protocol is defined in a registry key: "HKEY_CLASSES_ROOT\origin2\shell\open\command".

For Origin - the program is "Origin.exe", so the main app.

For EA app - it's set to "EALauncher.exe", which in turns runs "EALaunchHelper.exe" (still with that "origin2://" info as the first parameter), which in turns run "EADesktop.exe" (without that "origin2://" info). So clearly there's a problem with communication between "EALaunchHelper.exe" and "EADesktop.exe".

8 Replies

crinrict
Hero+
3 years ago
@anadius1 yes, this is a known issue. There's a discussion here about the shortcut issue here: https://answers.ea.com/t5/Technical-Issues-PC/Please-someone-tell-me-how-to-DLC-s-on-off-setting-in-EA-app/m-p/11921732
anadius1
New Rookie
3 years ago
@crinrict Doesn't really help that the other one is marked as "Solved". I'll probably make a workaround and post on MTS before EA does anything about it. -_- It will use args from a shortcut, not those set in EA app, but at least it will work.
crinrict
Hero+
3 years ago
@anadius1 EA knows about it and it's a different issue as the one in this thread though.

It was marked as solved by OP and they posted in the EA app forum I believe.
SimQARobo
EA Staff
3 years ago
Hello @anadius1

What version number of EA App are you using?

Also, what arguments are you using?

When I launched the game through shortcut with arguments in EA App, the arguments worked for me. I tried the -w and -disablepacks arguments, and am using EA App version 12.56.0.
anadius1
New Rookie
3 years ago
Hello @SimQARobo

When I posted on Sunday I had version 12.50.0. Today EA app updated to 12.56.0 and the game consistently starts with the arguments set in EA app. Doesn't matter if I start from EA app, exe file or a shortcut. Doesn't matter if EA app is running before I start the game or not. So that's good, one thing fixed. (I did my tests with -w and -nointro but it doesn't matter - if it works with those it works with others too.)

But arguments set in shortcut properties are still ignored. So if I want to have two shortcuts, one that disables packs, one that doesn't - I can't have that. I have to edit arguments in EA app each time I want to switch.

And I still don't know if arguments set in Steam settings work or not. I assume they don't.
crinrict
Hero+
3 years ago
@anadius1 Do you still have origin installed too ? Do the shortcut arguments work with that (I know they used to when I tested a while back but to make sure it still does)
anadius1
New Rookie
3 years ago
@crinrict No, I have EA app. I believe Origin got automatically uninstalled when I installed EA app.
crinrict
Hero+
3 years ago
@anadius1 Yes, it does but you can still reinstall Origin (for the time being)

Will try with Origin later today. Still have them both :D

EDIT: Tested Origin and that still seems to work with the short cut. I just tried -w for sake of easiness