-
Posts
12,647 -
Joined
-
Last visited
-
Days Won
38
Content Type
Profiles
Forums
Articles
Downloads
Gallery
Blogs
Everything posted by neil9000
-
It doesnt care about your GPU as its not used, it's all down to your CPU clock speed.
-
No we cant link bios files. Have you actually checked in Retroarch that it is the correct bios like i asked? The name may be the same but that doesnt mean it is correct or will work, retroarch will say its present if correct, like you can see in this image. Both my JAP and US/EU say they are present.
-
Error fail to load is usually because the game or the bios is wrong/broken,if you load the core and go to info in the main Retroarch UI does it show the bios as present? Also you dont need to scan the games into retroarch, but if you are and its not seeing it that usually only happens if you dont have the core for that system downloaded. My games imported there fine but mine are in CHD format. Also when you try to load the game in Retroarch you are loading the .cue right not the .bin, bins dont work in the beetle saturn core.
-
Not that i'm aware of, and if you just want to pick out specific roms from a romset you will need a non-merged romset which is the biggest in size, aroung 110GB if i recall you cant just pick games out of the other two romset syles as the will rely on other game zips and bios as well in order to run a lot of the games.
-
They should work for the most part, romset and emu version should really match but that should be fine. If not just download the 0.201 version of the emulator and use that.
- 16 replies
-
- mame
- initializing
-
(and 2 more)
Tagged with:
-
To be honest with you you would be better off grabbing a new romset. In order to update to 0.202 you would need every single MAME update pack between 0.141 and 0.202, so thats 62 update packs you need to find and download. You update using clrmamepro here is a tutorial. But that is a very long winded way of doing it and would take forever to update 62 packs, even if you can find them all, which i highly doubt. As i said it would be a lot simpler and faster to start from scratch with a new set.
-
Yeah thats the new import method and what you should use, it works with any MAME romset type.
-
It depends what tutorial you watched, we have a new MAME importer for fullsets and that is what you should use, it will work with any romset type.
-
Could be a video driver incompatibility in Retroarch, what are your system specs and what is the graphics driver set to in Retroarch? It could also be a shader incompatibility if you have turned any on.
-
I actually have both on my system, split and non-merged. I keep the non-merged so that if i setup another Launchbox on a smaller system or a Pi i can just pick the specific games i want with no issues.
-
Also you can just add your romset to MAMEUI and that will audit and list all the games, short and full names,in a windowed UI unlike the commandline version.
-
Either your bios or you chd's are bad is my guess. I use chd's myself in retroarch for psx and they work fine. load the core and go to info in the main Retroarch menu and check it likes your bios files,it will have a checksum to match against your bios.
-
Well those are two separate things, the text list view will only ever be text, hence the name. If you want clear logos you cant use the text list view. Recently played has to be coded by the theme maker, and very few bother with it at all. I personally am not a fan of cluttering the platform view with recently played art, but hey each to there own.
-
Also it would be helpful to know if you have a full romset and which version and which version of the emulator you are using (the versions should really match for all games to work) and whether you used the new MAME fullset importer wizard or the old import roms method when you imported your games. I have a feeling you used the old Tools/Import/Roms method which could be why they dont work correctly depending on your romset type, for example if you have a split set that method wont work correctly hence why the new fullset importer was implemented as that will work with all three romset types. The old method would only import the Parent roms, but the games also rely on files that could be in other game zip files, but Launchbox doesnt import those files so they are technically missing when loading a game.
- 16 replies
-
- mame
- initializing
-
(and 2 more)
Tagged with:
-
When you test them in just MAME are you loading them from the MAME UI or via commandline? You have told MAME the correct folder location for your roms correct? It needs to know where they are obviously in order to load them, you cant just give Launchbox the folder path as MAME needs it as well. As @DOS76 said above that error is simply saying that it cannot find your roms, so it sounds very much like a path typo/missing path completely issue.
- 16 replies
-
- mame
- initializing
-
(and 2 more)
Tagged with:
-
-
Startup Screens, Pause Screens, and Bezels Discussions
neil9000 replied to Jason Carr's topic in News and Updates
Yeah the difference is Jason would have to do it for every emulator, not just the emulators that you personally use. So that is a lot of emulators as Monkus said even obscure ones that only a handful of people use would need doing in order for it to "just work" for everyone, then as mentioned as soon as a emu changes it breaks. There is no way that Jason could keep up with every little change to every little obscure emulator, thats just not feasible and would obviously detract from general development if he is having to track down and read through all the changelogs for all the emulators out there. At the end of the day for people who need that level of support there then Rocketlauncher already covers that and i suspect that people who need it are already using that, so they can continue to use that if they so please. -
I personally use HIgan retroarch core for snes its more accurate but needs a beefier CPU than snes9x does, i also use Redream standalone for all the Dreamcast games it currently supports, and only use DEMUL for the games Redream doesnt support (which is the WinCE games mostly). Rest of that list is the same as mine though.
-
Then there likely isnt PAL/Japan artwork for those games on our or emumovies databases. I have a lot of Genesis in my covers even though i named the platform Sega Mega Drive and have Europe as my preference in the priorities.
-
The Launchbox Database uses the USA region as the default for game names, metadata and images, other regions can be added but they need to be specifically marked as a different region in the database when you add them otherwise they will be rejected as the wrong image for the region. As for it still showing the wrong region image in Launchbox, yes you will need to refresh the image cache first, all images get cached to a cache folder for quicker retrieval so that needs to be cleared of the other images first.
-
It is so that you can call the platform whatever you want, but still have is scrape the correct info. For example if you name a platform NES launchbox doesnt actually no what that is as NES is not in the database, Nintendo Entertainment System is though. So you can name it NES but scrape as Nintendo Entertainment System so you get the correct platform information and correct game information for NES.
-
If you dont use the default platform names when importing and type your own instead you can set it to "scrape as" a platform for media. For example i have a "Sega Mega Drive" platform but i set it to scrape as "Sega Genesis" so i get all the correct information.
-
Sounds like you havent set up the emulator in Launchbox correctly. Also i would agree with @CDBlue and use a different one if i was you.