Retro808

Interesting to know it sees it as a separate keyboard. I do not have an Xtension so no experience there. If you disconnect your actual keyboard will it map correctly? The Emulator addition is trimode so you can switch between keyboard, dinput, and xinput. I know it is not the best solution, but until you can figure something out you may need to run those games switching to Xinput mode.

Which specific Xtension controller do you have? Odd the keyboard works not the Xtension. It replicates a keyboard.

Works fine for me. Here are the settings I have.

It should be. It is a common issue with MameUI and LB. LB is looking for the mame.ini to be in the main mame folder which is where the regular mame would put it. Try moving your ini to the main Mame folder where the mame exe is.

Are you using MameUI by chance? If so make sure the Mame.ini file is located inside the main folder where the Mame exe is. It may be located in the ini folder.

I believe without a cart you should at least see the green jumbled looking initial screen. I cannot remember if even without a cart it shows the Neo Geo bios screen.

Ha, a stinking typo had me scratching my head. Your sorted so all that matters.

Huh? Are you talking about in a specific emulator?

@CDBlue Thanks. Did not notice I typed upper case "Q". I edited to original code in that post for future reference. @Nocta maybe trying the correct version that CDBlue put will help. LOL.

No worries. Sorry I did not really have a solution. In Citra's configuration under General do you have the box for Confirm Exit unchecked? This should not make a difference since you said Alt+F4 and Ctrl+Q closed Citra but just wanted to check.

Man not sure what to say. Citra closes just fine for me without needing an AHK. It also closes if I use any of the ones provided. Even an AHK to send F11 for fullscreen works. Are you on the most current Citra version?

That all looks good. What version Citra are you on? If you open Citra and just run a game there does hitting either Ctrl+Q or Alt+F4 close Citra? Can you try below. I doubt it is the AHK script since even the script to send Fullscreen is not working. But worth a try. ESC:: { SetTitleMatchMode, 2 WinWaitActive, citra Send !{f4} break }

Can you post pics of the Citra emulator setting from Launchbox. Post a pic of the Details tab and the Running AHK tab. You do have a button mapped for "Exit Game" in LaunchBox right?

What tab are you pasting the AHK script in?

Save states for Citra would be done in game just like you were playing a 3DS. I do not believe there is an actually emulator save option like Mame or RA would have. Also if you are going to be saving in Citra I recommend using a slightly altered AHK. The one posted earlier is a hard close command and can mess with an emulator properly saving in-game saves when it is closed that way. Ctrl+Q is Citra's close command or Alt+F4. So I would use something like below. ESC:: Send ^q or ESC:: Send !{f4}

May be how Jason originally coded it to go to the Platform folder. Not sure. It does it for me as well so does not look like a bug issues. I do not think anyone has really brought this up before, so it may not have been looked at since it was originally done.

Also try a different theme. There were some theme's that did have memory leak issues. Which one are you currently using? Default ones should be ok since Jason tests those pretty well.

Should work fine as long as the emulator does not have issues. I know many members use arcade controls and have gamepads for console specific systems. We have seen some users have issues with wired controllers being plugged and unplugged and some emulators not retaining the mapping since Windows can reassign a controller ID each time it is plugged back into a USB. I have not seen many issues like this with wireless though. I have been using my arcade controls with Xbox One and 8bitdo wireless controllers for several years now and minimal issues.

We have not seen other posts about Emumovies log in issues. I have been able to access Emumovies without issue even added and scraped a 20 games as recently as a couple hours ago. Are you getting an ID/password error or some other type of cannot access media error? You mentioned since the last beta this has occurred. Have you tried to reinstall the version you had before to confirm it might be beta related?

Do you have clear logos for the ones missing the Launchbox folder structure I mentioned? (The first folder path I listed) If so then a cache refresh should fix it.

Most themes do not come with clear logos. Those are usually downloaded when you add a platform and it scrapes the metadata, though not all systems are covered. So you may need to add your own, or add a different style of clear logo than the ones LaunchBox will scrape. Those typically get stored in \Launchbox\Images\[Platform Name]\Clear Logo folder. If a theme does include them they they would be located within the theme's main folder and within the Images\Theme\Logo folder. So \Launchbox\Themes\[Theme Name]\Images\Theme\Logo If you do add your own and they do not show you may need to refresh the cache. In BigBox go to the settings and look for Images. In that section will be options to refresh the image cache.

Yeah, anytime you add an image in the correct folders and BigBox does not automatically display them just do a cache refresh. Sometime this may even be needed in LaunchBox.

Agree. I cannot believe how horrible we are as moderators. ?

No worries. I think you did read a little to much into it. I am never worried if someone is or is not being judgmental of me. Just to be open about it, I did not even think that. I was suggesting simply that after 30 plus posts in a short period of time and he is up an running that was a good enough stopping point for me. You quoted me, so I just wanted to respond as I try not to ignore a member if I am tagged in a post.

I know. The fact he moved his original roms and did not have LB move them on import lets me know his new import is working and has good named roms which is why I really did not say much more. His last pic confirms what I was suspecting and even shows it does contain the proper rom along with the -1 name that LB can do when it moves roms. I know being more concise on the error might be helpful to others possibly, but a lot of info went back and forth and now that it is working sometimes it is best to stop right there for now.