So:
1) I removed the
-eac_launcher from Steam command line. Re-created the shortcut, so all is stored. Now, when attempting to run the game from the newly re-created Desktop shortcut, I get this:
2) Went into the UPlay launcher to set the parameters:
Hit 'Play'; still got error above.
3) Went to game folder and manually created a Desktop shortcut. To which I then manually set the
-eac_launcher parameter.
Ran the game from my manually created shortcut. Since I have the Steam version, I got this upon launching:
So I clicked OK. And the result:
Conclusion:
a) Using
-eac_launcher as launch parameter directly in the UPlay client doesn't work.
b) Using
-eac_launcher as launch parameter directly in the Steam client does work.
c) Regardless of UPlay or Steam launchers, if you manually set the launch parameter to the manually crated shortcut on the Desktop (see 3), that should BYPASS everything.
And that, #3, is pure simple executable logic and knowing those command line arguments are passed to it and are not depending on some game client. It's Windows 101 common sense/knowledge.
Can we now evolve from the monkey status? Thanks.