skizzosjt

I don't really use EA often at all. I have two games on it, which are actually Steam games but it still launches the EA launcher too (boy that is a pet peeve of mine - only one launcher, please lol) Last game I would have played a few times was Star Wars Jedi Knight (over a year ago) and I don't ever recall the EA launcher popping back up after exiting the game. I had to update the launcher to test this and it def does pop back up every time I exit a game now. So seems like new behavior for their latest app version. yea def can launch these games directly, but same here, the launcher window is restored at game exit each time. @Bucky can you also try using AHK to close the EA launcher? create another script with just a single line to close this window. put it on your desktop and double click it to run it from there. if this doesn't close the window then we know something def going on on your end preventing it from working WinClose, ahk_exe EADesktop.exe that pop up about needing admin privileges is suspicious but from what I can tell it's doing that to the game, not the launcher. AHK cannot close apps/windows that have admin privileges unless the script is also launched with admin privileges. but we're only using AHK to close the launcher rather than the game. if still not working, as a last ditch effort you can try making the script run with admin privileges but this opens another can of worms because you would need to always click yes on the UAC prompt to allow the script to use admin privileges so not exactly fully automated Here is the instructions from AHK docs. you just add this at start of a script https://www.autohotkey.com/docs/v1/lib/Run.htm#RunAs full_command_line := DllCall("GetCommandLine", "str") if not (A_IsAdmin or RegExMatch(full_command_line, " /restart(?!\S)")) { try { if A_IsCompiled Run *RunAs "%A_ScriptFullPath%" /restart else Run *RunAs "%A_AhkPath%" /restart "%A_ScriptFullPath%" } ExitApp } WinClose, ahk_exe EADesktop.exe

with both displays hooked up try and play the videos from Windows Explorer but make sure the videos are opening up on the 4K TV (rather than the 1080p one). takes Big Box out of the equation. do they "glitch" when played? if so then have just the 4K TV hooked up and try and play the videos from Window Explorer, still a problem? if so, that TV, its settings, or cable is the culprit.

Dolphin shouldn't flash any other window at boot of a game. maybe missing some launch param. are you using "-b" for batch? that would launch the game without the actual Dolphin interface window with your list of games and such. it would only launch the actual game window with that param

sorry that one is on me. clearly did NOT double check my work 🤦‍♂️ I left a line out and flip flopped the intended command. I did the following: Run the storefront launcher, wait for launcher to exist, run the game, wait for game to exist, wait for the launcher to close....lol makes no sense here is what I intended to do: Run the storefront launcher, wait for launcher to exist, run the game, wait for game to exist, wait for game to not exist, close the launcher. Run, "C:\Program Files\Electronic Arts\EA Desktop\EA Desktop\EADesktop.exe" WinWait, ahk_exe EADesktop.exe Run, "C:\Program Files\EA Games\Mass Effect\Binaries\MassEffect.exe" WinWait, ahk_exe MassEffect.exe WinWaitClose, ahk_exe MassEffect.exe WinClose, ahk_exe EADesktop.exe ExitApp Back at my main PC now and I do have the EA launcher on there. I tested out both of these commands, WinClose and Process, Close, they both work closing EADesktop.exe. So with that said, best to use the WinClose option since it's proven to work and the standard graceful way of closing a window or app

Run, "C:\Program Files\Electronic Arts\EA Desktop\EA Desktop\EADesktop.exe" WinWait, ahk_exe EADesktop.exe Run, "C:\Program Files\EA Games\Mass Effect\Binaries\MassEffect.exe" WinWait, ahk_exe MassEffect.exe WinWaitClose, ahk_exe EADesktop.exe ExitApp this is how I would do it. give this a shot and let us know how it goes! tip on why those didn't work for ya. I would assume the script is closing the game within nanoseconds after opening it Run, "C:\Program Files\EA Games\Mass Effect\Binaries\MassEffect.exe" WinClose, MassEffect.exe that runs the game, and the very next line is closing it. (edit: actually it would not close it cause I just noticed it's missing the ahk_exe part) when you use WinClose to refer to a process you need to use proper AHK criteria syntax. since it's a process it's "ahk_exe". you'll notice my suggestion uses these if you really want to learn some stuff thumb around in the AHK docs page. it helped me a lot. you can find stuff through their content or index tree or search keywords. https://www.autohotkey.com/docs/v1/ https://www.autohotkey.com/docs/v1/lib/WinClose.htm https://www.autohotkey.com/docs/v1/misc/WinTitle.htm

