RetroArch Wii Release (v1.0.0.2)

RetroArch Nintendo consoles
#41

Thanks for the explanation and clarification, that would certainly explain a lot of what’s going on. =D So with that said, let’s say we map the fast forward toggle to the right analog stick, and we want RetroArch to save that, do we need to change the mapping, exit, and then open up the emulator to make sure it was saved? When I changed the controls in one core, then I decide to change cores, but when I go back to the original one, the newly mapped key wasn’t saved. What would be the best way to make sure such changes are saved when the default retroarch core is loaded?

And also the custom resolution modes are probably still in WIP? Some emulators, like GBA, aren’t at the right resolution.

#42

I’m not sure what would have caused your problem with the fast forward control not sticking, but I agree that doing a “Restart RetroArch” after changing settings is probably a good idea. I’m not sure what the default is, but Configuration Save On Exit in General Options might need to be enabled for this scenario. I’m not certain what RetroArch does when this is set to OFF. Save in real-time? No save at all? Regardless, if it’s on, you can force a save at will by doing a Restart. I have had settings lost when a core crashes (e.g. FCEUmm lately), so by doing a restart before loading any content you should have the best chance of settings sticking.

EDIT: I should get in the habit of saying everything I’m thinking, then submitting. :stuck_out_tongue: I don’t think there’s currently a practical way to set custom resolutions for handheld platforms like GBA because they use obscure, non-TV aspect ratios. When you change the vertical resolution (e.g. from 640480 to 640448) what you’re really doing is telling the Wii to fill the top and bottom of the screen with 16 pixels each of black empty signal. So on a system like SNES which usually only uses 224 (448 doubled) lines, the other 16 (32) lines are still there, just empty.

Trying to apply this to GBA, though, you start to have problems. Let’s say the “sensible” hardcoded resolution for GBA is 480160 (or 480320 for HDTVs). Firstly, this means 40 (80) lines of black on top/bottom, but none on the sides, since RetroArch is currently set up to scale the image to fit the screen, horizontally (which is roughly what consoles meant for TV do). A GBA isn’t designed to do this, though, so if you set the resolution to 480160 or 480320, it’s going to look bad. The problem is RetroArch assumes an intended display width for all resolutions which is based on them being designed for television, which handhelds aren’t.

Slightly more complicated version: 480*160/320 with the video encoder width at 640 as RetroArch does currently will give you an image with the aspect ratio … 40:21, basically almost twice as wide as it is tall. The true GBA aspect ratio is 3:2, so this is about 27% wider than it should be. If you really wanted to use a hardcoded 480-wide resolution with GBA, you’d need to change the video encoder width to … 504 pixels. This would get you a 3:2 picture “accurate” to the GBA. But none of this video encoder scaling is currently available in RetroArch, it’s just locked to 640, so you can’t do GBA in a hardcoded resolution. Sorry to keep harping on this, but this is one reason why adjustable video encoder scaling would be great for RetroArch Wii/GC.

#43

I mean, fast forward does work well, it didn’t save when changing cores, but I’ll try that tomorrow :stuck_out_tongue: The other settings, like the ROM path, are fine and haven’t had trouble, and I also like how it has an auto-detect core setting based off the ROM file type, haven’t tested it yet. As for the FCEU MM crash, have you tried Nestopia? The emulation is actually better and has less issues, I personally use that (higher level of overall accuracy) =D

I’ll try the restart method and let you know how it goes.

#44

Using settings editor gui on Wiiu to change the hardcoded resolutions of the Wiiu can result different ly. So does starting RA from an forwarder opposed to the HBC. Also starting Settings editor gui from usb loader gx homebrew launcher also results in different behaviour ( Like an actual Wii changed the ratio meaning you have to set up your tv also for proper ratio )

In most cases this can result in black screens or background / sprite problems upon loading a rom in RA. As a fact you could say RA’s visual output can be determined on how you start RA or on how you prefer to change your Wiiu ratio settings.

I stumble upon this after I loaded RA from Usb loader GX homebrew launcher and after starting RA after applying settings in settings editor gui.

You can manipulate even on how the vWii behaves using various above mentioned methods. I do not know how RA gets it;s vWii ratio resolution info but, the “other” emulator do not present graphical problems regardless the the vWii settings. BTW this is not new. I could explain why some users have video problems on vWii using RA.

