Headrush69

This won’t get solved unless we narrow down the issue and eliminate possibilities. Two suggestions already given we haven’t heard that you tried: 1) Check permissions on hard drive Directions here 2) Install the previously working version of Launchbox to a NEW location. Do Not copy anything from your previous installation. Start this new copy of LaunchBox, import a few roms. Close and start this same copy of Launchbox, are the previously imported roms there how?

Agreed, it just works. I've tried various Bluetooth options and always stuck with the Mayflash dolphin bar.

You need to set up a dapinput.ini file with the information provided here: Sample dapinput.ini file Keycodes needed For SInge games, I needed a copy of dapinput.ini the main SInge directory, (In Daphne main directory only worked for Daphne games)

I'm actually running without admin privileges on anything with MK version 1.1 and everything works fine, including bananapass. You get a warning about admin privileges, but everything seems fine and they do say to. (Maybe it's a feature I'm not using)

You only have to run Teknoparrot_UI with admin rights, not LaunchBox or BigBox.

Are you 100% sure you aren't using the Retroarch MAME core within Launchbox? If no, 100% sure your command line options for MAME in LaunchBox is not specifying a different mame.ini file?

We need more information. You need to try to be more detailed and specific. Not sure what you are saying above. Did you install a clean install of LaunchBox to different hard drive or did you just copy your old installation to different location on another hard drive?

You should have continued in your previous thread, this just makes it harder for us to see where we are at and force us to search for your previous thread. It was many versions ago, but i encountered some library issues after at forced restart before. Can you install the previous working version of Launchbox in a NEW location? It won’t hurt your previous and will eliminate issues accumulated from previous troubles. Did you do the drive scan as suggested in the other thread to make sure permissions on some of the files have been changed?

I double checked my collection and indeed Get Bass was the one I couldn't get working as well. Since it's just a clone of Sega Bass Fishing, not a big deal for me. I generally don't keep clones unless they had somethig specific I need. (Character selection in TMNT, trackball support vs joystick support etc)

I find the new GUI is easier for new users as it will tell you exactly which file you are missing in each romset if they are incomplete.

Thought he said he had SVN r777.

Those nvram should have the test options set for a working config. Are you 100% sure your roms are correct? I would suggest downloading the new Supermodel3 GUI to help until you get all your games working, Is there any output if you start supermodel3 from the command line? Yes that is the forum, never required registration before though, hmmm. (Seems they're site getting spammed so you need to register now. You can get the Supermodel3 GUI there as well)

Can't find it right now, try these nvram files. (Put in nvram folder in supermodel folder) nvram.zip

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.