Lordmonkus

Your command line parameters are completely wrong and you have boxes checked that shouldn't be checked in the emulator details tab.

Try running the installer as administrator.

I would suggest to try re-installing the latest non beta version over top of it.

BigBox mode. Edit: Updated and much better now but still the problem of when coming back to the platforms from the options BigBox has a problem. It doesn't freeze in the sense that it crashes or hangs but it just sits there with the platform name and no games showing and I cannot go forward or backwards in the menus. Also wall view seems to work now at least.

Yes, this is based off the standard view and performance is something I have never had any real issues with in the past aside from certain betas where there was a problem which Jason fixed.

Just updated on a tester install of LB with only a single platform and 18 games and performance is absolutely abysmal. Going into the options and changing settings and then back to the platforms list completely stalls out LB to the point of having to kill it in the task manager and restarting it. I know the new wall view is a very early version but my immediate issue with it is that it only displays some of the box art and which art it shows changes each time I start up BigBox.

No, because I don't have to wait for my games to load unless it's something like a large modern PC game like GTA V. But I have also learned not to just start mashing buttons if something doesn't happen immediately.

The only other time I can think of causing this issue is with RocketLauncher because of how it has its own config files.

I wish I had a solution for you but unfortunately I do not. It could possibly be an issue with the UI version of Mame you are using, I have only used command line versions for a while now and never run into this issue. In that thread you linked they mention launching a game with no controller plugged in or turned on will cause the controls to reset.

I have a 360 controller, Hori Fight Commander and a wireless Logitech controller and none of these exhibit this issue with version 186 or any other version of Mame I have setup in the past.

Yeah post any URL you need as long as it doesn't contain copyright material such as roms and bios.

Yeah the General section is for all games and the Machine is just for that game or system if emulating a console or computer through Mame.

I have never experienced this issue with either wired or wireless controllers. Not saying it can't / doesn't happen to people but I have never experienced it with quite a few different versions of Mame.

That emulator will not work with RL. You also need to have a module that is compatible with the version of an emulator you are using. This is done through its built in AHK component so it's not a simple "emulator binding screen". Everything else said is about right. I don't tell people not to use it. I only tell people what to expect with it if they have never seen or used it before and remind them that getting tech support for it here is going to be tricky since most of us avoid it.

Well I wasn't thinking of banning you but if you wanna continue with shit like: I might consider it. I wasn't personally attacking your friends but you can't expect a program to account for every single possible point of failure such as friends who are impatient and spam buttons to get a game to load faster. Take a second to inform them that they may need to wait a few moments for a game to load. I have done this for my 5 and 11 year old cousins and they learned it instantly.

I've actually used it, I had a working HyperSpin setup but I abandoned it instantly as soon as I found Launchbox and I didn't have to ever look at RocketLauncher again. The learning curve for it alone is a pain in the ass and not worth the hassle just for cosmetic shit like fade screens which take as much time to load as my games do in the first place. Pause screens do nothing for me because if im pausing the game it's because I am gone away from the game to take a dump. Like I said before, it's a big learning curve for cosmetics and an extra layer of possible failure in the chain. I have seen many people in Simpy Austins Discord channel have issues because RL broke something. Most people would rather play games over wasting time troubleshooting RL.

I'm sorry but we're talking about a PC and a wide variety of software. If you need to pull out a whiteboard to explain to your friends to not spam the button and wait for the game to load then you need smarter friends. And when you post snarky shit like: "That search feature keyboard in BigBox not being able to jump from one side of the box to the other is a bit of a laugh too, what year is it again?? Go play some Pac-Man and recode that one Devs" Don't expect non snarky responses.

Get smarter friends, take a moment to teach them not to spam buttons or have a 2nd simpler setup for your friends ?

A button Launchbox to reset it would be nice though.

You could go into each platforms .xml file and look for all the instances of <PlayCount>#<PlayCount> and set it to 0.

There is no one size fits all settings for PCSX2 unless you use the software rendering which rules out any graphical enhancements like resolution scaling or anything else. If you want the enhancements you will need to use one of the hardware renderers and tweak each games settings which can be very tedious to setup. The easiest way I found to do this is to use a PCSX2 frontend called Spectabis which supports per-game configs and this then becomes your "emulator" in Launchbox once your games are tweaked and setup. Take a look at this thread here I posted a little while back about Spectabis

Sorry, but wrong forums. Locking this here and now. Edit: Unlocked but this is completely irrelevant to the Launchbox forums.

My advice for Playstation is to either use ePSXe 2.0.5 which is the latest or Retroarch using the Beetle PSX core. Whichever one you choose get it working outside of Launchbox first and then move into Launchbox with it. If it is working outside of LB first then we can trouble shoot much easier from there.

Without more details my first guess would be missing or incorrect bios. My 2nd guess would be bad disk images or you are loading the incorrect file.

RocketLauncher does add that "icing on the cake" but it comes with a very steep learning curve. Also RocketLauncher is something none of the moderators such as myself, Brad or Zombeaver use so don't expect any tech support from us with it though there are several people around here that do use it and they would most likely be willing to help you out with it.