CoinTos

Ok, can get you to update to the latest version, according to the log you are running 1.5.5 and the latest is 1.5.6 which introduced smb support and some code fixes. Probably won't change the issue but it will provide me with a debug log on my current code base and may produce a different result I can chase. Thanks.

My bad, in my previous post I did linked the Kodi Log File/Easy instructions on the words "debug log", I will need you to provide a pastebin link in your reply so I can view your posted debug log. Please follow the instructions here: Kodi Log File/Easy

Ok, in the %AppData%/Kodi/userdata/addon_data/script.launchbox.launcher/scripts/ there should be up to 2 logs LaunchBoxLauncher.log and LaunchBoxLauncher.old.log those should tell me what the ahk script is doing. If they are too old (aka you tried to run but the modified date is not the same date) or missing than the script didn't even make it launching the ahk script. I will then need a sanitized (usernames and passwords that other plugins may show during debug removed) debug log and pastebin link them so I can look at them. Currently, I am running Kodi 18.6 with addon version 1.5.6 and latest launchbox with no issues so I cannot currently recreate it.

Ok, lets start with the basics, what version of Kodi are you using or is the windows store version? Can you try enabling the "Delete and update userdata scripts on next run" option in Setting under Advance, then relaunch. If it is windows store version make sure the "UWA Fix: Change ahk script location" is enabled and valid save directory is selected. If that still fails, I need you check userdata directory (or selected save location for the UWA option) for the scripts run log. For windows 10 (non-UWA Kodi) %AppData%/Kodi/userdata/addon_data/script.launchbox.launcher/scripts/ will get the folder containing the log.

Yeah, my bad, forgot to mention that you need to select the "Delete and update userdata scripts on next run" in the addon's advanced settings, that will actually replace the old ahk one with the one you modified. Editing the python main.py is the other way but the autohotkey way is usually easier, that is, when I put the sentence before in the instructions.

Replace the %1% on line 67 of the autohotkey script with your full path to BigBox[1].exe (example line 67: BigBox = ?\Launchbox\Bigbox[1].exe).

The addon requires you to specify your Launchbox directory in its settings in Kodi and uses that to pass the bigbox.exe location to the autohotkey script which then handles the launching and monitoring of BigBox. So you would have to edit the autohotkey script to instead use your launcher instead of the supplied bigbox.exe location.

Hey @Bedwyr, Just got back from a week and a bit in the great outdoors, no cellular signal out where I go or I would have posted a reply sooner. Basically, the quote above is what I posted about porting a script to another program like GOG or Epic Games. That would be your simplest option. I hitting my slow season shortly with work which means I will look at improving my script some more with delayed ideas I have been toying with and I should be able to help you figure out the parts you are stuck on as I don't think GOG or Epic really need as much scripting as LaunchBox did to work properly.

Kodi addon for LaunchBox 1.5.6 released! CHANGES in 1.5.6: - Kodi 19 support - Python 3 compatible - Kodi SMB support 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. - Kodi-six package is now required, addon will fail if after first installation of Kodi-six package dependency, Kodi was not restarted. RELEASE NOTICE: This release is to add python 2 and 3 support, as well as SMB support to the version 1.5 branch. This allows the addon to support Kodi 16 to 19 as well as be able to use a remote SMB share for the Launchbox location setting. Unless any bug fixes are required this will be the end of the version 1.5 branch after which support for Kodi 16 and Kodi 17 will be dropped. The next planned version will be moved to Kodi 18+ support to allow easier management of GUI interfaces code for the multiple Launchbox support. IN DEVELOPMENT: - Back to looking into multiple Launchbox support Thanks goes to @nadonate for helping to test the SMB support over in the Kodi addon for Launchbox - Testing thread.

Beta 2 Released Fixes: Changed the smb label text in Advanced settings Rewrote Update handler to work with smb shares support better in AHK script

Glad, it's working for you now. The beta I posted this morning has work around for those that can't enable SMB1 support but letting you set the smb share with an IP in the addon's launchbox location and then setting the server name in the SMB IP Override option of the addon's Advanced settings. It then replaces the IP with server name supplied. As long as you can access the share (\\server\share\folder-with-launchbox-folder\) directly in windows network browser, you can use the IP override without setting up smb1 for Kodi and the mapper will create the drive with server name instead of IP to launch BigBox.

