Jump to content
LaunchBox Community Forums

Dolce Ardore

Members
  • Posts

    10
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Dolce Ardore's Achievements

8-Bit Processor

8-Bit Processor (3/7)

2

Reputation

  1. Is it possible to turn off this new feature? It makes importing new items painfully slow.
  2. Sadly it won't run at all when launched outside of Steam. Not sure if this is a DRM thing or what.
  3. Thanks for your reply. Unfortunately, this does not work, because the LaunchBox window is only temporarily activated, and the Steam window is re-activated again after a second or two. This is because when the BigBox.exe process terminates, Steam assumes that the "game" has closed and returns the user to the Steam launcher. Even without this issue, having to use Ctrl+B or the LaunchBox menu within SteamLink is rather painful. The best solution I have come up with so far is to create a KillLaunchBox.bat batch file, add that as a Non-Steam Game, and then launch it from Steam when I need to kill LaunchBox in order to run BigBox. Of course, this is pretty clunky and runs the risk of issues if LaunchBox happens to get killed in the middle of updating its database or other persistent state. If BigBox could gracefully terminate LaunchBox when it is started, that would be an almost ideal solution. KillLaunchBox.bat
  4. When I have LaunchBox already running on my system, launching BigBox.exe activates the LaunchBox window but it does not switch into BigBox mode. Is there a way (maybe a command-line switch?) to make it so that launching BigBox will open BigBox mode even if LaunchBox is already running? (The reason I am asking is that I want to use BigBox via SteamLink.)
  5. After a mass import, I end up with a lot of items in LB that couldn't find any match in the master LB database. Then I rename each of the files so that it ends up getting the correct match. That way I know I have a good filename for when I need to import in the future into either LB or some other launcher.
  6. Yes.... if LB kept some sort of hash for each file in its database, then it would be able to automatically update itself to point to the new file names.
  7. Thanks... though it would be nice if LB could rename the file for me, editing the file name in LB and then doing the same in Explorer is literally about 10X faster than what I was doing! Thanks a lot.
  8. I run into quite a few rom files with bad file names. Once a rom has already been added to LaunchBox, what is the quickest way to change the filename and sync the updated filename with LB? Note that I want to change the actual file name, not the title in LB. Right now, I do this: (1) Rename the file (e.g., in Explorer) (2) Delete the rom from LB (3) Drag and drop the renamed rom file from Explorer into LB and go through the import wizard with its many steps. This takes quite a white. Surely there is a better way?
  9. I tried adding the mount to the [autoexec] section of the main DOSBox config file (in ...\LaunchBox\ThirdParty\DOSBox\dosbox.conf) but that didn't didn't work when launching a game (only works when not launching a game). I also tied creating an individual dosbox.conf file for a game but that also didn't work. For the two games I've tried so far (Doom and Doom II), I get mono music from the GUS like you say, but when I use the PLAYMIDI GUS utility to play a midi file, I get stereo. So I think it may be an issue with the game rather than with DOSBox.
  10. I think they broke it somewhere along the line by adding in the "feature" to ignore the autoexec commands in the default DOSBox configuration file, which is where you're supposed to add the MOUNT command for the Ultrasound files. Was driving me mad trying to figure out what was wrong, since when I open DOSBox from LaunchBox without running a game, it runs the autoexec and everything is configured correctly.
×
×
  • Create New...