CoinTos

@ashramrak Removed 5 second sleep timer as it is not needed if splash is disabled and added check for the Big Box splash screen. If found, it will wait till it to finishes before starting main monitoring loop to prevent WinNotExist detection bug between the time it takes the splash screen to close and big box main interface to start. This will also optimized the script and prevent unnecessary delay due to my last solution as I forgot you can disable the splash screen so that 5 second sleep could cause problems down the road to those that disabled it.

Depends on what you are comparing it to. As far as compared to the 1.0 version of ashramrak: All irrelavent code from the steam autohotkey script he modified has been removed. An updater check was written by me to make sure if the installer was running Kodi wouldn't be relaunched as BigBox will be restarted once the install completes. The script was written to remove GOTO calls and to make understanding flow easier. A clean up check to make sure Big Box was closed after Kodi brought back to focus by the script. Was commented to help those learning/editing/recompiling the autohotkey script know what or where they might want to modified for their own setups. The big plus of this was to get a uniform plugin that both ashramrak and I will support. @ashramrak maybe you should submit it to the downloads for third party plugins and we will break from this thread and support it under it's newly create thread to save confusion.

Agreed and that was basically the point I was trying to make. It's hard to be in the middle as an army of one (Jason) and trying to make everything make sense or support both side at the same time. I was just trying to show the point from the other prospective of it. Hopefully, it was in an appropriate as possbile way to support development and support patience.

Everything is tested on an i3 system with a solid state drive running Kodi 16.1. So if there are bugs outside of that system I can modify as needed but this script is rewritten to account for slower systems and faster system should not be affected.

You can't really pick on that Voice recognition, I as well, have no use for it but he stated in his feature video for it that he was working it long before launchbox and good on him for finally putting it to use. Now back to your statement about you following the changelog for Launchbox vs BigBox. I am the otherside of the coin I support the BigBox side of the changelog as I use a 10ft approach and only use the launchbox app for scraping. Jason has the double edge knife problem of supporting both you and I in his development. If optimization is the course required currently, I think we should let the few features slide on either side and both support/follow the performance side for the time being as that seems to be the appoarch he is taking. Features are nice but it running well on all systems is key in both modes, that is really key in the end.

Ok so here is a very small bugfix update... my bad. Under random starts of the script, it would detect the bigbox window as not existing break the monitoring loop. This was caused by it getting to the monitoring loop too quickly. I thought I had had this squashed with the 2 second sleep timer before the loop but that wasn't enough time apparently. So this version has it set to 5 seconds and it appears the problem is now solved as I can no longer recreate it on my setup.

I know all to well the busy at work part, finally got a day off to write that ahk but for now, you can remain 'project lead' and I will just forward on my modification and bugfixes as I really don't feel like maintaining a Kodi package at the moment. If you lose interest, I will then repackage but for the time being, the extra set of eyes is beneficial.

As promised, here is the ahk script source and compiled exe as I heavily modified the script. Everything that doesn't relate to BigBox has been removed and an update check has been added so you can use the bigbox updater without being kick back to Kodi when the installer launches. I also commented it but that is just out of habit. Let me know what you think.

No worries, in a couple days I'll clean it up and post a heavily modified version that is tailor more to BigBox for you to look over.

One more small correction you may want to check as I forgot to include it in file. In the process exist ErrorLevel block before you 'Send {Esc}' you have WinWait, you probably want to use WinWaitActive as you mostly don't want to send escape till the window is truely in focus. Now, this is just out of curiousity but why the need to send escape if the process and window already exists and have been brought to focus?

I can confirm the same result as FoxyMonty, seem to start after the latest updates to LaunchBox/BigBox. Seems like it could be hanging or looping past on the exit detection of BigBox as the LaunchBoxLauncher-AHK.exe doesn't exit now but that is just a guess as I won't be able to debug the script till later tonight. Edit: So I got time to look at the ahk source and the issue lies with line 58 and the WinWait, it appears to hang there because of the 'LaunchBox' in front ahk_exe BigBox.exe, removing the labels allows the script to continue as expected. See attached ahk with all LaunchBox labels removed.

Works in Launchbox but not Big Box.

Ok so that link provided by DOS76 (thanks) did install a bunch of DirectX updates but still no device listed in Big Box.

OK, so that was a strike out on downloads. But according to my Nvidia control panel under help -> system information, I have the DirectX 12.0 runtime installed. So I am going to assume that is the latest because I can't find any other Microsoft downloads after 9.0c runtime and the july 2010 runtime update, both of those don't install in windows 10.

Yeah, I don't have that checked, I am running Windows 10 Pro so I am pretty sure my DirectX is all up-to-date.

Thanks for the reply. I am going to go with I believe so. So while in Big Box, I go to Options and under Controllers I have checked Enable Game Controllers but unlike when I used my xbox 360 controller there is nothing listed under Device: . Did I miss something?

Hi, I can't seem to get Big Box to detect my Bliss-box 4Play controllers but Launchbox has each of them in the drop down menu and works so I am at a loss. Is it a minor detection bug or something I am doing wrong in Big Box mode? Any ideas?