Boaderless gaming window wont close

[wolfenstein0099]

Im using an AHK script to run Target Bravo on Teknoparriot in full screen with boaderless gaming. There is a patch but cant use it because my monitor is ultra wide 3440 x 1440. 

 

This is the script im using... 

#SingleInstance Force

Run, "C:\Program Files (x86)\Borderless Gaming\BorderlessGaming.exe""

Sleep, 1000
Run, C:\Users\Wolfe\Documents\TeknoParrotUi.exe --profile=TargetBravo.xml

~Esc::
     Process,Close,TeknoParrotUi.exe
    Run,taskkill /im "TeknoParrotUi.exe" /F 
    Process,Close,BorderlessGaming.exe
    Run,taskkill /im "BorderlessGaming.exe" /F
return

 

I even tried to add...

 

$Esc::
{
    Process, Close, {{{StartupEXE}}}
}

Didn't work either. 

 

So im loading off the AHK everything boots like it should but when I exit the game even In bigbox mode with close active window. The window of boaderless gaming is still open. Not sure how ro close it when the game exits. Ill post a Pic of my window. 

 

Thank you 

 

[JoeViking245]

Process, Close, {{{StartupEXE}}}  won't work in your script because (I'm pretty sure) {{{StartupEXE}}} is a LaunchBox parameter (vs. an actual AHK parameter).

In your original script, you may try replacing ~Esc with $Esc

[wolfenstein0099]

45 minutes ago, JoeViking245 said:

Process, Close, {{{StartupEXE}}}  won't work in your script because (I'm pretty sure) {{{StartupEXE}}} is a LaunchBox parameter (vs. an actual AHK parameter).

In your original script, you may try replacing ~Esc with $Esc

Thanks for trying Joe. Didnt close the window and gave me an error on exit. 

[JoeViking245]

Can you share what the error was?

[Jayinem]

Why do you want to close Borderless Gaming? I just leave it as a tray icon and start it with Windows you can even hide it but then again I use it for a lot more than just one game. It's not like it's taking up a lot of RAM. 

[wolfenstein0099]

10 hours ago, JoeViking245 said:

Can you share what the error was?

Sure thing. 

 

Sorry for the wait. 

[JoeViking245]

That's not an AutoHotkey error.  So the $ change wouldn't have caused that.  Doesn't look like a LaunchBox error. Which leaves us with a TP or BorderlessGaming error.  

? maybe one or the other was still running in the background and you ran the script [again]? ? (speculating)

[wolfenstein0099]

49 minutes ago, JoeViking245 said:

That's not an AutoHotkey error.  So the $ change wouldn't have caused that.  Doesn't look like a LaunchBox error. Which leaves us with a TP or BorderlessGaming error.  

? maybe one or the other was still running in the background and you ran the script [again]? ? (speculating)

Thanks Joe. 

 

Nope. Just turned my pc this morning and ran it once from Launchbox. 

[JoeViking245]

2 minutes ago, wolfenstein0099 said:

Nope. Just turned my pc this morning and ran it once from Launchbox. 

And if you revert the $ change, does that error not come up? (granted, when exiting the game, BorderlessGaming (BG) still wouldn't close)  And if doesn't come up after reverting, (manually close BG and...) change it back to a $ to confirm (or not), that indeed what's causing the error. (then back-and-forth again for a triple/quadruple confirmation). aka: absolute process-of-elimination.

 

Some thoughts:

• Run the script from outside of LaunchBox to eliminate LB as the issue (which I'm doubting it is).
• Make sure not to have both Esc sequences in the script at the same time.
• The "return" at the end of the escape sequence shouldn't be necessary
  • It may be keeping the script open/running after escaping/exiting the game
  • Though may not be an issue when using SingleInstance Force
    • There's no need to have it continue to run. However harmless.
• Maybe create (and test) a script that starts BG, pauses 5 seconds or so, and then [attempts] to close BG to confirm that it's even possible with the methods used.

  • Run, "C:\Program Files (x86)\Borderless Gaming\BorderlessGaming.exe"
    Sleep, 5000
    Process, Close, BorderlessGaming.exe
    MsgBox Borderless Gaming should be closed now

    (when copying/pasting that 1st line, noticed you have 2 double-quotes at the end of the line. Removed one of them in my example)

• If Process, Close doesn't work, then try it with the Run, TaskKill... line.  Don't need both of them in there. Only the one-that-works.  

[wolfenstein0099]

1 hour ago, JoeViking245 said:

And if you revert the $ change, does that error not come up? (granted, when exiting the game, BorderlessGaming (BG) still wouldn't close)  And if doesn't come up after reverting, (manually close BG and...) change it back to a $ to confirm (or not), that indeed what's causing the error. (then back-and-forth again for a triple/quadruple confirmation). aka: absolute process-of-elimination.

 

Some thoughts:

• Run the script from outside of LaunchBox to eliminate LB as the issue (which I'm doubting it is).
• Make sure not to have both Esc sequences in the script at the same time.
• The "return" at the end of the escape sequence shouldn't be necessary
  • It may be keeping the script open/running after escaping/exiting the game
  • Though may not be an issue when using SingleInstance Force
    • There's no need to have it continue to run. However harmless.
• Maybe create (and test) a script that starts BG, pauses 5 seconds or so, and then [attempts] to close BG to confirm that it's even possible with the methods used.

  • Run, "C:\Program Files (x86)\Borderless Gaming\BorderlessGaming.exe"
    Sleep, 5000
    Process, Close, BorderlessGaming.exe
    MsgBox Borderless Gaming should be closed now

    (when copying/pasting that 1st line, noticed you have 2 double-quotes at the end of the line. Removed one of them in my example)

• If Process, Close doesn't work, then try it with the Run, TaskKill... line.  Don't need both of them in there. Only the one-that-works.  

Thank you so much my friend. Your awesome. 

 

If I revert it back to ~. No error at all. Ive booted it from the folder out of launchbox with the script and when I exit. The window is still there. 

 

Ill try yoyr suggestions. Also could just try running it when windows starts and in the taskbar and see what happens without the script. I could just use the xml in launchbox with it running all the time. I guess I'll try both. Its the only game right now that im using it with. 

 

I know this is off my topic Joe. I seem to have problems witn my steam account even though its linked. I cant add games or launch either, only stram. From what I've seen on older posts. Looks like a steam issue from The way they keep chagging the way things are handled on their end. 

 

Thanks again for everything