I think that it is, but I have no clue how it works.
I just grabbed the latest build, and it seems good so far. The one thing I’d want to point out is that some fairly “mainstream” resolutions are still missing. No 512480 (ideal for NES games for most HDTV owners), 384448 (CPS-1 and 2), 608*448 (some Neo Geo titles including Metal Slug). I’m sure there are others, but these, especially the NES one, should probably be standard.
As above, I’m finding the per-core config a bit complicated to use, and I assume it’s not quite finished yet. On startup, RetroArch loads from retroarch.cfg, and the “current” core is not updated in this file if you’re using per-core configs, so you always start out in the core most recently defined in retroarch.cfg. However, you can create config files for each core and manually load each one after startup from the main menu. This way you can keep different resolutions for each core, but you still need to load the specific config file first. It’s easier than manually switching up custom resolutions for each core, though.
While you can set a ROM path in each core, it doesn’t seem to be honored, and all the cores still seem to open into the directory defined in retroarch.cfg. Maybe there are supposed to be separate config directories for each core rather than just a config file per core? I’m not sure, but I imagine it’ll get less complicated as it matures. In its current state and with my understanding of it, it’s not entirely satisfying.
EDIT: I’ve also just noticed that both FCEUmm and Nestopia cores seem to be outputting an image with dimensions 240224. Native NES res is 256240, so I assume the purpose of this is to crop out overscan garbage. QuickNES still outputs a full 256*240 image. This is the kind of thing I think would work great as one or more Core Settings. Some games may not need cropping at all, some may only need the leftmost column of tiles cropped, etc. Perhaps two core settings would work best: “Crop Horizontally: Left / Right / Both” and “Crop Vertically: Top / Bottom / Both”? The current “always-on” cropping in FCEU and Nestopia seem like overkill.
I certainly hope it’s not final(can’t even save 240p modes) and I can’t imagine this “per-core-config” working well anyways.
Might sound far-fetched but wouldn’t a per-game-config make more sense? See, if we can’t automate the specific video modes when so many consoles use multiple modes then a per game config would work perfectly. Games that don’t have a config simply use default settings.
Uhh, I still get an orange and half-speed hbc when switching cores and launching roms from time to time.
Per-core config will not go away.
What we may consider is giving you per-game configs as an optional extra though.
Dear SquarePusher!
Per-Game video config will be simply awesome. Please, move forward! Count on me if you need any help on testing! This way we will be able to have perfect screen sizes in NeoGeo and specially FBA games!
Best regards, and MERRY XMAS!
C.
I think it’s clear to all involved how per-game configs would be a useful functionality for some games and platforms; I don’t think the feature needs to be evangelized. If someone feels it’s important enough to do and has the knowledge and time to do so, they probably will. As is, per-core configs are already an adequate solution for a number of platforms, especially most handhelds, which only ever need a single resolution. If you “don’t see it working well”, you’re focussing on the specific circumstances where it won’t at the expense of the myriad situations in which it does.
Updated to lastest commits:
-You can now custom keys, there’s a small issue in wiimote controllers, let say, you are playing and then you go to eat or go to the bathroom, you can take a while in any of them, (specially bathroom, what have you eat dude?), when you are back, classic controller is turned off, then you turn it on, but it retrieves default key binding.
-Issue: per core config, in this, I get help from what Vague Rant said, you can save/load cfg’s files for each core, but if you need to restart RetroArch, it still loads retroarch.cfg, and you can search and load your saved cfg file. I think a good behavior, could be:
//in retroarch.cfg loading or rom (content) loading
//loading gambatte
config.lastcore = "gambatte.dol "
if (!hasPreviousConfigFile("gambatte")){
//continue loading default settings
}
else{
//Reload / override last config file
loadSettings("gambatte.cfg")
}
Something like that.
I was misunderstood, I didn’t want the per-core configs to go away as well, for those same reasons you stated.
The reason why I said that it “wouldn’t work well” was because it lacked the addition of per-game configs. The intention was to combo both features.
The fb_alpha core is giving me a black screen on the latest build.
is there any chance of uploading the pre-release or commit of v1.1.0?
Yeah, give some minutes, my machine it’s working right now on it!
But remember, it’s only for testing not official.
Edit: Here you go:
http://depositfiles.org/files/5uz5jio9e