my bet is EADesktop.exe has a buttload of child processes and it isn't closing the main parent one. you should not be using Process, Close unless the standard WinClose command isn't getting the job done. going off JoeViking245's point that Process, Close is a forceful method. it's the same as pressing ALT+F4 or pulling the plug right out of the socket lol using WinClose will close the window, closing all relevant matching processes. Process, Close is only going to close the FIRST process it finds that matches whatever criteria it is looking for.

I recommend to be creating a profile in shaderglass. The github and manual included (same as all notes on the github) give excellent documentation on how to use and troubleshoot. No surprise chatgpt sucks and spits out a non working script. A script should be formatted something like this. launch shaderglass fullscreen and load a specific profile, wait for the game/emulator, wait for it to close, close shaderglass. Run, D:\Utilities\ShaderGlass\shaderglass.exe -f D:\Utilities\ShaderGlass\Profiles\RA_MB_TV2_16-9.sgp WinWait, ahk_exe xemu.exe WinWaitClose, ahk_exe xemu.exe WinClose, ahk_exe shaderglass.exe

yes WinHide, ahk_class Shell_TrayWnd to show it WinShow, ahk_class Shell_TrayWnd to have it hide at boot setup task scheduler to run the script at boot. for what it is worth, I do not know why, but every single time I exit Big Box when the task bar is hidden it magically reappears as if the WinShow line ran and it is def not because of any script. I can only assume Big Box is doing that also fair warning, I also have a hotkey setup to hide and show the task bar. otherwise it can be a pain when you find yourself with no way to get it to show again without logging out or restarting. you can push the Windows key to make parts of it show but it goes away again. point being, I would recommend having said script have a hotkey for those actions too. also best way in my opinion to launch Steam silently is to use the native option with Steam's settings to launch Steam at boot of OS. it is auto minimized (hidden) to the tray. this way when you launch games the client window continues to stay hidden and you never see that advertisement window either.

This can be handled with AHK. Shutdown if idle more than X. For ex, this uses 5 mins, adjust to your liking. Slip it into LaunchBox Startup Apps and set it to run only when Big Box launches Loop { If (A_TimeIdle >= 300000) Shutdown, 8 Process, Exist, BigBox.exe If (ErrorLevel = 0) ExitApp } FYI this was tested with attract mode running. Artificial inputs from Big Box have no impact on the built in AHK var A_TimeIdle and script works as intended Edit.....I re-read your comment and seems vague now lol. Did you mean to shutdown the PC or "shutdown" (close) Big Box and PC stays on?

importing through a wizard automatically changes the platform's "game" path to that directory.......it's a beyond annoying feature!

glad it worked! I was gonna eat my own shoe if you still had the problem! 😂 so that implies you tried it with v2.X ? that's normal. V2 changed, for the better, but most scripts written in V1 syntax aren't going to work in V2 and vise versa. syntax changed and then some, in V2 they made a big push to have as much as possible expression based along with many other changes. Link here to bring the point home how much changed, it's a pretty long list! https://www.autohotkey.com/docs/v2/v2-changes.htm but you shouldn't worry about that. anything you are already using was written in V1 and going to the most recent release of V1 is OK. your current/old scripts will continue to work as they have been despite swapping out the AHK exe file LB included.

