thedevilsjester

When scrolling through the list of games, BigBox will often just stop scrolling and then sit there for a few seconds until it eventually loads the box art for the currently selected title. Sometimes it stops for half a second, so its just stutter, and sometimes its 5+ seconds. There is currently a thread on this forum that discusses this (as well as someone posting a video that has the same behavior that I am experiencing), but its been locked. I have an Intel i7 7567U with a Intel Iris Plus 650 and 16 GB RAM, running off of an SSD in Windows 10. No other applications or services are running. I am using the default theme. I really like BigBox and I think the configuration design in LaunchBox is unmatched, but its unusable in its current state. What can I do to fix this that doesn't include disabling most of BigBox's features?

Are you sure that this is true? I have loaded over a dozen platforms and most of them have individual ROMS in folders, some are even categorized by folder, and just adding the top level folder has worked every time. The only time I have used the search function is when I have some files that I do _not_ want to include (like with bin/cue).

I saw a similar one on a website for AutoHotKeys but I was not able to get it running through LaunchBox (I am not familiar enough with the AutoHotKeys syntax and variable expansion). I am curious if anyone has gotten similar working with LaunchBox's AutoHotKey script area as it would just make everything so much simpler to only deal with LaunchBox.

Anecdotally, everyone I know that wants a front end, wants a controller/couch based front end. Like me, many of them have run the gamut of front ends that provide this, have found them lacking, and end up here. Unfortunately, if this is what you want, a nice console/couch based experience, there is no way that you can try this out without first purchasing BigBox. There is no demo or trial of any kind. I very nearly skipped past LaunchBox because of this. Trying out LaunchBox will give you an insight on the quality of the application, how easy it is to configure (even if you use BigBox, all of your configuration will be done via LaunchBox) and the plethora of options, pre-sets, guided wizards, and other things that really make the system shine and stand out from the competition. For what they are asking, it is very much worth the cost of entry. Buy the $20 license, and if its everything you want, or if you want to support the developers to make it better, upgrade to to the $50 license (they have an upgrade option).

Beware of using any remapping tools when running emulators because they add considerable latency to the controller input. Usually polling is set to around 10 ms so all of your input is delayed by 10 ms on top of what the emulators already do (this is roughly 10x the input latency that emulators strive for). You can often configure the polling interval to be smaller, but the more often you poll, the more CPU it eats up. You might not realize that this is why that jump is always just a little bit too late, or that you could have sworn you dodged that shot, it could be your timing, or it could be the additional latency of a remapping application. My personal use case (the rare but required input on some DS and 3DS games) does not require any reasonable input latency, but if you are mapping/remapping inputs it will definitly slow the input responsiveness of your game. I already know about additional apps that can achieve this, I used them prior to installing LaunchBox because of the Esc/Alt+F4 requirements to exit some of the emulators. LaunchBox has eliminated the need to have yet another application polling for input in the background for most of my use cases, I am just hoping that it can be used to remap an analog stick to the mouse, so it can do all of the remapping I need.

Has anyone played with getting an AutoHotKey script to map an analog stick to the mouse for certain emulators like DeSmuME and Citra?

I am trying to get BigBox into a restricted "kiosk" mode. BigBox has a "Lock" mode, but it seems that if I disable the ability to exit BigBox (to the desktop), I also lose the ability to restart/shutdown. I want the benefits of the Lock, but I also want them to be able to safely shut the box down from within the app. Is there a setting that still allows this, or should I be filing this as a feature request?