Lordmonkus

Split, Merged and Non Merged all have the same games in them, they are just packaged up differently for different uses by different users. This diagram shows the differences between them.

No problem, texture pack naming is sensitive.

Try renaming the texture pack htc file to: SUPER MARIO 64_HIRESTEXTURES.htc

Yup, no one is forced to use them, don't like them ? Don't download them, pretty simple.

While I agree it would be nice to have downloads of previous versions of cores there is nothing forcing you to update the cores and the source code is available for people to compile their own previous builds.

Yeah I need my shaders as well, I really cannot stand old pixel art without them.

Yeah

The mednafen_psx_libretro.dll core is the most compatible and least buggy core, HW is decent but there are some minor bugs.

The Mame cores are updated along with the official updates, if you have the core that matches your set already you shouldn't update the RA core without knowing that you may run into possible problems. As for re-obtaining the 195 core you can ask around and see if anyone else still has the 195 core or you can get the source code from the Libretro site and compile your own.

Jason is finishing up work on Launchbox Next and then back to the poll, the code for LBN will lay the foundation to make future features easier to implement.

You don't need to create a new emulator entry, all you had to do was add the Arcade platform and command line parameter to load the core you want for it in the Associated Platforms window of your already existing Retroarch entry.

Glad you got it sorted though I am surprised that was the issue, usually when the ini file is in a sub folder Mame games have problems loading through LB.

Hmm, everything you are showing appears to be correct. Where are your roms located ? What is the full path to the folder with them ? Sometimes if they are really deep the path can be too long for Windows and it will break command line functionality. I don't believe that is there issue here, looking at your folder structure it looks like you have your stuff organized in a sensible manner. Unfortunately for me right now it is almost 4:30 am so I have to head to bed but I have passed this thread along to the other moderators and hopefully they can get you sorted out. I will check back in tomorrow.

Do your platform names match those in the Associated Platforms window of your Retroarch emulator in Launchbox ? Here is a quick tutorial I did for setting up Retroarch with Launchbox, I show some of the main problems to watch out for. I use the NES as an example but the same principals apply with all the different platforms and cores.

Is your mame.ini file in your Mame folder where the exe is located or is it in a sub folder ? Are you using a shader for your scanlines or an overlay ? My mame.ini file is in the main Mame folder with the exe and I use HLSL shaders perfectly fine, BGFX shaders work just fine as well. I haven't used an overlay scanline in a very long time so I have no idea if that might be the problem or not.

Great eyes.

You have 2 platforms in the Associated Platforms window ? Do those match the way you have it named in Launchbox ?

If you could provide screenshots of your edit emulator and associated platforms windows maybe we can help you.

I have nothing to do with the database stuff but if it were put to a vote I would vote for this.

Launchbox doesn't care what rom set or version of Mame you are using, only the emulator cares. Can you show us a screen shot of the error ?

16:9 is definitely stretching it, now it's up to you whether or not you like it or not.

Looks like you got 16:9 aspect ratio on now. Like I said I don't use CRT shaders with 3D polygonal games and systems.

Those scanlines look awfully spaced in your screen shot, looks like you have integer scale off which can wreak havoc on some CRT scanline shaders.

The internal resolution and anti aliasing settings will be in the core settings, they aren't in the video settings of RA. Of course the settings available will vary from core to core, some may or may not be available.