I am moving this test file from Alpha to Beta. Everything is feature complete for 1.5.6's release just need some testers for both with and without using a smb share. If you use an IPv4 address (IPv6 is not support at all) for your smb share you will need to enable SMB IP Override setting in Advance Settings and enter in your SMB host name of your share server. If you don't, a dialog will pop up telling you to do so or if no is selected, it will exit the addon. Key Features: Kodi SMB support (user/pass, IPv4 override support) Python 2 and 3 compatible using Kodi Six library (Kodi restart is required on first install of Kodi Six module or addon won't see it)

As long as you can get a path to BigBox.exe folder in Launchbox folder field (ie. smb://192.168.1.11/games/launchbox/) the addon doesn't care about smb version because it uses external commands (net use) to create the mapping. So if you can try that with last test file and it still fails then it has to do with how I handle 'net use' creation in python. We have proved that commands and mapping work outside of Kodi so all that leaves is the mapping creation in addon's python code. EDIT: I can recreate it now, it has to do with using a IP instead of hostname. Looking into it now. EDIT 2: Nothing I can do to allow IP mapping support, from all my searching windows won't let exes run from a mapped drive created with an IP instead NETBIOS name. So unless you can get a netbios name in the launchbox location field, it won't run. I will have to work on a workaround.

So, using smb share directly in the addon folder location still fails?

Ok the script doesn't mount directly to the launchbox due to update installer compatibility, can you try: net use Y: \\lyonas\games Then browse to the launchbox folder (Y:\launchbox) and try launching it. Also, the new test file still fails to launch it when the share location is used, correct?

My bad, I quickly typed that reply at the start of my work day. what i meant was in command prompt (not running prompt as admin mode) run the "net use" mapping command then launch BigBox.exe from that mapped drive's launchbox folder, no Kodi involved in that test. If that works, leave the mapped drive, launch Kodi. point the addon to the launchbox folder on that still existing mapped drive and try launching it. If that works, let me know, then you can remove the mapped drive using the bottom command in command prompt. If any of those don't work, then let me know as well. But first, try this, I have new test file. I spent most of today cleaning up the error handling, removing all deprecated ahk code found and rewrote it using current recommended standards.

OK so lets start with creating the mapping the way you used to and using that mapping folder path in the Kodi addon, should still work the same, aka it loads Bigbox fully. If it doesn't then we have different issue. If that still works, try manually doing the commands I use to create the mapping. First try running BigBox.exe outside of Kodi and see if does the same closing issue then we know it's could be mapping, permission, or possible a firewall/antivirus issue of some sorts. If it doesn't, then try using the created mapping folder path in Kodi. If that works then it's an addon issue of some sorts with the mapping creation. ; Non=admin cmd prompt ; Without username and password net use * \\path\to\<dir holding launchbox folder> ; or net use * \\path\to\<dir holding launchbox folder> /user:username password C:\<drive>:\<launchbox folder>\BigBox.exe ; After all testing, with and without kodi you can use the following command to remove the mapping net use <drive>: /delete

@nadonate New test file handling BigBox dying before showing a window. Will gracefully clean up the mapped drive created by the Kodi addon before launching the AHK script. It doesn't really fix your issue but will log now if BigBox dies unexpectedly in launch while I still work to understand the issue causing your problem.

Ok, under process tab is it gone from background processes as well? This is weird one because on my test machine in any version of Kodi, it stalls a little, not responsive due to loading over wifi, no issues on hard line and takes up to about 1gig of ram while loading up (I tested with and without a start up video) and runs without issue. I don't really know how to recreate this. I also did a launchbox update test over the mapped drive with addon and that is when I saw a 7zip extraction on first boot after update that stalled the start up a fair bit more but haven't had anything kill the process like your video suggests.

OK, well Bigbox.exe ran or it would timed out and produced an error. Can you please launch task manager, set it to details view and always on top then use the addon. Check if there is a 7z.exe running when Bigbox launches or if BigBox.exe exits after launch.

@nadonate This is a python 2 and 3 compatible smb test file (supports Kodi 19 Matrix). It will install Kodi-Six dependency, if you don't have that installed already the current test file will 'fail' due to no 'Kodi-Six' module found. You must restart Kodi to allow the dependency to active then this addon will work. This test file is also now compatible with updating Launchbox through BigBox (disable auto updater workaround still applies), the previous test file wasn't compatible due to how I created the mapped drive.

Ok, i think i know what is going on but first can we confirm it is the ahk timing it out. Can you check the LaunchBoxLauncher.log (C:\Users\<username>\AppData\Roaming\Kodi\userdata\addon_data\script.launchbox.launcher\scripts\ if you are using Windows installer Kodi) to see if says BigBox wasn't detected in 60 seconds. Also, are you using hardline or wifi for the connection.

Oops. apparently, I wasn't set to be alerted to new post on this thread, my bad. Anyways, this one is for @nadonate, here is a smb test file. Basically, it will create a temporary mapped network drive and then destroy it when done. This should fix your smb issues in kodi... hopefully. I have tested it without a username and password, no issues. It does have username and password support that will need to be tested so if anything one has that setup, please report back.

You would have an easier time modifying Steam Launcher for those programs than using my script as base due to the way it uses launchbox's included autohotkey.exe to make the ahk helper script work. With Steam Launcher you would have to change: folder name, addon.xml, default.py (to look for the exe of those program launchers), strings.xml (setting display text) and recompile the autohotkey ahk file into a exe with the changes to monitoring names for those programs exe's which you have to use autohotkey window spy to get the detected window and/or class names. I haven't really looked myself but that is why I want to make a PowerShell helper script to handle that by creating a mapping on Kodi smb link detection on launch and destroying it when Launchbox is done running. Doing that should allow it to be more stable and less unreliable when using sleep/hibernation etc.

Yep, it has to do with the way Kodi handles smb shares. I wrote a test file that translates it to something that could be passed to the helper script and the path detection but abandoned it when I couldn't cleanly handle usernames and passwords on shares. I am looking into a way of using powerscript to automate the creation of a temporary mounted network drive when a Kodi smb is supplied but that is currently delayed. I am back in classroom training newbies for the company i work for and have limited free time currently due to travel time. I plan to tackle the multiple Launchbox support and attempt the smb stuff during my vacation near the end of July. Current workaround is to create a mapped network share to assign it a drive and use that in Kodi.