Lordmonkus

Keep in mind, the RA core will get the updated GlideN64 plugin if it's not already in there, the Mupen64plus_Next core is the one to look for.

Yeah we have tutorial videos on the YouTube channel. Yes, you should always do this with any emulator.

I would suggest the Retroarch core at this point in time, the person behind Mupen64plus has recently put it behind a Patreon paywall of 1$. If you are ok with giving that 1$ to the Patreon then it is a very good choice but that's a decision up to you.

There are different possible causes of this depending on your setup and we have guides on the YouTube channel for setting up Mame with Launchbox. But off the top make sure that your mame.ini is located in your Mame folder where your Mame executable is located, it may be in your \Mame\ini folder which will cause a problem.

No, there are black borders but I play on a 1440 display so they are relatively small and I am ok with that because I much prefer integer scale where possible. You need to set it on a per system basis in the config I believe ;Enable specified OpenGL shader. ss.shader goat

I should add I no long use any of the command line stuff from above, I now just set it all up in the config and all I change is the shader to GOAT for a CRT effect.

Here you go, Kuri Kinton.

I know the game you are talking about but I have to find it to tell you the name. It's a game that plays pretty much like Kung-Fu.

In any case, have a look in your default.cfg file and look for the line: video_shader = "" If it looks like that above we will have to look elsewhere, but if it has a shader preset path in between the 2 quotes remove that path so it looks like it does above and save it. Then make sure you don't have any core presets saved in your shaders\presets folders.

That's actually how a good consumer grade CRT TV looks if you get close enough to it.

You probably have the scanlines enabled in the default.cfg file and that is getting loaded into the core when you load it. Try certain shaders like CRT-Royale or the Kurozumi variant, they are made specifically for 4K.

I haven't been dismissive of you at all. If you want to provide more information such as screenshots of your emulators setup in Launchbox (if / when this issue occurs for you again) we will try and help you out. Screenshots of your edit emulator, edit platforms and associated platforms window would help out a lot, quite often when we dig into peoples setups we find a small but not so obvious error in the setup such as a path changed, platform name mismatch or the user changed the emulator and didn't transfer that change in Launchbox.

I meant you could try Launchbox on it since it's free.

You can try it out since it's free, see how it goes.

I'm afraid that hardware is far too weak to handle BigBox. Some of the more basic emulators would probably run fine on it but your choices would be very limited.

Grabbed this yesterday, great update.

Have fun

I see your problem, in your associated platforms you have Intellivision but your platform is called Mattel Intellivision, change the associated platforms one to Mattel Intellivision and it should work.

Let's continue this over in the other thread rather than have 2 threads about this going.

Stand alone Mame will use normal rom files as well, I use it with the No-Intro set frequently because I can't be bothered to download the Softwarelists set. Can you post some screenshots of your Mame emulator entry in LB ?

There is not, Launchbox has no way of knowing or logging when an emulator fails to load a game for any reason. Launchbox only runs a "shortcut" telling what emulator to load what rom in the way that you tell it to even though it simplifies that process a great deal.

Launchbox / BigBox doesn't have anything to do with controls in games themselves.

Again, I am only guessing here but I am gonna say there is some other underlying cause of the issue here and it's not Launchbox itself. Like I said before, I have never experienced this is in the 3-4 years of using LB and I have never seen any other users have this issue. Simply deleting and re-installing Lb without find the actual cause of the issue is just going to end up in the same result again for you.

That is extremely strange, like I said, I have never seen that or seen anyone mention anything similar. Maybe you have an overly aggressive anti-virus or something but I am only guessing when I say that. I will tag @Jason Carr for him to have a look at this thread and maybe he has some more insight into what could cause this sort of problem.

Not sure what to tell you, I have never had this happen to me in the 3-4 years I have been using Launchbox, nor have I seen anyone mention this happening to them. I would suggest though that if this happens again, instead of uninstalling and re-installing try selecting all the games in the platform causing issues and using the bulk edit tool to re-assing the emulator to the roms.