d00d! do0o0o0o0o0o0o0o0d! having an eureka moment! Started thinking about the fact you're using the AHK version included with LaunchBox. One of the very first scripts I wrote years ago had an issue when I first started using LB. It was the other way around though, I wrote a script on a really old version of V1 and it worked fine with that version.....but LB had a newer version and it impacted the scripts behavior negatively. I had to change syntax since they changed it between those versions. this time around I'm using a more recent release of V1 I just tried running the script with LB's AHK file, which is v1.1.24.03 and is pretty darn old relatively speaking in AHK world. Also is the 32bit version and I always use the 64bit version THERE IS DIFFERENT BEHAVIOR BETWEEN AHK VERSIONS! I'm betting on THAT is the root cause here! I can recreate same error that being the file is read, but I cannot get the qty of entries in the array due to it seems the count method isn't working! As I wondered with the above troubleshooting version, I can even read the array, but something not working right with the Count() method (I called it a function in other posts but it's really a "method"). I get a null value and infinite loop just like you do when trying to use it to determine number of values in the array! Value is null using the AHK exe included with LB yet here I am running a much more recent version of AHK V1 and it works fine! lets check if 32bit matters at all......NOPE! Get your hands on the latest version of AHK V1. Even I am not on the latest but should be. The last release for V1 was like a year ago. V2 was in limbo for many years and they finally pulled the trigger on making it the official release version at that time about a year ago. So V1 is actually deprecated now but it's been around for so long that most basic users aren't going to make the switch. so for ex I have this working fine when using v1.1.36.02 I just downloaded the last official release of V1 which is v1.1.37.02 and also works fine! Each time I try and run it with the one included with LB is the only time the script doesn't work correctly! You will need to download a newer version from their site. You can then replace the exe included with LB with the one you downloaded Showing this so you don't think I'm just linking you to some rando website Got to autohotkey.com and Click the green download button Click other versions Click AHK V1.1 Sort by date and pick the circled zip version of the latest release. The zip version is a portable version. You can simply unpack this archive anywhere and AHK is set to jet right away. Go into that folder and copy AutoHotkeyU64.exe to where LB stores its AHK exe. (\LaunchBox\ThirdParty\AutoHotkey) Be sure to rename the file to the same name inside the LaunchBox folder. ie rename the exe you just pasted in there from AutoHotkeyU64.exe to AutoHotkey.exe I also pointed to the exe version should you want that. this one goes through the typical setup wizard process if that is more to your liking. Adding it to start menu and Windows Programs and App list, right click context menu and the like, etc etc official program stuff. I think I'll advocate to the dev team to not be several years behind on their AHK version lmao! They are using a version released in 2017 that's before I even started using LB let alone AHK! 🤦‍♂️ Gotta get with the times! I went digging in their change log and it all makes so much sense now! this method didn't even EXIST until a later version! Of course it won't work in some version from 2017, gotta have this version from 2018 or newer to use .Count() I assumed I was going to find some bug fix report in here for the count method rather than it wasn't even introduced until a later version, but boy I'm glad I found this info here! I go nuts not knowing the "why" of things! The dots are now fully connected!

no problem and your welcome! but we're not quite out of the woods yet, hold the thanks until then......we will get there. I'm determined lol ok this is all excellent info but......not good.....I'm at a point of 'da fuck is going on here? 😕 it's reading the file (good), but does not seem to be pushing these values into the array (bad)......weird situation. I'm no programmer and don't understand what challenge is on your side, bare with me as we stumble through this together. Very frustrating since the script works for me, this specific issue isn't making sense why it would show up on one person's system but not another's. I'm adding some more stuff to try and troubleshoot. After the 3rd message box I've got #3B right after it. Right before this, the value is pushed into the array. So, by theory reading that array position right afterwards should let us see the exact same value. For ex If it's blank like this (notice no "Dolphin" or whatever value it was supposed to add to the array) there is some problem going on I cannot identify yet this will repeat for the PCSX2 and Xemu lines like last time The last message box will have more text. Even if the array count is null maybe something weird is going on with just the count function. This also reads the array's first three entries regardless. So we want to see stuff here for ex Please try this version of the script out AFTER trying the above version to see what happens....THEN please do this edit to the above script. Simply replace line #6 with this line below. All we're doing here is adding "Global" in front of declaring the array. Global WindowCastListArray := [] After making that edit try and run the script again and see if behavior changes! Fingers crossed! 🤞 For transparency. The first test is to see if the values in the array can be read prior to leaving the loop where they are being pushed into said array but still cannot be read outside the loop. The second test is to see if making the array a global variable will allow it to be read at all other points in the script