CoinTos
-
Posts
169 -
Joined
-
Last visited
Content Type
Profiles
Forums
Articles
Downloads
Gallery
Blogs
Posts posted by CoinTos
-
-
3 hours ago, Aurel said:
@greengriffon : @viking already made a very nice Sega Megadrive vid you can use as a genesis one. As far as I know, they're very (very) similar in shape and color. Am I wrong?
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.
-
2 hours ago, ashramrak said:
Worked for me as well on both my laptop and htpc, so I just updated the OP with the new version of the addon
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.
-
@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.
-
@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.
-
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.
-
@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.
-
6 minutes ago, katsu said:
@CoinTos OMG I got it working bro thank you so much!
I suffered a lot of sleepless nights figuring this out and thanks to you it's finally fix And since you've been very dependable, I hope you can also provide a solution to some of this questions/wishes:
1.) Do you know a way that when I double click the game it automatically closes the LaunchBox program/window?
2.) And also do you know a way that when I want to close the game i just press esc on the keyboard and it closes the emulator completely?
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.
-
Ah, I think I found the issue. Your vb screenshot doesn't have a space after the exe. ie. "DeSmuME_X432R_x64.exe ".
-
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"
-
@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.
-
@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.
-
@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?
-
17 minutes ago, ashramrak said:
I tried it and kodi opens right away as soon as the LB upgrade window is displayed (setup has detected that launchbox is currently open, blablabla close it then click ok to continue)
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.
-
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
-
@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.
-
1
-
-
3 hours ago, Charco said:
What are the benefits of the new addon? I haven't had any issues with the current one I have as it boots to Big Box and when I hit exit it goes back to Kodi without any problems.
Depends on what you are comparing it to. As far as compared to the 1.0 version of ashramrak:
- All irrelavent code from the steam autohotkey script he modified has been removed.
- An updater check was written by me to make sure if the installer was running Kodi wouldn't be relaunched as BigBox will be restarted once the install completes.
- The script was written to remove GOTO calls and to make understanding flow easier.
- A clean up check to make sure Big Box was closed after Kodi brought back to focus by the script.
- Was commented to help those learning/editing/recompiling the autohotkey script know what or where they might want to modified for their own setups.
The big plus of this was to get a uniform plugin that both ashramrak and I will support.
@ashramrak maybe you should submit it to the downloads for third party plugins and we will break from this thread and support it under it's newly create thread to save confusion.
-
6 minutes ago, SentaiBrad said:
So some features that were made for BigBox also run in LaunchBox, and improvements to the software can benefits both in a lot of ways that users may not see right away. Jason is just one man, and it is split 4-5 different ways (if not more), so he and I appreciate the patience and support.
Agreed and that was basically the point I was trying to make. It's hard to be in the middle as an army of one (Jason) and trying to make everything make sense or support both side at the same time. I was just trying to show the point from the other prospective of it. Hopefully, it was in an appropriate as possbile way to support development and support patience.
-
Just now, ashramrak said:
will check it out this weekend !
are you on kodi 16 or 17 ? I still didn't upgrade waiting for a release candidate
Everything is tested on an i3 system with a solid state drive running Kodi 16.1. So if there are bugs outside of that system I can modify as needed but this script is rewritten to account for slower systems and faster system should not be affected.
-
1 minute ago, Drybonz said:
I agree... Structural improvements are the most important thing.
Voice recognition.
You can't really pick on that Voice recognition, I as well, have no use for it but he stated in his feature video for it that he was working it long before launchbox and good on him for finally putting it to use. Now back to your statement about you following the changelog for Launchbox vs BigBox. I am the otherside of the coin I support the BigBox side of the changelog as I use a 10ft approach and only use the launchbox app for scraping. Jason has the double edge knife problem of supporting both you and I in his development. If optimization is the course required currently, I think we should let the few features slide on either side and both support/follow the performance side for the time being as that seems to be the appoarch he is taking. Features are nice but it running well on all systems is key in both modes, that is really key in the end.
-
Ok so here is a very small bugfix update... my bad. Under random starts of the script, it would detect the bigbox window as not existing break the monitoring loop. This was caused by it getting to the monitoring loop too quickly. I thought I had had this squashed with the 2 second sleep timer before the loop but that wasn't enough time apparently. So this version has it set to 5 seconds and it appears the problem is now solved as I can no longer recreate it on my setup.
-
30 minutes ago, ashramrak said:
awesome, I really love the idea that that its handling bigbox updater properly !
I'll look into it asap, very busy at work for now
I'll also make sure to credit you properly in the changelog of the addon ! or you could also repackage it yourself and put your own name in the author field; it's not like I'm the original dev of the plugin or anything
I know all to well the busy at work part, finally got a day off to write that ahk but for now, you can remain 'project lead'
and I will just forward on my modification and bugfixes as I really don't feel like maintaining a Kodi package at the moment. If you lose interest, I will then repackage but for the time being, the extra set of eyes is beneficial.
-
As promised, here is the ahk script source and compiled exe as I heavily modified the script. Everything that doesn't relate to BigBox has been removed and an update check has been added so you can use the bigbox updater without being kick back to Kodi when the installer launches. I also commented it but that is just out of habit.
Let me know what you think.
-
1
-
-
14 hours ago, ashramrak said:
like mentionned above this addon is a really quick and dirty copy/paste of teeedub's steam addon so to be honest I don't know
No worries, in a couple days I'll clean it up and post a heavily modified version that is tailor more to BigBox for you to look over.
-
One more small correction you may want to check as I forgot to include it in file. In the process exist ErrorLevel block before you 'Send {Esc}' you have WinWait, you probably want to use WinWaitActive as you mostly don't want to send escape till the window is truely in focus. Now, this is just out of curiousity but why the need to send escape if the process and window already exists and have been brought to focus?
I'll also make sure to credit you properly in the changelog of the addon ! or you could also repackage it yourself and put your own name in the author field; it's not like I'm the original dev of the plugin or anything 
Futurestate Theme
in Big Box Custom Themes
Posted
Open the PlatformWheel1FilterView.xaml in the Futurestate theme folder in a text editor and remove or comment out line 58:
That will remove the scanlines effect only for the platform view.