totoro

Hi, I´ve noticed the games mixed up with the eXoDOS-installation folder. I got only one Launchbox built and merged my own stuff, eXoDOS and C64 Dreams. How can this be fixed?

Solved it by myself. If anyone else encounters this: mark all and hit F5 (update graphics).

I've followed the merging instructions, but for some reason boxart is not showing up. The 3D-model seems to grab it somewhere in the details. What am I missing?

Thank you, this worked for me as well. 👍

Constant error message pops up when certain games are selected after updating to 13.15: Year, Month, and Day parameters describe an un-representable DateTime. App: LaunchBox Version: 13.15 Theme: Default Type: System.ArgumentOutOfRangeException Site: Void ThrowArgumentOutOfRange_BadYearMonthDay() Source: System.Private.CoreLib at Unbroken.LaunchBox.Search.LocalDbSearchResultGame..ctor(DbGame game, String region) at Unbroken.LaunchBox.Search.LocalDbSearchResult..ctor(DbGame game, String region) at Unbroken.LaunchBox.Search.LocalDb.GetGameById(Int32 id) at Unbroken.LaunchBox.Windows.Data.GameSuggester.GetSuggestions(GameBase game, Int32 max, Boolean allowSameDbId) at ConfigCollectionProducer.InstantiateObservableWrapper(Object , GameBase game, Int32 max, Boolean allowSameDbId, ConfigCollectionProducer ) at Unbroken.LaunchBox.Windows.Data.GameSuggester.GetSuggestions(Int32 max, Boolean allowSameDbId) at Unbroken.LaunchBox.Windows.Desktop.ViewModels.GameDetailsViewModel.ManageCompositeUtils() at Unbroken.LaunchBox.Windows.Threading.<>c__DisplayClass0_0.CancelStatelessParameter(Object ) at Unbroken.LaunchBox.Windows.Threading.<>c__DisplayClass0_0.ReadMultipartDic() at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() Recent Log: 12:04:32 Exception This does not occur in Big Box mode.

I just finished my OpenBOR collection and can absolutely NOT recommend to merge paks into one build. While 70% of all games might run, a lot of games break if the used build is too new or too old when the game was developed. Remember, this is a game engine, not an emulator. Also, some games do not come in pak-, but in files-format. I used a very late v3 build, tested out if the game worked and looked alright without crashing, renamed the exe to the game title and imported all exe-files into Launchbox later on. If a build didn't work, it was ALWAYS because the OpenBOR build needed to be lower. So I worked through some older builds until it worked again - even then sometimes I had to use the OpenBOR exe provided with the pak-file instead. It's also important to create control configs for every OpenBOR option and rename the .cfg file in the Saves folder into "default", before you create new copies. That way you don't have to map keys everytime. Sadly those Default-Files are build-dependant, so you have to go through these for every OpenBOR option. I hope this helps anyone trying to get OpenBOR up and running.

Can you recommend a default controlling scheme for xbox gamepads when all buttons need to be mapped and which works for all games? Normally I would use the facebuttons, but sometimes there a too many actions... attack attack 2 attack 3 attack 4 jump special block I'd like to create a standard for every game and copy/rename the config files, as I don't want to go through every game/options menu.

Well, technically it's the same table with two different emulators/filetypes. But I guess the graphical appearance is quite different, so it's probably best to separate them.

Yeah, so how did you do it for your collection? Add an additional version for each table, choosing future pinball as emulator I guess? Maybe there is a bulk edit method to it instead of doing one table at a time, thats what I was wondering.

Thanks, I always download the backglass files as well to have everything ready for a 3-screen setup somewhen. After watching some Future Pinball videos I must say some tables look quite good, so I guess I will add this later on as a second option for some tables. I would like to import all table filetypes of both emulators in one run when everything is ready, to combine more than one table. Is it possible to tell launchbox "if vpx-Filetype, run with vpx" and "if future pinball-filetype, run with future pinball"?

Thanks for the writeup, this helps a lot. I did it like you guys and created extra folders per table to keep things organized. The only part I did differently: I've kept the version of the table in the folder name while renaming the vpx-file "Launchbox-Database-friendly". While the Baller Installer is a great option, I went the "hard route" as troubleshooting is far easier when you know how things are tied together. I guess I would use it on a cab though. While the whole software part is not portable... I guess if I run the baller installer on a new machine and copy the game-related folders (tables, roms, music, nvrams), it should at least boot up the table just like before, right? My idea is to make sure every table is running without errors, copy this game related stuff to a fresh install on a cab somewhen and "only" walk through the tables one more time to correct screen postions. Should this work or do I have to start from scratch?

Thanks. I was wondering about 2 things while setting things up: 1. What about portability of all of this pinball software stuff? I've installed everything into my Launchbox/Emulators directory but especially these additional DMD setups seem to write something into the windows registry. I try to keep everything portable in my LB built. Just changing the directory name from "Visual Pinball X" to "Visual Pinball" already broke everything and tables didn't run properly anymore. 2. Some games come with backglass files or media. I was wondering how your "tables" folder should look like? I mean is it better to just keep the .vpx and backglass files in the tables directory or did you create subfolders for each one including extrafiles like ultradmds or whatelse not. I noticed things get pretty messy if I just unpack every table in that folder if I don't check for extra files. Not sure what to keep. I think music files, if existing, are stored in the main directory, but some seemed to need subfolders whole others didn't. In the end most of the tables run but I'm a little lost whats the best folder structure to hold everything together nice and tidy.