neil9000

Is it a lifetime license?

There is no current beta, 9.3 official was released last night so that is what you should be updating to.

It is no different to how it updates when a update is downloaded, just that you are initiating it yourself. It won't overwite any of your configs it will simply update the program, exactly the same as a normal update. Just make sure to install to the correct folder as the installer adds a \Launchbox to the location and you don't want a Launchbox folder inside your Launchbox folder. So if you just have Launchbox on the root of your F: drive just choose F: in the installer.

Have you tried manually installing the update from the update folder and specifying the path in the installer wizard?

So Launchbox downloaded the update then you get that when it restarts to install the update?

It looks like your HDD doesnt have a drive letter, or you dont have permissions to write to it from that PC.

Yeah there is no chance there im afraid. Launchbox was completely rewritten since then and is now using a completely different framework than what you are on uses. The startup/shutdown screens are simply incompatible with your version.

OK now i'm confused, are you running Amiga through MAME as well? If so you likely need the kickstarts for that, but im not even sure if that works in MAME, or if it does i dont know anyone who uses it, they use dedicated Amiga emulators. As for Arcade roms working when you unzip them that makes no sense at all, MAME roms should be loaded in a compressed format, you will just get a error if you load a unzipped rom to MAME, are you sure you actually have correct pack and not the Software List pack for MAME which contains old computer systems and a handful of consoles?

This could be several things. First do you actually have all the bios files, they are not included in all the romset types, they are in the non-merged set but i'm not to sure about the merged pack. Also the romsets and the emulator are versioned for a reason, so if you have a 0.202 merged romset then you should really be using version 0.202 of the MAME emulator along side it as this can cause incompatibilitys (rom zips and the emulator can change from version to version, and a game that worked in a previous version can be broken in a current version and vice versa). Thirdly what games are you testing? Some games also need a CHD file as well as the rom zip in order to work, CHD's are essentially CD images compressed to the CHD format and some games need them. Killer Instinct 1 and 2, Street Fighter 3 and it's sequels for example all need bios, gamename.zip and CHD.

Also to add, as you are using a pre built build that also uses Rocketlauncher you could break things by updating emulators. The rocketlauncher modules that interface with the emulators are usually for specific emulator versions and can/will break if you update to a non supported version.

The Launchbox database does not have any game videos, there are however a handful of theme videos on our database for a very small collection of games. The game videos need a paid emumovies subscription in order for them to be scrape-able in Launchbox, so it sounds like either you dont have a emumovies premium subscription or your credentials are wrong.

The second image is the game details screen, this can not be changed it always uses the list view as it is a list. I personally dont use that screen so just switch it off. As for the 3D boxes you could edit the xaml, but it is actually based on your priorities you have set in Launchbox, so change those.

lol, well you would be surprised with how many posts we get that just say "retroarch works but not through launchbox, help".

This is why we always ask for pictures when people have issues, it helps us out a great deal, so thanks for that.

Spotted it!!! you have Retroarch set to unzip your games, arcade roms should never be unzipped, you just load the zip directly.

Are you sure you are using the correct fba core in the associated platform dropdown, there is more than one in retroarch if i recall.

Nothing i can see off the top of my head in all honesty, do the neogeo games load in retroarch by itself? I havent used fba before so dont know if it needs to know your rom path like MAME does, or that the neogeo.zip needs to be in the retroarch/system folder like other bios files. Also like i asked previously are these new imports or were you originally using a different emu for them?

OK, sorry just noticed in your image, yeah your platforms are named differently to how they are in the associated platform tab, you must match them.

Make sure that the platform name in the retroarch associated platform screen you posted EXACTLY matches how the platform is named in the left sidebar in Launchbox. For example in your image its called "SNK Neo Geo Pocket Color" so that must match the platform name in launchbox, it could for example just be called "Neo Geo Pocket Color" there so Launchbox will think they are different systems. Also were you originally launching these syatems with different emulators in Launchbox?

You didn't create any controversy , i was simply saying that changing how the program works for everyone for one user isn't likely. That's not to say that it wouldn't be considered or could be added as a option in the settings to toggle but that is up to Jason. At the end of the day Jason focus's his development on the additions that many people want to see added, and i believe this is the best way to work with the community. Maybe this change can be added to the next poll for users to vote on, so that interest in it can be gauged.

Do you have the correct mame romset, and do they work when just loading them from within mame.

Yes but if you are using rocketlauncher then that has to be the emulator, not retroarch or mame.

This is how it has always been, changing how the program works for just one person probably isn't on the cards if i'm honest. If enough people all feel it should be changed then maybe @Jason Carr would consider it, but i highly doubt it will be changed for everyone to appease one user i'm afraid.