I do prefer everything in a game specific file, not just the DS buttons.
Don't see a reason why I would want to change DS buttons anyways.
Savestats and Screen swapping is most important I think.
Even if there's only a global config file at first it would be fine for me.
Don't see why I would want to change such things per game.
I think PCSX has the best solution here.
The external gamepad settings are stored differently to the Pandora buttons (no reconfiguration needed when unplugging the External Gamepad).
DraStic uses a global configuration file, and you can make game-specific ones that override it. I was just wondering if I should even get the non-DS gamepad options from the game specific file, because these feel like more global options by nature. I guess I would do it this why if you were configuring inputs for the GUI control, but it'll just be limited to things that take effect while the game is running.
There should be no reason to have separate configuration files for internal and external controls here, the configuration will store something like 0-4 inputs for each action. I can't think of a reason why you wouldn't want to have both the Pandora controls and the external controls set to trigger actions at the same time. Or maybe this is actually what you were saying?
Shenmue said:
Any chance of screen rotation in the next release?
I have to ask notaz how to do this.. again :/ (if you're reading this notaz, if you send me an e-mail I promise I won't have to be reminded again)
This really kind of complicates things because something like 1x:2x mode would no longer work since the screens are now virtual 192x256, and 384x512 won't fit on the screen without clipping. I'm really kind of loathing the idea of adding more and more different screen modes. Maybe it'd be best to just have a custom configuration option. It wouldn't be very GUI driven, it'd be more like you can enter this:
< Joined mode >
X: <pixels>
Y: <pixels>
width: <pixels>
height: <pixels>
rotate: <no, yes>
orientation: <horizontal, vertical>
Code:
< Split mode >
A X: <pixels>
A Y: <pixels>
A width: <pixels>
A height: <pixels>
A rotate: <no, yes>
B X: <pixels>
B Y: <pixels>
B rotate: <no, yes>
Joined mode would mean both screens are scaled but stuck next to each other, either left to right or top to bottom (maybe with an optional gap parameter). Split mode would let you freely position both screens, but screen B would be locked at 256x192. This is also assuming that can actually rotate fb0, I don't remember if this is the case or not.
I know some people would probably prefer a touch based interface that lets you drag things around, but I personally find this a lot nicer to work with. I could however maybe have a graphic that shows what the current setting would look like.
This would at least make it easier to migrate to Pyra, for whatever we have on that (hopefully will have full independent scaling and the option for using shaders and stuff)
Exophase is there any reason that Axe doesn't work?
http://pineight.com/ds/
IIRC it displays correctly but doesn't actually output sound...
I wouldn't know, I haven't looked at this or even heard of it until now. The source looks pretty straightforward, I can try to see where it's going wrong.
(as you quoted in your response..)
