CoinTos

@FoxyMonty No problem, if it is still happening to you then it might be something I need to check in the relaunching portion with the portable option enabled. Haven't done too much testing with portable version as I really don't use it so might be something I need setup and dig deeper into.

Kodi addon for LaunchBox version 1.5.1 released! CHANGES in 1.5.1: - Added override option for Kodi detection KNOWN ISSUES: - The upgrade support in this addon's Autohotkey script will not work properly with the auto download background option for LaunchBox enabled. Current workaround is to remove the check mark from the "Automatically Download Updates in the Background" box in LaunchBox's Options under the Updates section.

No problem, I will add an override option to the advance tap shortly for you. The setting you speak of was originally there like steam launcher but was removed to allow UWA support (Windows Store version) as the Autohotkey script was written to detect the Kodi path on launch. Also, if you get a chance, please PM or reply here with your Kodi version, I am curious if something has changed in Kodi that I should address in the path detection. Thanks.

Kodi addon for LaunchBox version 1.5 released! BIG CHANGES in 1.5.0: - THIS KODI ADDON NO LONGER INCLUDES A COMPILED AUTOHOTKEY SCRIPT (LaunchBoxLauncher-AHK.exe). Why you ask, since this Kodi addon requires Launchbox to be useful and LaunchBox itself is required to include the AutoHotkey.exe separately to comply with the GPL license. There is no need for a compiled script. Instead, once you set your LaunchBox directory ( eg. C:\Users\<username>\LaunchBox\) in the addon settings, it will use LaunchBox's included AutoHotkey.exe to run the needed ahk helper script. This also allow better compliance with Kodi submission rules in the future for their repository, which is something that will be considered once LaunchBox run on other operating systems. Bugfixes in 1.5.0: - fixed idle shutdown timer issue shutting down users using the minimize option with the idle shutdown timer in kodi set in power savings system settings.

Yeah, for the time being just add the 'exit 0' to tell my ahk script that there was no errors it should be concerned with and ran as intended. I will release an update shortly which will better address these kind of errors.

@psychofaktory Looks like it might be your batch script is not exiting cleanly and triggers the the ErrorLevel check in the pre/post script runs but to make sure can you create a simple batch file with the following: If that works then I will update the ahk script to log errors like that to a log file instead, remove the pop up and also change the error message as at the time I wasn't thinking about programs exit codes changing batch files exit codes but if it ran the batch file or not. my bad on that.

@psychofaktory Sounds like something messed in my ahk script triggering the error handling response. I will check it later today and get back to you.

@viclovin I responded to your pm as well. This addon requires both Kodi and LaunchBox on the same device so currently the addon is set to only install on Kodi for Windows devices due to LaunchBox being a windows only application and will throw an install error on unsupported platforms (mac, linux, android). The developer is looking into android as the next platform LaunchBox will run on and when that happens this Kodi addon will be updated to support it.

The only downside is Jason would have to come up with a way to change the startup delay to match what is required for the randomly selected video to try and prevent looping, that will be a fun chore.

Hi tdancetv2, I see you referencing what appears to be an android app so make sure you can complete everything on this installation checklist below before you purchase BigBox to make sure the Kodi addon for LaunchBox applies to your setup. Installation Checklist: 1. You are running Kodi for Windows (version 16, 17 or Windows Store). 2. You have Launchbox installed on the same Windows box you have Kodi installed on. 3. You have purchased LaunchBox Premium and placed the License.xml in the LaunchBox application folder. 4. You have added roms, etc to LaunchBox for use in BigBox. 5. You have downloaded the Kodi addon for LaunchBox zip from above file link in the first post to the Windows computer running both Kodi and LaunchBox. 6. You have installed the addon using the 'Install from zip' option in Kodi's Addons. 7. You have configured the addon settings and set the BigBox executable location, BigBox.exe file ls located in the folder where you installed LaunchBox. 8. You have configured any other addon settings that apply to your setup. 9. You can now launch BigBox from Kodi. If step 1 and 2 are not possible then this addon isn't what you are looking for.

Holy, what an update that was... amazing work as always @viking. Thanks.

You need %1 to pass the variable that LaunchBox passed to the batch script to tell the emulator what to load. Or you can also use the set command if you prefer that method.

If you like, post the batch script and I will take a look at it. I am guessing you are using LaunchBox to launch the batch script in place of the actual emulator executable. Flow is basically: -> launch game in LaunchBox -> LaunchBox passes the rom filename and path to batch script -> batch script launches joytokey with profile -> batch scrtipt launches emulator with passed rom filename and path You are then running into trouble getting the emulator actually running the passed filename and path from LaunchBox when launched from the batch script, correct?

