twobucks

kind of a longshot but have you tried launching games using just a keyboard and bypassing the keyboard encoder(assuming your using an ipac of some sort)? do you still have the mame startup issue using just a standard keyboard with no other controls plugged into the pc?

I have had some experience with demul and most of the time the dreamcast rip is the problem as mentioned above but there are a few other things you can try. If its a bin and cue try converting it to a chd file. There is a free utility called "cue or gdi to chd" that will convert cue or gdi files to chd. I have had very good luck with doing this conversion. If you dont already have the lastest version of demul then try updating. The very latest version is 180428. After uprading some of my cdi games started working properly.

for the crosshairs being off make sure you have calibrated the gun in both the aimtrak utility and in the games service menu if it has one. carnevil does have a sevice menu to calibrate your guns

couple other things to try: 1.seems like microsoft released a patch that caused severe game performance issues. make sure you have the patch installed that adresses the problem kb4489889. 2. try disabling fullscreen optimizations in the compatibility tab for mame64.exe. 3. make sure the new focusing feature is completely off in windows 10. try turning off game mode in windows 10. 4. make sure you dont have any video card driver utilities running that may be conflicting like geforce experience etc. try disabling or uninstalling.

I ended up using a program called display fusion to resolve my problem using windows position profiles. I save the windows positions before starting a gun game and disable the marquee monitor using display fusion, then reenable the monitor and recall the saved profile after exiting the game. So far it has worked very well.

I dont know much about the windows problems since i have not upgraded yet. Maybe someone else can chime in on that part. Try turning off game mode in windows 10. As for reinstalling mame there really is no installer just extract the files to a new folder and set it up. Download the mame 203 version from mame's website and extract to the new folder.optionally you can replace the exe with the no nag version. Then from there generate a new mame.ini file and configure all your settings. Make sure to configure your paths for roms , chd, samples, to point to your existing rom set. Add your controller file if you have one. When i tested mame 202 on my system i just added it as an additional emulator in launchbox and changed the associated emulator for the rom. I would suggest trying a few roms first then i believe you can batch edit the associated emulator for all of your roms. Now test it and see if the startup problem is gone.

The problem is similar but not exactly the same as yours. In my case the problem may cause a couple second lag but not to the point of it causing a system lockup. Ledblinky sometimes getting confused on the first rom has been happening for a while. Checking the windows event log as i suggested might help and should be running by default. Just type "event viewer" in the OS search bar. Open it and look at both the application and system events from time of system boot to bigbox locking up. You might get clued in on the problem. Did you update windows 10 when you updated bigbox? I am running version 1709. If you did update maybe a new windows feature is causing a conflict. If its not windows maybe something got messed up during the mame upgrade. Try doing a full reinstall of mame and regenerate the mame.ini

I tried loading a 202 mame rom in bigbox right after booting and i did run into a few minor issues. The first time the loading screen opened it timed out and dropped back to bigbox, then a few seconds later the game started. This maybe added a few seconds but not minutes. The second time i loaded a rom right after startup ledblinky did not light the controls. Ledblinky threw an error "timeout waiting for primary instance handle". In both cases the roms opened with a little added delay and closed fine when exiting. The subsequent rom i opened had no problems and ledblinky worked fine. Keep in mind these same issues do happen with earlier versions of mame. Sounds like you may have some kind of major startup delay causing your issue. Have you checked the windows event viewer for any application or system errors that happen anytime between windows startup to just after force closing mame? Which version of launchbox are you running? 9.7 is what i tested with and i am also on windows 10.

Ok, i added mame 202 and so far i didnt run into any issues. I added mame 202 and 202 roms that were new since the 185 set. I had no lockup issues opening and closing mame 202 games in bigbox. Ledblinky is also working fine. How often would the lockup happen to you and any particular games that would cause it?

