CoinTos

Are you selecting the LaunchBox base directory (ie. <drive>:\<path to>\Launchbox\) in the setting of the addon? Everything still works fine with Kodi 21 as I just updated and double checked so I am guessing the LaunchBox folder path is wrong in the addon settings.

All you have to do is select the LaunchBox Folder field in the addon's settings under General and browse to the LaunchBox base folder ie. C:\Users\SomeUser\LaunchBox\ then select ok. You do not need to add BigBox.exe to the LaunchBox Folder location field, the addon adds the BigBox.exe or LaunchBox.exe (depending on mode selected) to the folder specified in the addon's settings and check if the exe (of the mode selected) exists in the previously specified folder, if not the addon produces that error.

The zip isn't supposed to be extracted or ran from LaunchBox directory. To install in Kodi, you need to install from zip. See Install from Zip on the Kodi wiki for how to. After which you run the addon from Kodi's Addons Menu and set the settings in addon's config to your liking while making sure LaunchBox's base directory location is set in Launchbox folder field.

CHANGES in 1.6.0: - Add support for LaunchBox and BigBox modes - Kodi 19+ support only - Detect which monitor has Kodi on it and moves LaunchBox to it - A ton of bug fixes 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. - Taskbar will flash on Kodi Windows Store version (UWA). Current workaround is to switch to Kodi non-UWA or to minimize effects, enable hide task bar in advance options, remove Cortana search bar and change taskbar to black. - 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. RELEASE NOTICE: This release moves the addon to only Kodi 19+ and dropping support for all previous Kodi versions. It also adds support for LaunchBox (Free or Premium) and BigBox modes as well as multi monitor detection.

Thank you for your help in testing, the final release has now been posted to the download section.

I think I have fixed everything you have listed here. Try this one and if it still loads on the first monitor when Kodi is full screen on the second, please post the launcher's script log because I will be really confused on why it's not working. I have a tri-monitor setup and I have no issues on any of the monitors with Kodi loading on them fullscreen and moving LaunchBox to that monitor which is displaying Kodi. The maximizing of Kodi when Kodi was minimize while in window mode is fixed as well, that was just missed by me because LaunchBox ahk script is based on my BigBox ahk script which is for a 10ft setup hence the maximize on reload instead of restore. Also, the "Delete and update userdata scripts on next run" will turn off after every run of the addon if you turned on before hand, as it's purpose is to remove the ahk files and autohotkey.exe and recopy the files from the currently installed addon. This allows you to rule out outdated script files and have the ones from the currently installed addon and current autohotkey.exe from LaunchBox copied into the userdata folder. Outside of this testing, normally the addon will ask you if you want to update the userdata's copy of the scripts if the addon's version is newer than them so turning that option on normally isn't necessary. So to some up Beta 7 below: I rewrote the whole handling again including LaunchBox update handling.

I don't know what pop up window it is detecting so here's another beta that looks only for the one LaunchBox would create and moves it to the monitor Kodi was running on, after it is closed it will move LaunchBox to that monitor. Make sure Kodi is completely in the monitor you want LaunchBox to move to then launch the addon or set Kodi to load up in fullscreen to wanted monitor in Kodi's Display settings,

So on your main monitor is there a pop up asking you if you want to upgrade LaunchBox? It's waiting for that be closed before continuing. If you don't care about upgrades or need to stick on one specific version, please disable upgrade checks in LaunchBox's options. Also, is your Kodi running in windowed mode? The script is detecting the left top corner of Kodi is in the first monitor. Go to your Kodi Settings and set it to start on your preferred monitor or move it completely into the second monitor.

@oliviergregoire try this one and post the log.

It won't move launchbox to the new screen till main window is loaded, I will upload another beta in a few minutes that will not fix it but will give me more info in the log to try and figure it out.

Kodi addon for LaunchBox 1.6.0~beta4 Changes since beta 3: - Multimonitor detection added for both LaunchBox and Bigbox, it will move LaunchBox to match where Kodi is but for BigBox, you will have to have the screen set in it's setting menu. - Fixed the black gui's window size to not bleed on to other monitors Hopefully, this will be the last beta and I can release it as a ton of time was spend on coding, testing and debugging this.

Current beta is posted on the Testing Thread, won't have a final release till this weekend.

I always recommend updating to the latest release that I put out as I usually found a mistake I made and fixed it. 🙂 As for the starting on the same screen as Kodi, it's possible and I will look into it when I get some time, probably by this weekend. Use beta 3 for now as it is basically what I was planning to release if nobody else that tried it finds an issue and I will post another test file if I get something sensible for you request.

Kodi addon for LaunchBox 1.6.0~beta3 Changes since beta 2: - More code clean up and logic improvements - Support restored for Kodi 19+

Under the addon's settings "General" section, change "Quit Kodi?" to "No" and Kodi will be minimized instead of being closed.

There is your problem. Please disable the Kodi override option in the addon's advanced section as the script should detect kodi.exe location. Only if the script doesn't detect it or is needed for a special use case, you should enable it and point it to kodi.exe location. Also, update the file I uploaded above as there are some code improvements that will need to be tested. Thanks.

Kodi addon for LaunchBox 1.6.0~beta2 (Kodi 20+ only) Changes since beta 1: - Some ahk script code clean up for Launchbox free and premium support

Can you show me the log from "C:\Users\<username>\AppData\Roaming\Kodi\userdata\addon_data\script.launchbox.launcher\scripts\LaunchBoxLauncher.log"? I don't have a windows 7 system test on so I will have to see what was detected by the ahk script's log.

It's the same as the regular download from the released page. - Download the zip to a folder - Open Kodi 20 - Go to Settings, Addons, Install from zip. - Browse to download folder and select zip - note in Kodi's addons settings page, 'unknown sources' must be enabled to install from zip Also, if you have had an older version of this addon installed, please go to this addon's settings, under advanced and select "Delete and update userdata scripts on next run". I goofed on the handler script version numbering when I split launchbox and bigbox into 2 separate autohotkey scripts so till next beta or final, existing users will have to do that to get the right script active and working.

Tester Needed for beta. Kodi addon for LaunchBox 1.6.0~beta1 (Kodi 20+ only) Changes: - Mode select added for choice between LaunchBox and Bigbox, support both free and paid versions - support for Kodi 20+ only to keep my life simple @hellgate24@Mad.Monkey.3@oliviergregoire

Alright, good to know, that hasn't changed. @Dan79 Make sure that your License.xml file is in the LaunchBox root folder and that BigBox when launched manually accepts it. If the script still errors out provide the log from script's data directory, normally located in "C:\User\<insert user>\AppData\Roaming\Kodi\userdata\addons_data\script.launchbox.launcher\scripts\LaunchBoxLauncher.log", and I will take a look.

My guess is LaunchBox dev's changed where the Licence.xml is located. That error shows when no file called License.xml exists in the root LaunchBox directory. Just create a blank text file called License.xml and the error will not show anymore. If I get time, I will look into a proper fix, most likely just remove the file check and do something else to ensure the user understand Premium is required.