SunBeam wrote: ↑Tue Dec 03, 2019 4:40 am
All you do is bluntly and hardcodedly running up GRB_UPP.exe or GRB.exe. Simple as that. You didn't even bother using one .exe; no - one loader for GRB, one for GRB_UPP...
Um.. you are simply incorrect. Maybe I am misunderstanding you, but factually you are just incorrect. But it's probably because you haven't looked into it yet.
When you press PLAY in Uplay:
Game runs GRB.exe
GRB.exe checks for existence of GRB_BE.exe and if not present runs it, then closes.
GRB_BE.exe then runs the file
BEService_x64.exe
here:
C:\Program Files (x86)\Ubisoft\Ubisoft Game Launcher\games\Ghost Recon Breakpoint\BattlEye
Which dumps file here:
C:\Program Files (x86)\Common Files\BattlEye
BEService_grb.exe
then renames it to:
BEService.exe
which it then runs, which creates the system driver BEDaisy.sys and starts it
then runs the GRB.exe.
THEN the process is repeated again, with GRB.exe checking to see if GRB_BE.exe is running.
If so, then it continues the process of running.
You can't just 'start the game' by renaming GRB_BE.exe and then using a launch parameter in UPlay. Thus your statement:
"You don't need the driver anymore. The command line parameter still seems to work." is no longer valid.
You also have no idea regarding the other method being used by our project, but that's irrelevant. The launcher is doing a lot more than "bluntly running the game", and as I stated before it stops the service and driver AFTER they already were started without the game closing.
At any rate, I don't want to get into a collossal fistfight yet again, when I don't have to. If you think I am wrong or have other information or view about this, whatever. I am pretty confident in what I am writing because I have actually dealt with the update and worked out solution(s ). Maybe your experience or solution will be different.
Screw it, I'll just go ahead and post some bypasses here in a few minutes.
"Why are you here again?" <- I'm contributing.
best,
Cal