Jump to content
LaunchBox Community Forums

CoinTos

Members
  • Content Count

    142
  • Joined

  • Last visited

Community Reputation

38 Excellent

3 Followers

About CoinTos

  • Rank
    32-Bit GPU

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Well, the whole Kodi and python 3 is fun story, basically Kodi 18 was python 2 like the ones before but they had Kodi 18 test builds with python 3 instead for those that were making addon's python 3 compatible to test on. Kodi didn't officially switch to python 3 till upcoming Kodi 19, currently in alpha.
  2. Kodi addon for LaunchBox 1.5.9 released! CHANGES in 1.5.9: - More fixes to AutoHotkey detection - AutoHotkey is now copied from LaunchBox to the addon's userdata - User can set their own AutoHotkey.exe from Advanced settings - Some code clean up with the 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 another optimization fix. Cleaned up some code with the smb support. AutoHotkey is now save in the addon's settings to stop it from scanning for it on every launch, on first detection will copy AutoHotkey.exe and license.txt (if found) to the addon's userdata folder to fix AHK script update installer support. The installer was killing AutoHotkey.exe the addon was using in the LaunchBox folder causing the AHK script to close. Added option to set own AutoHotkey.exe in Advanced settings of addon. IN DEVELOPMENT: - Back to looking into multiple Launchbox support, most likely now a Kodi 19 only feature.
  3. 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.
  4. 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.
  5. @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.
  6. I am currently in the process of changing some logic for Autohotkey exe again and I think I know what is causing the slow down.
  7. 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.
  8. 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 better 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 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.
  9. Just finished 8 straight days of work in the field so I have just sat down with the code today. I will be posting a file in a few hours as I am currently reviewing and testing the fix and improving some debug logging.
  10. @doogie You are 100% right, I didn't constraint it which was dumb on my part. I will look into the code you posted and add you as contrib, releasing the fix shortly. I haven't done anything on Github because I really have no need for as I do this addon for fun and my own use. I post the releases here leaving the control of it's existence in the hands of the LaunchBox's moderators and administrators which so far has worked out well for me. Thanks for helping out as I really haven't had time to look into this properly.
  11. 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
  12. 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 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. - 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.
  13. 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.
  14. 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.
  15. 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.
×
×
  • Create New...