Jump to content
LaunchBox Community Forums

CoinTos

Members
 View Profile  See their activity

  • Posts

    169

  • Joined

  • Last visited

 Content Type 

Everything posted by CoinTos

  1. CoinTos
    Yeah, I notice that as well, but it was midnight, complete enough for a test build and I worked in the morning so I posted it but check back Tuesday and I should have a lean mean release candidate to try. True and in the end this plugin will prevail.
  2. CoinTos
    @Ruester Ok so it looks like the UWA addon_data folder is protected by the container and won't allow plugin like this helper exe's to execute inside of it so here is a new test build. Under Advance tab in the plugin settings is a new option called "UWA Fix: Change script EXE save location", enable that and set a folder in the field below somewhere the script can save exe to (ie. c:\scripts\).
  3. CoinTos
    Welcome to the forum and thanks for the post, always nice to hear when things are working properly for users of the plugin. Enjoy.
  4. CoinTos
    I now know why it's not launching... oh and officially I hate UWA. The stupid jail/container it builds doesn't build anything around this script addon executable (compiled ahk script) so the plugin is trying to launch it from a directory that doesn't exist so it's failing. Example: The script tries launching C:\Users\<username>\AppData\Roaming\Kodi\userdata\addon_data\script.launchbox.launcher\scripts\LaunchBoxLauncher-AHK.exe when the script is actually located in C:\Users\<username>\AppData\Local\Packages\XBMCFoundation.Kodi_4n2hpmxwrvr6p\LocalCache\Roaming\Kodi\userdata\addon_data\script.launchbox.launcher\scripts\LaunchBoxLauncher-AHK.exe I will continue to look into a proper solution, time to brush up on my python. Edit: I have a post started on the Kodi addon development forum so hopefully a solution to this can be found.
  5. CoinTos
    Well, it seems like the plugin is launching the script exe so next I need to you try this test version. It will display a pop up for 5 seconds just before the run command for BigBox. If it displays and nothing happens after then BigBox is failing to launch for some reason but I will have a better idea of where it is failing. Make sure there is no previous script is running in the taskbar (launchbox cube icon) and that you use the " delete and update userdata scripts on next run " option after upgrade. Thanks.
  6. CoinTos
    OK so now to debug, are you getting any error popups or can you post a Kodi log so I can see if it is a plugin issue? Any info could help in figuring it out.
  7. CoinTos
    As I got to keep today off I went over the ahk script again. I corrected some errors, commented, formatting, etc, and put some more time in testing on both version of Kodi. One thing I was trying to see if it was possible was the portable mode option, it appears that Windows Store App version does not support command parameter so there is no support for portable mode. So whether you select portable mode or not in the plugin options it will always launch without the parameter for the Windows Store version. If all is working this will be the one that will release as 1.4 official so report any bugs found please. REMINDER ON UPGRADING: Make sure to go in the options and select "delete and update userdata scripts on next run" to ensure you are testing the correct ahk script NOTICE: THE BELOW ATTACHMENT IS A BETA VERSION FOR ANYONE THAT WISHES TO TEST AND REPORT. SEE FIRST POST FOR OFFICIAL.
  8. CoinTos
    @Ruester If you are willing to test I have posted a 'beta' version with support for Windows Store App of Kodi. It works both with the original Kodi installer and the Windows store versions as the need to set your Kodi directory has been removed and a detect has been written into the autohotkey script instead. NOTICE: THE BELOW ATTACHMENT IS A BETA VERSION FOR ANYONE THAT WISHES TO TEST AND REPORT. SEE FIRST POST FOR OFFICIAL.
  9. CoinTos
    No, it's not you. This plugin and ahk script/exe wasn't written to support the Windows Store version of Kodi as that uses the UWA container and is a totally different beast then the regular Kodi windows installer. I do plan to try and support it but was waiting for a stable/RC version of Kodi 17 to make sure they were done playing with UWA container. It will likely require changes to both the plugin and ahk to support it (if it is possible) but I won't know that for sure till I get some time to look into how the container/app works. So at this time, I recommend the standalone windows installer of Kodi if you wish to use the current plugin.
  10. CoinTos
    Open the PlatformWheel1FilterView.xaml in the Futurestate theme folder in a text editor and remove or comment out line 58: <Image Source="pack://siteoforigin:,,,/Themes/FutureState/Images/scanline.png" HorizontalAlignment="Stretch" Stretch="Fill" VerticalAlignment="Stretch" Grid.Column="0" Grid.Row="0" Grid.ColumnSpan="20" Grid.RowSpan="12" Opacity="0.25" RenderOptions.BitmapScalingMode="HighQuality" Panel.ZIndex="2"/> That will remove the scanlines effect only for the platform view.
  11. CoinTos
    I believe he is referring to the second model of Genesis, the compact design like what is shown in the Sega 32x video. If viking has the time and ambition to do it, I too would appreciate it if a second model genesis was available as an option but have no problem sticking with the mega drive video if not. @vikingThanks for the US version of SNES.
  12. CoinTos
    Awesome, one problem I edited my last post late last night with a new revision (17) to fix how launchbox/bigbox handle upgrades. The one you included only assumes 1 upgrade per ahk script launch, but apparently if you are running a beta before the official and there is another beta after the official, it will make you download the official, then offer the beta which break the 1 upgrade assumption. Had to change 2 variables to fix the script to handle that so you just got swap rev 16 for 17 in 1.3 and all is well, no other changes were made.
  13. CoinTos
    @jman85 your image doesn't seem to load when I select it so I can't make out the error. Repost it and I will take a look at it.
  14. CoinTos
    @ashramrak Ok, here is the rewritten scripted with the new updater check. This rewrite also removes the delay at the end of old one when no update was downloaded. Please try it out because I have tried it both on my laptop (i5 with hdd) and htpc (i3 with ssd) but can't get the error message you get to show so I need to know your results to see if my attempt to handle the error works. Edit: File updated to correct the script to handle a situation where you are running a beta, get an upgrade yes/no window to an official but after reloading get another beta yes/no upgrade window. If you had selected yes it would fail to handle it properly as the script assumed 1 update per script launch. My bad, didn't really think about this till Jason released the 7.0 betas.
  15. CoinTos
    Thought of better solution last night for the upgrade monitoring by checking the launchbox updates folder for a freshly downloaded update instead of waiting for an installer to launch thus removing the delay for kodi starting back. So I will submit that for testing in a couple of days. I know why it didn't work for you as well, your systems is faster and I am guessing your library is larger then expected so I should have grouped the winwait check for both error pop up and normal installer window. But there is no point in submitting a fix for that as I am going to rewrite it anyways. If that doesn't work for you then, ah well, we can remove the update check but I am pretty confident that this will cover all of BigBox's behaviors.
  16. CoinTos
    @katsu Basically, I recommend you start a new thread with your requests providing example situations under features forum and see what happens. I say you stand a good chance someone will whip something up.
  17. CoinTos
    If both were a requirement an external program/script would be required as launchbox would be closed. For number 2 only, you could do it with the built in autohotkey script support in emulator's management window.
  18. CoinTos
    Ah, I think I found the issue. Your vb screenshot doesn't have a space after the exe. ie. "DeSmuME_X432R_x64.exe ".
  19. CoinTos
    If the vbs file is in the DeSmuME folder that contains the exe and it's still erroring the same way, try specifying the full path to the DeSmuME_X432R_x64.exe. ie, "C:\DeSmuME\DeSmuME_X432R_x64.exe"
  20. CoinTos
    @katsu For the first message you can uncheck "Always..." and click open it won't pop up there after with Open/Cancel dialog and the second screenshot error is because the script specified "DeSmuME_0.9.11_x86.exe" as the exe and your doesn't match the one in your DeSmuME folder. Change that to match your DeSmuME exe and you will be fine.
  21. CoinTos
    @ashramrak Here is a fix for you to try. It checks for the setup error message and attempts to correct the problem by trying to close BigBoxes process and sending enter to the dialog box.
  22. CoinTos
    @ashramrak Nevermind, I think I misunderstood your error. In otherwords, BigBox hasn't finishing shutting before the installer launches so a pop up with a different title shows and the installer disappears, correct?
  23. CoinTos
    Alright, will look at the splash and upgrade check now. Edit: Actually sound like the delay on setup windows is too short. Can you try changing on line 73 from 3 to 5 and recompile just to check? Edit 2: As I run with solid state drives, the installer loads instantly so 3 second wait after bigbox exits is more than enough but might not be enough for other systems. I might to need edit the kodi script as well to make that an option configurable to set under advance settings.
  24. CoinTos
    Sorry for yet another bug fix but I made a brain dead mistake that showed itself while I was adding a new system to my LaunchBox. Basically, with the splash screen enabled in Big Box the delay between the time when the splash screen closes and Big Box main window shows isn't fixed. This is very apparent when adding a new system because BigBox needs time to load/refresh all the new images before it shows itself causing an unknown delay and therefore a fixed sleep timer was bad idea on my part. Changes: Replaced Sleep delay with WinWaitActive in splash detection to fix it from leaving the check too soon due to varying delay between the splash screen closing and Big Box opening Added link to this forum thread to script header
  25. CoinTos
    @ashramrak Removed 5 second sleep timer as it is not needed if splash is disabled and added check for the Big Box splash screen. If found, it will wait till it to finishes before starting main monitoring loop to prevent WinNotExist detection bug between the time it takes the splash screen to close and big box main interface to start. This will also optimized the script and prevent unnecessary delay due to my last solution as I forgot you can disable the splash screen so that 5 second sleep could cause problems down the road to those that disabled it.
×
×
  • Create New...