Hmmmm, i didnt know you were still having issues with bigbox opening five instances. I had assumed you got that sorted. Yeah i agree that ledblinky is not the problem in this case. If i get time this weekend i will add a new version of mame (version 203 or greater)to launchbox and a couple roms to see if i get the same issue. I have been debating updating my mame set and this will be a good test.

Does it work properly if you alt-tab to the game after starting from bigbox/ launchbox? You might be able to bring the game to the forefront using an ahk script to launch the game. The game is on my list to pickup but waiting on the next steam sale.

No, There is a mame.xml that is generated using the -listxml command from mame. I would suggest regenerating this file since you did upgrade your mame version. I don't remember the full command but if you check the mame documentation it should tell you how to generate the file. I believe for the mame.ini file the only setting you need to be concerned with is making sure the "OSD output setting" is set to "windows". Did you regenerate the mame.ini file when you upgraded mame or did you just copy your old mame.ini? This could cause problems if config options have changed between versions of mame. Now go into LED blinky config and make sure the mame tab has all the paths setup correctly. If you installed the new version of mame in a new folder then your paths may be wrong. Here is a screenshot of what mine looks like If you still having trouble i would suggest checking out this video on youtube which takes you step by step integrating LEDblinky to mame using a launchbox frontend. My thought is when you upgraded mame something in the ledblinky config may have gotten broken.

Did you try regenerating the mame.xml file using the 203 version and ensure ledblinky is pointing to the new file?

I also have a cabinet setup with mame version 185, ledblinky 6.6.0.1 and bigbox 9.7. Everything on my end works including startup screens, lights, and speech. I have witnessed some minor issues with ledblinky getting confused on which rom it lights buttons for but nothing like your experiencing. Is your ledblinky version up to date?

I had a similar problem when i imported naomi and atomiswave games. I had to dowload the videos manually from the emumovies ftp site.

Display fusion is also a good 3rd party software option if needed. I use it on my multi monitor arcade cabinet. It has a pretty good command line option so you can control it by running batch files both pre and post game launch.

Can you run the games directly from demul? Make sure your path to the roms is setup correctly and you have all the bios files. Just so you know version 111117 is not the latest version of demul. The latest version is 180428 that is located in the demul russian forums. Reason i bring this up is the latest version did help with certain dreamcast games not running for me.

I am using dual monitors on my cabinet setup. One thing i can suggest is make sure your primary monitor is setup in windows as the right monitor and the secondary monitor is on the left. This simple changed fixed a lot of problems with my dual monitor setup.

I might be able to help but i will need a bit more info on your setup. What version of mame, ledblinky, and launchbox are you running? Are you using a keyboard or joystick encoder(ipac). Include some screen shots of your ledblinky configuration page for the mame config and front end config. Do u have ledblinky working with other emulators in launchbox?

I dont have the same setup that you have with multiple monitors but i can say i do use the most recent version of displayfusion to shut off my marquee monitor during certain games then reenable and restore the launchbox marquee window on game close. Take a look at the recent version of displayfusion and its command line options that can be executed via batch files. you may be able to do what want.

I am using UCR for some games and I use the additional apps feature to launch it. see below Don't forget to create a batch file to close UCR after you exit the game or your keyboard controls will still emulate an xbox controller.

Have you tried using ucr

Ok sounds like you have gone through a lot of troubleshooting already. If I was in the same situation I would download a clean copy of the emulator. Setup the emulator in a new folder leave all the options on default and set your Rom location (point to your Roms folder that also have needed bios). Don't copy any config files from any other versions to demul. Then just run a naomi rom from demul and see if it starts without crashing. If it does crash, what rom set are you using?

Which version of demul are u running? 180428 is latest version. How recent are your video card drivers? What OS? I am currently running all demul naomi roms using an ati card (rx 550) with no issues on windows 10.

By the way i would take out ignore_aspect_ratio. This is only if you were running a version of dragons lair that was not a 4x3 aspect ratio. Glad it worked out.