#45

Config is saved on exit, if that is set to off it won’t save at all.

#46

Thanks, AndresSM, I appreciate the clarification.

#47

Another way to make the config save the changes as I saw in other thread is to load a Rom, change what you want, go back to the main menu and load another Rom with the same Core. After that, if the configuration still applies, it’s saved.

I did it yesterday with some of the cores and it saved the changes, so if the above tips doesn’t work, you could try this too…

And, excuse me, Vague Rant, but you know a way to make save paths stick with the ones I want? Everytime I change them it reverts to the original one. I don’t know if i’m doing something wrong.

#48

Yeah, but does this save resolution settings? I don’t think so.

I am choosing a core, loading a ROM, then going to RGUI, changing resolutions, aspect ratios etc, then restarting RA to save the changes to the config. Aspect ratios save, even if I switch cores, but the resolution defaults back to 640 x 480 each time. I have Save Config on Exit enabled.

#49

No, doing that doesn’t save the Resolution, but the other ways doesn’t work either (And that’s why I use Custom Ratio in the meantime which Retroarch saves).

My comment was for the problem that Nintendonerd had with the Fast Forward input, although is my fault for not saying it… Sorry.

#50

Unfortunately, the 4:3 aspect ratio bothers me to no end, even if it is how older games were meant to be viewed in, as such, I use the HBC forward that Joostinonline wrote and it’s very stable, but like you said, it has a few anomalies and can cause RA to show a black screen every now and then (hard to reproduce, I don’t know how it triggers, it seems random). The forwarder forces vWii to be 16:9 after the system update, 4:3 just makes me OCD about it lol.

How to prevent the issue or make it so vWii doesn’t freak out, I don’t know.

No worries dude, I was merely wondering why it never saved that custom mapped control, now I know :stuck_out_tongue:

#51

You’ll get your resolution setting saved - just don’t bother me if you get problems if it applies it and you get a wrong picture at startup - this is EXACTLY why we haven’t saved those settings all this time.

But if you want it so bad - sure - we can play Russian roulette.

#52

No worries dude, I was merely wondering why it never saved that custom mapped control, now I know :p[/quote]

I had the same problem too, in my case it was the Rgui Button and after doing that it saved. I’m very happy to see that I don’t need to press L+R+Start+Z with the GC Controller anymore, it created a LOT of problems like resetting or freezing the game with GB, GBA, Pc-Engine/TurboGrafx games, and a few other from different platforms.

I must say that this issues are not caused by Retroarch, but the original systems themselves. But that’s not a problem anymore!

#53

I don’t need it that badly, like, at all, the default resolution is very good for all the cores I’ve tested… We were just confused at the feature’s inclusion to the Wii port of the emulator, now we know why it doesn’t work on a permanent basis, nor does it need to work permanently. I apologize for being a jerk about it when I had no right to.

So uh… think 'm gonna take a break from these forums to spare myself further embarrassment. =| :confused:

#54

If it doesn’t work in testing then you don’t need add it? No Russian roulette at all then I suppose.

#55

If it doesn’t work in testing then you don’t need add it? No Russian roulette at all then I suppose.[/quote]

I don’t know why I even bother asking for feature requests or make bug reports anymore.

#56

But it turns out it wasn’t a bug.

#57

Then we should probably forget about having it implemented in the Wii version, I mean, if it’s not a bug…how is it supposed to be used? Is it just there to mess around with? What about the per-core config not saving? That’s a bug right?

#58

Resolutions are pretty much a Wii thing. Per-core does save on all platforms I’ve tested tbh, you just have to exit retroarch cleanly.

#59

Then may I ask as to the purpose of having custom resolutions on the Wii port is indeed a Wii thing? I mean, isn’t it kind of a pain to change the resolution of each core every time said core is used?

#60

Personally, i stuck with the ‘‘beta’’ versions posted a week ago (and with the custom NGP 0.9.9. core) and never looked back. Saved aspect ratios per core, saved inputs, saved directories per core, NO codedumps after multiple rom loads for every core (bar the prboom one and the FCEUM one, but i much prefer Nestopia) and the ability to rename the cores and their respective .cfg files to my preference. Scanlines don’t hurt either :slight_smile:

Anyway, since i am away from home, only question is, for the quys who have tested 1.0.0.2 VBA core, has the VBA core performance improved in your opinion?