Dybdal

Your a superstar Joe, works like a charm. You made someone's day

Hey everyone. Got a bit of an issue helping a mate setup an emulator inside Launchbox that has somewhat of a unique problem. The issue is around the way Launchbox structures its command line. Emulator.exe -command -command "FULL\PATH\TO\ROM\FILE" /command <- is what i need the command line to look like. Emulator.exe -command -command /command "FULL\PATH\TO\ROM\FILE" <- is what im getting and the emulator is not happy about the /command line being behind the romfile. Is there a %command% to tell LaunchBox where to place the "FULL\PATH\TO\ROM\FILE" ?

Sorry for the slight delay in response, obligations got in the way. Did some short tests and it does indeed seem to be related to favoriting a game, then swapping quickly to the next game.

Favoriting stuff, clicking around on games, anything that causes the database to be read. Im thinking this is a borked install on my end, if others arn't having it. reason why i decided not to bug report it. It's all singular actions taken that causes it, so im thinking someone else would have dealt with the same issue is this error was fixable on your end.

Need to know if this is just my installation thats buggy or if its a common thing, before i bug report it. Getting this bug every single day. Object reference not set to an instance of an object. App: LaunchBox Version: 13.20 Theme: Default Type: System.NullReferenceException Site: Void RunMultipartPublisher() Source: LaunchBox at Unbroken.LaunchBox.Windows.Desktop.ViewModels.GameDetailsViewModel.<>c__DisplayClass620_0.RunMultipartPublisher() at Unbroken.LaunchBox.Windows.Data.DataManager.<>c__DisplayClass189_0.FlushMultipartTask(Object) at Unbroken.LaunchBox.Windows.Data.DataManager.<>c__DisplayClass189_0.RemoveStatelessCallback() at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location --- at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) Recent Log: 23:01:42 Exception

Same issue. Fix was to remove both "ScummVMImport.dll" and the folder "ScummVM LaunchBox Integration" from the plugin folder

And another development to keep an eye on, is the View-Master Interactive Vision. It's a 3rd gen VHS console, that has had all of it's VHS tapes found, dumped and remastered on archive.org A project around those tapes should see completion this year. Think that's about it for all the stuff worth mentioning.

And a few weeks ago someone posted a simulator for the last remainging un-emulated or simulated VHS console from SEGA, the SEGA Video Driver/Family Driver.

Another new system got it's first emulator last year, the LJN Video Art.

Also worth mentioning is that the MAME team managed to emulate the "Gakken Compact Vision TV Boy" around the same time. Bringing the remaining 2nd generation consoles un-emulated down from 6 to 4.

Something for the completionists out there. One of the last remaining consoles that has been unemulated since the 80's, just got it's very first emulator in febuary last year. It went under the radar to such an extend, that even the emulation wiki does not know about it. https://emulation.gametechwiki.com/index.php/Epoch ((Linked Removed))

Thanks! But most of what's discribed about my issue (and how to solve it) does not apply to the Libretro core. m3u playlists are not supported and as far as i can figure out, you cannot apply two files to RetroArch's command line. It seems to ignore the 2nd augmentation

Hey everyone. Strumbled on an automation issue with Retroarch that i hope someone has an answer to. There are some games that requires both disk drives to be used to launch a game (4D Driving fx) but so far i've been unable to figure out how to accomplish this. Is there any command line command to attach content to a secondary drive inside Retroarch? or does that have to be done manualy each and every time?

Can see i forgot to mention something DCB (Discrete Circuitry-Based) machines means a machine without a CPU

The Coleco Telstar & Coleco Telstar Arcade are both DCB (Discrete Circuitry-Based) machines and such are very unlikely to see any emulator anytime soon. (and when they do, they will all be very CPU resource intensive) Looking at the mame dev forums, there was some talk around 2018 of some dumping progress being made but i have yet to see anything come out of it. The files your listing does seem to be the dumps that has floated around the mame dev forums for the initial Coleco Telstar (model 6040, 1976). It's very unlikely anyone is going to do much work on this machine, it's more likely that progress will be made on the other higher profileDCB/TIL arcade machines.