Jump to content
LaunchBox Community Forums

Jason Carr

Administrators
  • Posts

    13,723
  • Joined

  • Last visited

  • Days Won

    388

Everything posted by Jason Carr

  1. Hi @ianrace, would it be enough to just always make the Extras folder path be the same as the Game Data Path?
  2. Thanks guys. @scree, I need help figuring out that error. What was the error you saw? Martin, so there's a conflict between LaunchBox AutoHotkey and Big Box AutoHotkey settings you think?
  3. Hmm, the question is...do we need it to be game-specific? I probably need to add default scripts for DOSBox, ScummVM, and Windows games. But then, from there, do we need game-specific scripts as well?
  4. Hi @CrystalForce, you raise a great point. I hadn't thought of that, but you're very right. Might as well add it while I'm in here. ;)
  5. Hi @scree, yes; the new beta no longer requires the AutoHotkey.exe file for the AutoHotkey functionality (it now uses a DLL, which solves some of the previous issues users were seeing). So I delete the file just to clean that up. I just put out another new beta with default scripts for all the default emulators. They make it so that all default emulators now close out properly with the Escape key. There is more functionality that I'd like to add, but this is a start for now. I'm also planning on adding the same functionality to DOSBox, ScummVM, and Windows games. Though there will be no default scripts for those, likely. Also, for what it's worth, a list view is on its way. I have a very basic version of it working, but it's not accessible in this current beta. Stay tuned.
  6. Hi @mattsoft, indeed there is. Just select all the games you want to change (easiest way is to press Ctrl+A to select them all), then right-click and Edit. That will pull up the Bulk Edit Wizard. You can change the Emulator field there for all of the games at once.
  7. Thanks @ianrace, got it. I will add that to my short list. :)
  8. Interesting; I guess the command line parameters changed then? It looks like the LaunchBox default command line parameters are blank for MAME, actually.
  9. New beta to address an issue with the AutoHotkey changes; errors come up if multiple instances of LaunchBox and/or Big Box are running. This is problematic anyway (has a chance to cause data corruption), so I've put safety checks in place to make sure that no two instances can run at the same time. Does this cause an issue for anyone? If I remember correctly, some people might have been using nested instances.
  10. Thanks @JBourne21, glad to hear there's progress at least. I believe the error you're getting in Big Box is due to running LaunchBox and Big Box at the same time, or running multiple instances of one or the other. I'm going to add some safety checks to make sure that can't happen; hopefully that will resolve the issue. Per PCSX2, one of the things I did with the AutoHotkey revamp was to add emulator-specific AutoHotkey scripts, so that those can be used to solve problems like that specifically for each emulator. So today I'm going to be working on coming up with those scripts. :)
  11. Hey all, I just re-vamped AutoHotkey for the latest beta. @JBourne21, can you test it now? The glitch you mention above with the hold button is still there, though. That's a separate issue.
  12. Hey all, I just added custom AutoHotkey scripts to emulators in the latest beta. @eric, I put your Demul script in as the default script for Demul, works great.
  13. And we have another new beta. This one is kind of a big deal. I've added custom AutoHotkey scripts to emulators; this should allow us to do things like make sure that the Escape always works for every emulator. We'll just need to put together default scripts for every emulator. Beyond that, it should provide some awesome flexibility options, if you're interested in diving into the scripts. I also removed the "v" when displaying versions. I chose to do that for flexibility; I figured people can put the "v" in themselves in the version field if they feel the need to do so.
  14. Bah, that sucks. And holy crap. Lol.
  15. Thanks @Nickjs and @DOS76. To clarify in case anyone stumbles on this thread, LaunchBox by default won't import duplicates if the ROM file is already in your collection. You can override this though by checking the box to force duplicates.
  16. What @garbanzo said. That System/BIOS path had me up in arms for hours.
  17. Hi @ianrace, that's interesting; I wasn't aware of that extras folder. LaunchBox doesn't specify an extras folder via command line when it runs the EXE. The command it runs looks like this: ScummVM.exe -f --aspect-ratio --no-console --savepath="[ScummVMFolderPath]" -p "[GameDataFolderPath]" Could it be the savepath?
  18. The beta testing thread is the thread that I update regularly with the developments for each new beta: https://www.launchbox-app.com/forum/features/launchbox-beta-testing That's probably the best place to go. You can subscribe to that thread. :)
  19. Hi @MultipleX, thanks for the feedback. Not a bad idea on #1; it's not a big priority right now but I will add that to the list. Different views for Big Box are definitely coming. The wizards do actually have a back button in the upper left (the wizards use Microsoft's new wizard format introduced in Vista).
  20. Yeah, I can see that being a problem with the emulators. I wonder if anyone's ever come up with a solution for that...anyone know if Rocket Launcher does anything for that?
  21. Oh man, there goes *all* my productivity.
  22. Yeah, this is on my to-do list. However, I have noticed that if I open Big Box from a shortcut on monitor #1, it will open on monitor #1. If I open Big Box from a shortcut on monitor #2, it will open on monitor #2, at least for me on Windows 10. You can test this by opening up Windows Explorer (the file explorer) to your LaunchBox folder. Drag the window to one monitor and double-click on BigBox.exe. Then drag it to the other monitor and do the same thing. I realize this is still an issue though and I will get it fixed.
  23. I only see one payment from you, actually. So not sure what happened the first time around but it looks like it didn't go through. I guess that's why you didn't get an email at first. What you could do for the import, is import them all now, and then just delete the games that didn't pull information (you can filter by TheGamesDB.net ID). Then you can re-import them all later once we have the new solution, and it will skip over the games that already exist. I hope to get to that import thing soon, but I can't make any promises as to when at this point. Custom filters exclusions are another thing that I still need to tackle.
  24. Hi @crimsonnight, sorry for the delay; I went to bed shortly after posting that. It looks like the email went out to you last night on schedule. I just re-sent it again. Let me know if you receive it.
  25. Hi @crimsonnight, per PayPal, I've switched it to use a different payment provider, but the old page is still cached for some people. Try pressing F5 to refresh the page. The automatic matching is tricky because it's easy to make matching mistakes if we get too lenient in the matching process. That said, I know it's not ideal. I have an item on my list to allow you to go through non-matches at the end of the process and easily choose the item to match them to.
×
×
  • Create New...