-
Posts
13,723 -
Joined
-
Last visited
-
Days Won
388
Content Type
Profiles
Forums
Articles
Downloads
Gallery
Blogs
Everything posted by Jason Carr
-
I think this is a known issue, probably due to how we use and process images in LaunchBox vs. Big Box. I'm sure it can be fixed, but it hasn't been a priority as of yet. If you can report a bug for it though on BitBucket, I'd appreciate it.
-
Yes, LaunchBox updates will overwrite changes to that file.
-
BigBox crash while sitting idle doing attract mode
Jason Carr replied to MrSco's topic in Troubleshooting
Thanks @MrSco; that error message should definitely be helpful. We'll dive in. -
Glad to hear it @morgan999. Most likely a driver update or a Windows/Microsoft update fixed the issue for you.
-
Oh, should probably post this on Bitbucket if you haven't already as a feature request.
-
Thanks @legamin, noted. I agree that those would be good options.
-
I have gotten a couple of BSODs since the update, sigh. But I wasn't running LB or BB at the time, so mine are unrelated, at least. Are you still having this issue? My guess is that it's unrelated, but I can't say for certain. Do you have debug logging enabled?
-
It's the last item in the top 20, which are the ones that won the top half of the votes. We never intended to tackle all of the items.
-
Hey all, the first 11.12 beta is out now here:
-
Hey all, the first 11.12 beta is out now with the following: Fixed: Potential error in Big Box when switching view types and then navigating too quickly Fixed: For theme developers, the FlowControl SelectedScale property was not working with CoverFactory Fixed: On rare occasions, Epic image downloads were not saving correctly due to inconsistences with game images on Epic's servers Fixed: Errors for some users with the Edit DOSBox Configuration window (introduced in 11.11) We are currently working on the last item from the poll as well: Icons for Types of Controls (Keyboard/Mouse, PS4/Xbox Controller, Wiimote, Nunchuk, etc.). We still have some work to do on that, but I wanted to get a beta out because of the above fixes.
- 133 replies
-
- 10
-
-
-
-
Hey all, @faeran put this out and it's tremendously helpful and informative:
-
BigBox crash while sitting idle doing attract mode
Jason Carr replied to MrSco's topic in Troubleshooting
That is really quite interesting. It's been ages since I've tested with FLV files, so that could actually be the culprit. We'll investigate. -
Just removed it.
-
You should be able to change the backgrounds just by replacing the images in the LaunchBox\Themes\Unified & Ultrawide\Images\Theme\Background folder.
- 53 replies
-
- criticalcid
- unified
- (and 4 more)
-
Responded to @Joe35car via PM, but to clarify, the MAME arcade full set importer will always prioritize the selected region, even if you choose "skip clones". This will make it pick the best ROM for the selected region to prioritize. It will not just import the parent games. Back when this was all built, in our discussions, no argument could be made for the benefit of importing only "parent" ROMs. Generally, it's best to ignore that and prioritize region and other factors (like officially released versions).
-
Version 1.0
1,693 downloads
LaunchBox Shell for DOSBox is a single EXE file that you can copy next to an MS-DOS game to automatically and easily be able to play and install it. The focus here is on ease of use, portability, and easy distribution. Why was this built? I built this because I wanted to upload some old abandonware MS-DOS games to archive.org, and I realized that most users would have difficulty playing them without some help. I built LaunchBox Shell for DOSBox to be able to be easily distributed with a single MS-DOS game to make it exceedingly easy to play. In addition, I wanted to preserve the entire MS-DOS experience, including the installation program. LaunchBox Shell for DOSBox can be distributed next to a CD image (ISO or BIN/CUE) file and automatically help the user run the installer and then play the game. System Requirements LaunchBox Shell for DOSBox runs on the .NET Framework 4.6, which is automatically included on every install of Windows 10, and is already installed on most Windows 7 installations. Therefore, you should have no problem just distributing the "Play with DOSBox.exe" file only, and it should just work on all Windows 10 systems (and most Windows 7 systems). No other libraries are required for it to run. How to Use In general, using LaunchBox Shell for DOSBox is as easy as putting the "Play with DOSBox.exe" file next to the game files and launching the EXE. That said, there are a number of caveats and best practices, so it's best to follow the steps from one of the three sections below, depending on what type of files you're using. How to Use with an ISO or BIN/CUE CD Image File If you have an ISO or a BIN/CUE CD image file of the original MS-DOS disc, do the following: Rename the ISO or the BIN/CUE files to match the full name of the game. Make sure that you update the path to the BIN file in the CUE file if you change the name of the BIN file (the CUE file can be edited with a text editor). Copy "Play with DOSBox.exe" into the same folder as the CD image files. Download a screenshot of the game (in either PNG or JPG format) and place it also in the same folder (ideally also rename it to match the full name of the game). This step is optional; no image will be displayed in the app if there is no image in the folder. Run the "Play with DOSBox.exe" file and test installing and playing the game to make sure that it works properly before distribution. If distributing, delete the "DOSBox" and "Game Files" folders that were created in order to save disk space (or you may keep them so that the user does not have to run the MS-DOS installation program). How to Use with MS-DOS Game Installation Files If you have the MS-DOS installation files for a game, but do not have an image of the original media, do the following: Create a new folder and place the "Play with DOSBox.exe" file into that folder. Create another new folder inside of the above folder, and name it with the full name of the game. Place the MS-DOS installation files inside of this folder. Download a screenshot of the game (in either PNG or JPG format) and place it in the same folder as the "Play with DOSBox.exe" file (ideally also rename it to match the full name of the game). This step is optional; no image will be displayed in the app if there is no image in the folder. Run the "Play with DOSBox.exe" file and test installing and playing the game to make sure that it works properly before distribution. If distributing, delete the "DOSBox" and "Game Files" folders that were created in order to save disk space (or you may keep them so that the user does not have to run the MS-DOS installation program). How to Use with Already-Installed MS-DOS Game Files If you have the installed MS-DOS game files, but do not have the original media or the game's installation files, do the following: Create a new folder, name it with the full name of the game, and place the "Play with DOSBox.exe" file into that folder. Create a new "Game Files" folder inside of the above folder, and place the installed MS-DOS game files into that folder. Download a screenshot of the game (in either PNG or JPG format) and place it in the same folder as the "Play with DOSBox.exe" file (ideally also rename it to match the full name of the game). This step is optional; no image will be displayed in the app if there is no image in the folder. Run the "Play with DOSBox.exe" file and test playing the game to make sure that it works properly before distribution. If distributing, delete the "DOSBox" folder that was created in order to save disk space. Known Issues Currently, multi-disc games are not supported. This is planned for a future release. Games that run straight from the CD and don't copy any EXE, COM, or BAT files over to the hard drive do not currently work. A fix for this is also planned for a future release. Game disc images that don't have an install or setup file in the root of the disc will not currently work; these game discs are relatively rare, but they do exist (usually they're discs that include versions for both DOS and Windows). A fix for this is planned as well. Support for floppy disk images is planned, but not yet available in version 1.0. The goal of this application is to make as many games as possible "just work" without any custom configuration; however, there are bound to be games that do not. If you run across one of these games, please report it in the Comments section, and we'll do our best to make it work for the next version. You can also try the Debugging section below. Debugging If a game is not working, it's usually because the game's installer or game play application can't be found, or the wrong application is chosen. Until we test every single MS-DOS game out there (not really possible), this will always be an educated guess. If a game isn't working, here are some troubleshooting steps: Go to the Advanced Configuration tab, and then the Debugging tab, and uncheck the box to "Automatically Exit DOSBox". This will allow you to see any error messages that appear on screen. In the same tab, check the box to "Show MS-DOS" commands. This will allow you to see the commands that LaunchBox Shell for DOSBox is running, and it might give you a clue as to what the issue is. Start the game (or the installer) and observe any error messages that come up. Most likely these are the result of the wrong startup files being chosen, so type "DIR *.EXE" (without the quotes) and press Enter to see what files are available. If you see a file like looks like the right file instead, go ahead and type that file name and press Enter, which may make the installer or the game work. However, you will need to do this every time to start the game, so please report the issue in the Comments section so we can fix it. If no EXE file is found that works or makes sense to run you can try typing "DIR *.COM" or "DIR *.BAT" and pressing Enter instead. You can exit DOSBox by typing "EXIT" (without the quotes) and pressing Enter. FAQ Doesn't LaunchBox already do this? Yes, but it doesn't work well to distribute with games, for obvious reasons. In addition, there are some improvements to the way games are handled that are not yet in LaunchBox. We plan to integrate the changes here very soon, however. How does LaunchBox Shell for DOSBox determine the name of the game that is displayed? It does its best to gather it from wherever it can. When using a disc image, it will take the game's name from the file name of the disc image. When using installation files, it will take the game's name from the folder name of the installation files. Otherwise, it will try to get the game's name from any image files, or from the name of the parent folder. How do I save the DOSBox configuration for distribution? If DOSBox needs a custom configuration for the game, you can tweak the settings under the Advanced Configuration tab. When you play or install the game, those settings will be saved to any "dosbox.conf" file that is found anywhere inside of the application folder, or a new one will be created in the DOSBox subfolder. To save these settings for distribution, you can simply distribute the dosbox.conf file with the game. The dosbox.conf file can be kept either in the DOSBox folder, or in the root application folder. However, it is not advised to place it in the "Game Files" subfolder, as that folder is removed when the game is uninstalled via the interface. Can I use a custom version of DOSBox, such as an older version or a distribution like DOSBox-X? Yes, you should be able to use any custom version of DOSBox, though we have not tested it against any other versions. The version that is included inside of the "Play with DOSBox.exe" file is DOSBox 0.74-3 (the latest version at the time of this release). To use a custom version, simply overwrite the files in the DOSBox subfolder (these files are created whenever you install or run the game). LaunchBox Shell for DOSBox should not overwrite any custom DOSBox files that you place into this folder.- 2 comments
-
- 10
-
-
-
-
It doesn't do all its saving on startup/shutdown. It *does indeed* save things as they are updated.
-
Beta 3 is out now with the following: Fixed: Corrected performance issue in Game wheels introduced in 11.11 beta 2 Fixed: Corrected positioning issue with FlowControl using NavigationRows or NavigationColumns Fixed: Wheel easing is now functioning (introduced in 11.10)
-
Thanks @drphobus. Good to know. We'll do some investigating.
-
This is an EmuMovies error. Please report it to EmuMovies support.
-
@atbc Please create a new forum post for this and we can help you out. You can call me out with @Jason Carr to make sure that I see it. We'll need to enable debug logging so we can get an actual useful log.
-
Beta 2 is out now with the following: Improvement: For theme designers, FlowImage now has a CreateFallbackImage property to turn off the fallback image loading if the item doesn't have the image type you are requesting Updated the EmuMovies integration code to be a bit more resilient and make any errors more clear Various fixes for the updated wheels/CoverFlow/wall views Fix for the right click icons issue
-
Okay, well, somehow, something on the system is corrupted. It could be drivers or .NET Core or the .NET Framework installation, so you might try uninstalling and reinstalling those. Beyond that, it could somehow be DirectX, I suppose. I'm sorry I don't have any better steps to resolve.
-
Yes, I don't know of a way to replace the options list with graphic buttons for the TextGamesView, at least not without us programming a new version of the view, unfortunately. I will put that on my list though.
-
Off the top of my head, unfortunately I don't know of a way to do this. You might have better luck asking in the XAML Tips and Tricks thread though.
- 53 replies
-
- criticalcid
- unified
- (and 4 more)