Headrush69

All working here. You likely need to adjust some setting in the test menu. I'll see if I can find the the thread again on the supermodel forum that shows what needs to be done. Are you using actual 0.3a-wip version or a newer SVN? (SVN will still say 0.3a in output)

Devreorder wasn't consistent for me until I installed it system wide. You also have to be careful to get the right DLLs installed when on x64 and the permissions correct. x64/dinput8.dll -> C:\Windows\System32 x86/dinput.dll -> C:\Windows\sysWOW64 Edit: Remember this only works on Xinput devices if the application is accessing them in Dinput mode, not Xinput. Also, if the application uses the COM interface for using Dinput, only the system wide method will work.

Currently, MAME does NOT run Dragon's Lair. To find the roms and a checksum for the files any mame game needs: >mame64.exe -listroms dlair Name Size Checksum dl_f2_u1.bin 8192 CRC(f5ea3b9d) SHA1(c0cafff8b2982125fd3314ffc66681e47f027fc9) dl_f2_u2.bin 8192 CRC(dcc1dff2) SHA1(614ca8f6c5b6fa1d590f6b80d731377faa3a65a9) dl_f2_u3.bin 8192 CRC(ab514e5b) SHA1(29d1015b951f0f2d4e5257497f3bf007c5e2262c) dl_f2_u4.bin 8192 CRC(f5ec23d2) SHA1(71149e2d359cc5944fbbb53dd7d0c2b42fbc9bb4) dlair NO GOOD DUMP KNOWN z03_1001_vyw-053_v1-0.bin 8192 CRC(31ec4687) SHA1(52f91c304a878ba02b2fa1cda1a9489d6dd5a34f) In this case, no good dump in MAME for the CHD yet.

Yes, with the recent changes I've switched completely to the Retroarch vicex64sc core for all my C64 games. I did find a weird virtual keyboard issue that only occurred in some games when using a keyboard mapped to RetroPad, not when using a gamepad, and they had it fixed within hours of posting it on the github issues page. Great work rsn8887 and sonninnos!

I prefer under Retroarch options , using the horizontal overscan cropping. Save this as a game specific options. You will have still have very small black bars vertically, but it's very close and you don't have to mess with config files.

Why not configure them within Retroarch and save the autoconfig? Or are you looking to ignore these controller completely?

I agree. I've made the upgrade already. My comments was a little tongue in check about if it isn't broken, not touch it for "most" users. Like users that think they always have to have the lastest MAME rom set when so many of the changes are systems they don't use, or are minor emulation improvements, not necessarily playablity improvements. (Not to say there aren't any) That sucks, Wonder if anything shows up in debug log. Both my upgrade and clean install don't show these issues. It's odd that it happens with all video cores too.

But it's newer, it must be better!

Are you making this decision based on a new install or applying over your old setup? Probably better to be sure this isn't an upgrade issue before declaring it a bad release to everyone.

Delete BigBoxSettings.xml in your LaunchBox/Data folder.

Not that I compared FPS, but both mupen64plus and paralleln64 cores both running fine here. Just zip your entire Retroarch directory and then apply the update. If you find issues and want to go back, just delete and unzip that backup.

The save options are all consolidated under the SAVE option in Shaders, You can save by core, by directory, and by game.

dov_EL, if you install 1.7.8 to a new location (clean install), do you have the same issues? Sounds like might be a specific issue with your setup and not Retroarch specifically. If you could run the debug version of Retroarch and post the output that would be very useful.

Are you using a custom config file? Looks like when you saved the configuration, it’s was saved as mame2.cfg. I noticed some quirks with config saving on cores I was using custom configs.

Working here. What video driver are you using, and what version are you upgrading from?

I like having each core’s options in a specific options file per core instead of an all in one inclusive Retroarch-core-options file.

Unless I know I need a specific version, I just got with whatever the no-intro atom for my region is. For MAME games I usually try to use the parent rom, except when it’s not for my region, or adds special features. For example, Double Dragon, I’ll use the world version ddragonw, instead of the parent Japanese version ddragon. Another is using a variant of Teenage Mutant Turtles rom so I can pick my character since by default the parent rom works with a 4 player cabinet.

I found it easier to use bat command files over trying to do everything in AHK scripts. Although I’m not familiar with that specific program, if you can run it now under additional apps in Launchbox, You should be able to run it from a bat command file. Edit: In your case you would have to start antimicro using Start so the script wouldn’t waiting for it finish, run your emulator making sure it waits for completion, than use appropriate commands to kill antimicro

In case like this I make a simple .bat file, use command line Start or Call command to run the applications I need, than have that also call the original emulator passing on the filename Launchbox sends. Add this .bat file as a new emulator and have the roms that need those additional apps set to your .bat file. Here is a simple example: @echo off call "C:\Program Files (x86)\WinIPAC V2\WinIPAC.exe" "C:\Program Files (x86)\WinIPAC V2\WinVICE.ipc" call C:\Users\ARCADEPC\LaunchBox\Emulators\WinVICE\x64sc.exe %1 call "C:\Program Files (x86)\WinIPAC V2\WinIPAC.exe" "C:\Program Files (x86)\WinIPAC V2\Default.ipc" exit 0

Delete BigBoxSettings.xml in your LaunchBox/Data folder Or rename it if you wish to recover some settings you might have had.

I do a similar thing. Once you have you the list of roms you want, it’s easy to do a directory listing without the file extensions to produce a text file with the roms name of your games. When a new Mame release comes out, using ClrMamePro, go into set information, select load from file and use that text file you created. Now your only checking the games you want and it will show any files you might now need. Super fast and no need keep a full Mame collection if you don’t want to or can’t.

There was a small bug in the 1.7.7 version that is causing this. There is a discussion on the issue on Retroarch GitHub site: https://github.com/libretro/RetroArch/issues/8834 It should be fixed for 1.7.8, but if you need it now, you can grab a nightly which has the fix.

Just for completeness sake, setting servostik modes using LEDBlinky with Launchbox's built in support works perfectly. It's as simple as pointing LEDBlinkly to your MAME cfg folder, a controls.ini file and a MAME.xml and most of the games are preconfigured. (You don't have to have LEDs to use LEDBlinky. LEDBlinky has a tool for adding support for other non-MAME systems. For me setting Atari 2600 games to 4-way was required, but most consoles use 8-way, most 4-ways games are in MAME, so not much configuring since those files cover most of the roms already.

Progetto's Web Site

In general terms, I think too many users try to maintain a full MAME set, when a smaller subset is usually enough. Once you have pruned your set down, it's really easy to maintain and update with ClrMamePro. (Though you'll find the most popular roms don't often change much, if at all.) I'm a big fan of the Bezel Project bezels as well, but you have to be careful as they will overwrite some of the regular MAME artwork that have advanced features like color overlays, lighted bezel elements based on game elements etc.