CoinTos
-
Posts
169 -
Joined
-
Last visited
Content Type
Profiles
Forums
Articles
Downloads
Gallery
Blogs
Posts posted by CoinTos
-
-
Test 2 attached now is just to clean up all the smb separation mistakes in test 1. I am posting it while I continue working on 1.5.9's stable release, just incase some needs the autohotkey delay fix and wants to test smb.Test 3, due to how the newer LaunchBox installers work, they will kill the AutoHotkey.exe process if ran from LaunchBox folder on update, therefore killing the AHK script. The addon now copies the AutoHotkey.exe and license.txt (if found) from LaunchBox folder to the userdata folder. Also, under Advance settings there is an option to change to another user selected AutoHotkey exe if desired.
-
@debennett2 Can you give one of these test files a try (py3 is for Kodi 19) and see if it fixes the slow down. I added an AutoHotKey Location setting under Advanced in settings, if the location is blank or invalid it will search the LaunchBox folder for AutoHotkey.exe and if it finds it, it will set the AutoHotkey location setting so next time it doesn't need to waste time searching... well till it is invalid again, that is.
-
On 7/27/2020 at 1:48 AM, magerbooze said:
So I am having an issue
"Failed to create mapped drive"
I have launchbox on smb
The launch location for launchbox is //homeserver
It works for videos but not launchbox for some reason
hope you could help
Sorry it took so long to reply. I am in the process of rewriting a bunch of the smb logic as I finally got some spare time to look at it today. I will need some more information though and possibly a file path from launchbox's xml config (Launchbox\Data\Platforms\<platform>.xml) to see if my logic is even right. As for the fail to create mapped drive, can you try manually creating a mapped drive in cmd "net use * //homeserver/<some folder to test>" and see if it errors out.
-
Kodi addon for LaunchBox 1.5.8 released!
CHANGES in 1.5.8:
- Fixed AutoHotkey location slow detection using debug help and code from @doogie
- Added some more logging to detect delays betterKNOWN 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 an optimization fix and adds additional logging. I made a bone head mistake in my AutoHotkey location detection and did not ignore directories that would never contain it. Thanks to @doogie for taking the time I didn't have and locating as well as supplying fix.IN DEVELOPMENT:
- Back to looking into multiple Launchbox support, most likely now a Kodi 19 only feature. -
Well, here's a not so perfect solution that may be better in your use case. You can compile into autohotkey exe or rename the autohotkey exe and script ahk to the same name. Use a script like this as your shell, you will still see the taskbar flash in my very quick tests but might be more to your liking and allow explorer active for volume control.
#NoEnv #SingleInstance force SetWorkingDir %A_ScriptDir% ;Load Explorer Run, explorer.exe ; Load Blank GUI to cover taskbar loading Gui,Color,Black,000000 Gui, -Caption TempVar := A_ScreenHeight +100 Gui,Show, h%TempVar% w%A_ScreenWidth% ; Load Bigbox Run, <path to BigBox.exe> WinWaitActive, ahk_exe BigBox.exe ; Sleep for x ms before exiting script Sleep, 5000 ExitApp
-
Kodi addon for LaunchBox 1.5.7 released!
CHANGES in 1.5.7:
- Separate Python 3 version for Kodi 19+ support
- Fixed AutoHotkey location change in 10.12+
- Fixed the blank black window not staying behind BigBox
- Improved Kodi SMB support error handling
- Other minor error handling fixesKNOWN 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 fixes the AutoHotkey directory change in 10.12, now the script will search the LaunchBox directory for the AutoHotkey.exe allowing it to remaining compatible with previous and future directory changes for Third Party Programs in Launchbox. It will now error out if it doesn't find the AutoHotkey.exe. Also, a bunch of bug fixes and error handling improvements were made for both SMB support and general script handling. Due to changes in Kodi 19, there is no way to have a python 2/3 compatible single package so a separate Python 3 only package is available for Kodi 19 Alpha+ users. This package will upgrade any user with a Kodi 16+ existing install who moves to Kodi 19 just by install it after upgrading to Kodi 19.IN DEVELOPMENT:
- Back to looking into multiple Launchbox support, most likely now a Kodi 19 only feature.-
2
-
-
44 minutes ago, 03397 said:
The Kodi is running.
I am getting into bigbox using the script.
OK, I need you to troubleshoot and I am obviously not saying this right so I am going to put this in steps.
1. Do NOT use Kodi, exit out.
2. Launch BigBox via the start menu or desktop shortcuts
3. Launch Origin Games like you have been doing and note if the same thing is happening
4a. IF so, please post a topic about your issue in the LaunchBox Troubleshooting section, it is not a me problem.
4b. IF not, it may be a problem with script and I will try to recreate it. -
5 minutes ago, 03397 said:
It is kind of difficult to explain.
Origin does not appear since I have it running at the background and not as a window.
So, when I start the game with origin for the first time, I log in to origin, origin runs at the background. After I finish the game I return to bigbox and I can navigate just fine.
If I start again the game since I am already logged in in origin, game starts automatically but after i exit the game and return back to bigbox, now I need alt+tab so that I can navigate. It is like origin is focused but without its window to be visible.
This is happening for all the games that run with origin. I do not have this problem with other launchers.
If it happens with just BigBox running and not using this script with Kodi, then I have to refer to Jason and you will have to start a thread in LaunchBox Troubleshooting, as that is not something this script is meant to handle.
-
7 minutes ago, 03397 said:
No I meant when I exit the game I return in bigbox not in origin, I do not return to origin, but in order to be able to navigate I need to use alt+tab.
This does not happen when I start the game for the first time and I log in to origin.
Right, so you launch the game it requires Origin to launch in order to launch it so Origin loads and displays but when you exit the game, you don't see the origin launcher anymore but BIgBox. That would be outside the scope of this script, if you were to try do same with BigBox only, no Kodi, and you get the same result, that would fall onto BigBox to take care of Origin's focus, so you would need a game exit script to fix that or talk to Jason for a feature for Origin Games.
-
3 hours ago, 03397 said:
I have downloaded the beta version but the problem is still there.
To give you a clearer picture when I start an origin game for the first time inside launchbox and exit the game no alt+tab is needed.
But when I start the game and I am already logged in origin the alt+ tab is needed.
So what you are saying is the alt+tab is need to display the game or Origin client as in BigBox is over it? I personally hate Origin and only use it because of Battlefield 4 which I wrote an open and close script to kill it after I am done playing so give as much detail as possible and I will see if it is in the scope of this script or if you will have to do something like I did.
11 hours ago, ivant said:You're a legend! Whatever you changed in the beta has fixed the issue. Thanks!
PM me if you have any donate details, happy to tip for the work.
Good to hear, it didn't break anything because it really was a simple fix, can't believe I missed it when I first did the blank window.
-
-
27 minutes ago, ivant said:
Yep only happens with mednafen, no issues with the others.
In LaunchBox's emulator settings for mednafen, in the Exit AutoHotkey script tab, try this:
if WinExist("ahk_exe BigBox.exe") WinActivateThat should being Bigbox back to front whenever you exit that emulator.
10 minutes ago, 03397 said:I have the exact same issue with the origin launcher of EA.
Every time I exit the game I need to alt+tab.
I can't force the black window to the back because it will go under the task bar which defeats it's purpose of hiding desktop icons and such. I take a look at trying to make it hide behind BigBox all the time but i am not sure that is possible without breaking things but I will look into it.
-
15 minutes ago, ivant said:
I'm having a minor issue with 1.5.6 when I exit games that use mednafen emulator, I have a blank screen that I have to manually alt-tab out of back to big box.. the tab is called AHK.ahk
I haven't configured an autohotkey script or anything. Any idea on no how to solve this?
Only happens when I use bigbox via this addon.
What you are seeing is the blank black window, the script creates to hide desktop icons. For some reason your mednafen is bring it in front of BigBox on exit. Is it the only emulator that does that for you?
-
Well, due to self isolation starting this morning, I have a beta fix for those that need it. Apparently, some changes were made in Kodi 19 so I will have to start working on 2 separate releases for python 2 and 3. So for right, I am releasing a 'beta' for Kodi 16, 17, 18, Store here and will work on getting a proper release out in the day or so.
Changes:
- the script will now search the LaunchBox directory for the AutoHotKey.exe and error out if not found.
-
52 minutes ago, meshflesh said:
JUst want to mention. As of the latest launcbox update 10.12. the plugin no longer works. thank you
Yep, it was noted yesterday, LaunchBox changed the directory structure and nested the AutoHotkey directory in ThirdParty. It will be properly fixed this weekend as I am still out in the field working and can't schedule time for it till my days off. A manual edit is noted 3 post before this, if you want to quick fix it yourself.
Edit: Looks like you edited while I was replying, glad it is working again. Stay tuned for a proper fix.
-
6 minutes ago, Narecker said:
Well it seems that you found the problem... no AHK folder in my launchbox directory !
I'll do a clean reinstall and keep you up to date !
It's under Launchbox\ThirdParty\AutoHotKey, it appears the latest (at least latest Beta for sure, on my test machine) Launchbox redid directory structure.... well, that sucks, gonna have to release a fix for that. Sounds like a 'this coming weekend' project for a proper fix but till then you can manually edit the main.py line 346 to:
autohotkeyExe = os.path.join(launchbox, 'ThirdParty\AutoHotkey', 'AutoHotkey.exe')
That should fix it.
-
12 minutes ago, Narecker said:
Indeed my bad I tried yesterday with the 1.5.5 version !
Here it is : https://pastebin.com/uQrmEuJU
Again many thanks for your help
2020-03-25 01:59:10.328 T:1728 DEBUG: script.launchbox.launcher: attempting to launch: "C:\Users\<user>\LaunchBox\AutoHotkey\AutoHotkey.exe" "C:\Users\<user>\AppData\Roaming\Kodi\userdata\addon_data\script.launchbox.launcher\scripts\LaunchBoxLauncher-AHK.ahk" "C:\Users\<user>\LaunchBox\BigBox.exe" "0" "false" "false" "false" "false" "false" "0" 2020-03-25 01:59:10.330 T:1728 INFO: CPythonInvoker(3, C:\Users\<user>\AppData\Roaming\Kodi\addons\script.launchbox.launcher\default.py): script successfully run
So it tries to launch the ahk script with the setting parameters and does not catch an error which suggest it does find the AutoHotkey.exe. Can you confirm AutoHotkey.exe does exist in your Launchbox\AutoHotkey\ folder and you don't have any log files in your C:\Users\<user>\AppData\Roaming\Kodi\userdata\addon_data\script.launchbox.launcher\scripts\ folder, correct?
-
47 minutes ago, Narecker said:
Its on me ! I had to check your post ! I'll do it now
Here it is : https://pastebin.com/hFiEb32n
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.
-
12 minutes ago, Narecker said:
Ok ! I checked the path you gave me and didn't found any log in it. Sorry I am quiet a newbie regarding this but I dont know where I can find the debug log you need :s
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
-
9 hours ago, Narecker said:
Hello CoinTos ! Happy user of your addon for a year I'm in the same situation as snarfo67. I updated Kodi (18.6) and your addon (1.5.6) and it stopped working. I'm on the non windows store version of Kodi.
I checked the userdata but dont know what to search for
Thanks in advance !
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.
-
1 hour ago, snarfo67 said:
This addon has been working flawlessly for me for over a year, but when I tried to launch it a few days ago, I got... nothing. No crashes or errors from Kodi, just no response. I checked and saw I had version 1.5.3 installed so I manually updated it to 1.5.6, but still no luck. Uninstalled and reinstalled, no joy. Any ideas? For the record, script writing is not my forte...
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.
-
16 hours ago, CtinD said:
OK, so its not launching through my launcher. I changed the script to what you suggested but it's still just launching the BigBox.exe instead of my launcher. This is a rather sophisticated script and I dont want to break it. Any suggestions? I am sorry if i am being a pain
Edit: So I sorted it out by leaving the script alone and instead opening main.py and edited line 345 bigboxExe = os.path.join(launchbox, 'BigBox.exe') to the launcher. Works perfectly for me now. Thank you for your help @CoinTos
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.
-
6 minutes ago, CtinD said:
That's what I was wondering. I use the same directory as launchbox for my launcher. I am somewhat experienced in editing AHK scripts from the early hyperspin/hyperlaunch days. I cant quite make heads or tails as to what I need to edit so that it looks for my launcher, which is named Bigbox[1].exe, rather than bigbox.exe. I already have it launching bigbix perfectly through the add-on. I just want it to search for my launcher instead.
Honestly, this is only my second time asking for help in editing ahk scripts, It is pretty straight forward. I am juts lost in this instance.
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).
-
12 minutes ago, CtinD said:
Awesome addon for kodi. I have a bit of an issue that I am trying to sort out though. I run all of mmy games through steam for the ability to remap the controls on the fly. This includes launching BigBox. I have created a bat file that launches BB through steam and converted it to exe so it is invisible. I am trying to find in the script where it searches for the BigBox .exe and change that to my little launcher, but am not having luck finding it....can anyone help me with this. Even if its a post launch script. Thanks in advance
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.
Kodi addon for LaunchBox
in Third-Party Applications and Plugins (Released)
Posted
Maybe it's one of the exit settings in Launcher4Kodi for the whole taskbar starting, I use Launcher4Kodi 1.1 as my shell with all exit settings off and no problem with Kodi/BigBox. I don't use AnyDVD but I have never had an issue with my blu-ray drive after using BigBox from Kodi, Kodi still sees my drive/disc and hands it off as expected to PowerDVD. So don't think I can be much help on that issue.