Well that back fired nicely, I submitted my latest update (1.4.1) to the file download as SentaiBrad keeps recommending to others but apparently even if you set the name the same as this current thread the system will still create a new thread with the same. So anyways, latest minor update to add support for BigBox's startup video feature, can be found here.

Kodi addon for LaunchBox View File Launches LaunchBox in Big Box mode from within Kodi - It will close or minimize Kodi, launch LaunchBox in Big Box mode and when Big Box is exited Kodi will restart or maximize, with the option to run programs pre/post LaunchBox. It works with Windows only. Features: BigBox Startup video and splash screen support BigBox Updater support Pre/Post scripts Minimize or close Kodi option Launcher Helper script version check Supports Kodi 16, Kodi 17, Kodi 18, Kodi 19 and Kodi Windows Store versions. Requirements: Windows PC LaunchBox Premium Kodi 16, 17, 18, 19 or Kodi Windows Store for Windows Known Issues: Due to Windows Store's UWA security restrictions, user must set a save directory under the plugin's Advanced Settings to a directory of the user choice where the plugin's ahk helper script and icon file can be saved. Taskbar will flash on Kodi Windows Store version (UWA) using 1.5.4+. Current workaround is to switch to Kodi non-UWA or to minimize effects, enable hide taskbar in advance options, remove Cortana search bar and change taskbar to black. Starting with version 1.5.6, due to windows security restriction on SMB shares over IP (eg. \\192.168.1.1\shared-folder\), the addon will produce an error saying it is not supported. Current workaround is to enable SMB fix in Advance settings to replace IP with supplied server name or enable SMBv1 on server and computer to allow NetBIOS name resolutions in Kodi. Kodi-six package is now required with 1.5.6+, addon will fail if after first installation of Kodi-six package dependency, Kodi was not restarted. Install instructions: Use 'Install from Zip' in Kodi and browse to the directory the plugin's zip was downloaded to and select it. Configuration: This plugin requires the user to set the location of their LaunchBox directory in the addon settings before first use. eg. C:\Users\<username>\LaunchBox\ PLEASE NOTE: THIS PLUGIN WILL PRODUCE AN ERROR DURING INSTALL IN KODI ON ANY OPERATING SYSTEM THAT CANNOT RUN LAUNCHBOX. SINCE LAUNCHBOX IS CURRENTLY WINDOWS ONLY THAT IS THE ONLY OPERATING SYSTEM THE PLUGIN CURRENTLY SUPPORTS. ATTENTION: WILL NOT WORK ON ANDROID (BOX, SMART TV, ETC.), IOS or MAC AND LINUX. Submitter CoinTos Submitted 01/25/2017 Category Third-party Apps and Plugins  

Hey cm0123, please attach a Kodi debug log while trying to launch Bigbox with the addon and I will look into what is happening. If you have never done a Kodi debug log before here is a link to the Kodi debug log wiki page. Thanks,

I can confirm this as well on both the last and current beta, On both my laptop and htpc the platform wheel images don't show till you press up or down.

We need a true classic for a BigBox voice reply. My personal favourite is broken english, or if you prefer, "Engrish" translation of games. "All your base are belong to us" - Zero Wing (1989) [English translation]

@ashramrak Since there hasn't been any complaints about the last test file, here is the final version of the 1.4 for the first post. See above post for changes. script.launchbox.launcher-1.4.zip New versions can now be found here:

I would have to see the batch file because my test.bat launched every time with either way, hardcoded ($Esc::Run, %comspec% /c "c:\scripts\test.bat",,Hide) or with variable defined at top (batchpath=c:\scripts\test.bat) and set in command ($Esc::Run, %comspec% /c %batchpath%,,Hide) So you got working then outside of launchbox ahk?

Ok, here is the cleaned up and formated version as promised. Last chance for any changes before it goes to ashramrak to have the 1.3.95 changed to 1.4 for official release at the top post. New Features: Supports Kodi 16, Kodi 17 and Kodi Windows Store* versions. Bugfixes: Added error handling to prevent ahk script from hanging and needing to be manually closed. Fixed ahk script comparison check. Changes: Updated addon.xml for better Kodi 17 support Removed need to set Kodi exe in plugin settings * Due to Windows Store's UWA security restrictions, user must set a save directory under the plugin's Advanced Settings to a directory of the user choice where the plugin's ahk helper exe can be saved.

$Esc::Run, %comspec% /c "c:\example\example.bat",,Hide Change the example path and bat file to yours and that should work.

Are you looking for a complete script or just the best way to run a bat file in an autohotkey script you already started? ; Set batch file path batchpath = c:\example\example.bat ; Run bat script, hide cmd window Run, %comspec% /c %batchpath%,,Hide The above is most likely what you are looking for, if not let me know.