How Do I add the BattleEye Launcher to Legion’s launch arguments?
I have to do it that way because, after a PC crash, Legion REFUSES to run unless I run it in dx11 mode. It just shows a black screen without ‘-dx11’ in the command line.
So when trying to launch Legion via WeMod, I ALSO get the black screen. 
Which means I have to add BattleEye to the launch arguments to run WeMod AFTER I boot up Legion.
But how?
Yeah I hear you. The game will not start for me start unless I put in -dx11 in the box. Anything else the game will either crash or not start at all. In the last game it was a lot easier to bypass battleye.
Bypass instructions(command) are in the trainer notes.
I kept -dx11 in the arguments and tried to launch the game through wemod by pressing play in wemod. Within 15 or 20 seconds I saw the watchdogs splash screen for about a second then got the message from wemod saying “we are having trouble starting or finding your opened game”
They are not, unless I’m being very stupid (which is always a possibility.)
My notes just say ‘You must add BattlEyeLauncher to the game’s launch arguments’. They don’t say how to do that, though.
You do it the same way you added the dx11 flag.
Thank you…and I see now that it says ‘-BattlEyeLauncher’. I totally missed the hyphen the last 10 times I looked at it.
It was, as you said, telling me exactly what to add. My bad.
And also it’s at the top of this page second comment too
Ah well. Darn for me; I can’t fix the black screen bug, so I can’t launch through WeMod, and even after adding -BattlEyeLauncher to the game’s launch options, the trainer will not work if launched after the game itself.
The game won’t launch for me unless -dx11 is in the arguments. Can you add both -dx11 and -BattlEyeLauncher in the arguments? Will it work that way??
We just added -dx11 to the launch arguments for both trainers 
It works! Thank you! 
So with the new trainer update can I not play the game in DX12? It seems it always reverts me to DX11 when I launch through WeMod.
You will need to launch the game through uplay with the flag to disable battleye.
Yep. Got it working. Gotta have that Ray Tracing ya know.
game just got updated
Yeah, the game recently got an update but it still seems to work for me. On that note, I assume it’s the -dx11 tag that keeps making my game launch in DirectX 11 mode? I keep needing to revert it (and my ray tracing settings) back to dx12 after launch.
Edit - There seems to be an issue exiting the game whilst using the trainer. When I click to ‘Exit to main menu’ the game gets stuck on the autosaving stage. This requires an alt-f4 closure, resulting in the loss of around half an hours worth of gameplay.
Is it possible to have the -dx11 parameter be optional launching via WeMod? It more than quadruples the load time on my SSD, not to mention disabling ray tracing support for those who use it.
There seems to be an issue exiting the game whilst using the trainer. When I click to ‘Exit to main menu’ the game gets stuck on the autosaving stage. This requires an alt-f4 closure, resulting in the loss of around half an hours worth of gameplay.
This is a known bug with the game even without the trainer. Patch 1.05 was supposed to fix it but has not. If you leave your game at the auto-saving stage for 15-20 minutes it eventually saves and exits. I’d check the Ubi forums for updates on that bug.
Thanks for the heads up, I realised you’re right.
I hadn’t had the issue personally until after the update, and even the saving did work when I tried it in my tests earlier. It’s just a coincidence it was without using the trainer, because as you mentioned it doesn’t actually have an effect on the saving issue.