Jump to content
LaunchBox Community Forums

CoinTos

Members
  • Posts

    169
  • Joined

  • Last visited

Posts posted by CoinTos

  1. 1 hour ago, dbcooper said:

    This is the guide I followed. I installed from zip as directed.

    When I try to open LB I receive the following error, which requires me to add bigbox.exe to the path:

     

    However, afterwards (when I then try to add the Bigbox.exe file to the path) it is still not visible when I navigate to its location. Even though I can see the Bigbox.exe in my window explorer

    Screenshot (1).png

    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.

  2. 33 minutes ago, dbcooper said:

    Kodi 20.1 on Windows 10 initial install:

    Kodi cannot see the Bigbox.exe. I ran the zip file from Launchbox folder. But while in Kodi, I cannot see Bigbox.exe in the launchbox folder, thus preventing me from adding it to the path. I used:

    However, when I'm on the desktop using the Window explorer I can see Bigbox.exe in the launchbox folder. I have tried a fresh install of Kodi and showing hidden files in Windows.

    How do make Bigbox.exe visible to Kodi 20.1? Thank you in advance!

    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.

  3. 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.

     

  4. On 2/2/2023 at 1:32 PM, oliviergregoire said:

    CoinTos, I'm really sorry I didn't answer earlier.

     

    So I did several tests:

     

    I went back to beta 3 to verify the black screen and discoverd I had the black screen when I closed the Launchbox window if "Delete and update userdata scripts on next run" wasn't selected.

    As for beta 4 & 5: I had black screen whether  "Delete and update userdata scripts on next run" was selected or not.

     

    Beta 6:

    Everything works great: no black screen at the end whether "Delete and update userdata scripts on next run" is selected or not.

    • If Kodi is in window mode: Launchbox starts on the screen the kodi window is, with a little delay if it's on screen 2 (it starts on screen 1 then move by itself on screen 2. Nothing important for me).
    • If Kodi is in fullscreen: If I'm on my main monitor (1), Launchbox starts on screen 1. But if Kodi is on screen 2 (TV), Launch box starts on screen 1 and Kodi stays on screen 2.

    I did several tests to verify, one after another and always get the same results.

     

    Also, when I start Kodi in window mode, when I close Launchbox Kodi comes back in maximised window mode, it does the same for every betas.

    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.

     

  5. On 1/30/2023 at 3:45 PM, oliviergregoire said:

    No there's no pop up

    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,

     

  6. 2 minutes ago, oliviergregoire said:

    20230130010741 - INFO: Starting LaunchBox Launcher Autohotkey script revision 104.
    20230130010741 - INFO: Detecting Kodi information.
    20230130010741 - INFO: Detected Kodi running at "******\kodi.exe".
    20230130010741 - INFO: Monitor Count: 2.
    20230130010741 - INFO: Kodi detected at X677 Y191.
    20230130010741 - INFO: Monitor 1 selected.
    20230130010741 - INFO: Loading blank gui at W1920 H1080 X0 Y0.
    20230130010741 - INFO: Starting all LaunchBox procedures.
    20230130010741 - INFO: Attempting to run "*******\LaunchBox.exe".
    20230130010741 - INFO: LaunchBox run successful. LaunchBox is starting up.
    20230130010741 - INFO: Process detected. LaunchBox.exe is running.
    20230130010744 - INFO: Minimizing or exiting Kodi...Done.
    20230130010744 - INFO: Launchbox loading screen detected. Waiting for it to close...Done.
    20230130010747 - INFO: Upgrade pop up detected. Waiting for it to close...

    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. 

  7. 9 minutes ago, oliviergregoire said:

    And it still launch on screen 1 whatever screen I am.

    And  screen 1 is black if I launch it from screen 2, but screen 2 stays normal if I launch it from screen 1.

    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.

  8. 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.

     

  9. 1 hour ago, oliviergregoire said:

    Ok. So it works well with beta 2.

    Just one thing, if I start or place  Kodi on my 2nd screen (I have a computer monitor as screen 1 and a TV as screen 2), Launchbox will start on screen 1 wherever Kodi is . Could you add an option to make it start on the same screen as kodi is placed at the moment you launch Launchbox (screen 1, 2, 3...) ?

     

    Do you want me to also try beta 3?

    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.

  10. 1 hour ago, oliviergregoire said:

    So I did what you said. It works great. Just one thing. When I shutdown Launchbox it restarts Kodi.

    Could it be possible to just hide Kodi when Launchbox starts and then "reappear" where the state was when Launchbox is over? Like when I play a movie, I use an external player (mpc-hc...), the movie starts on mpc, it hides Kodi, and when the movie is over or I turn off the player, Kodi reappears in the state he was just before.

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

  11. 1 minute ago, oliviergregoire said:

    20230122182035 - INFO: Using override path for Kodi "*************\LaunchBox\LaunchBox.exe".

    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.

  12. 19 minutes ago, oliviergregoire said:

    Ok, I did exactly as you said.

    So, it works well for launching (on windows 7) from Kodi (I also changed the start from Bigbox to Launchbox in the addon settings), it starts well, and I can play normally. But when I close the Launchbox window, I have a black screen and nothing happens.

    I had to do a ctrl-Alt-Del to see the nails at the bottom of the windows screen to shutdown Launchbox because neither Launchbox or Kodi appeared in the windows task manager.

    After that, I don't get no longer kodi running. i had to launch it manually. (Sorry english is not my primary language).

     

    Anyway, I thank you CoinTos very much for the addon update.

    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.

  13. 4 minutes ago, oliviergregoire said:

    Thank you very much, I will test it. Where sould I put the file?

    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.

  14. 2 minutes ago, Lordmonkus said:

    The license is still located in the main folder along side the launchbox / bigbox exe files.

    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.

  15. 1 hour ago, Dan79 said:

    I am getting the error that the script requires launchbox premium, which I have, so I'm confused why it's still asking for it. It closes out after I hit ok

     

    Running the latest on the latest with py3

    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.

  16. 2 hours ago, Bedwyr said:

    Should I not be using your python 3 file for 1.5.9? I just downloaded and re-installed/updated Kodi just to be sure and I'm still getting an xbmc.python 3.0 dependency error.

     

    edit: I must have been confused about this before because I had both versions of 1.5.8 in my download directory and regular 1.5.9 worked so that's fixed. But that's still confusing me a bit because I thought that Kodi deprecated python 2.x and only works with 3.x. <scratches head>

    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.

  17. 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.

     

    • Thanks 2
×
×
  • Create New...