Create an InputStation Diagram for every console controller currently used in RetroPie Libretro cores #2
Comments
|
Those look great and fit very well in the Wiki pages imho! Great job! |
|
I noticed that in some of the diagrams the color gradients for the controller bodies seem to be faulty. This might be due to resizing the controller and the gradient anchors not moving as well (I think this might be an Inkscape problem). It's very visible on the second and third but last schematic in the post above... |
|
Yeah I just realised that, my laptop screen has horrible quality so I didn't quite notice and yes I think you may be right it is an issue with inkscape. this seems to be a viable fix potentially: |
|
Ok: These are the before and after. second one is the newest one- I'll change the others with the gradient option selected in inkscape. |
|
Looks much better now, thanks for taking the time to look it over again! Not your fault...I think Inkscape's behaviour in regards to gradients is often times very dubious ^^ thanks for the link! |
|
Ok, so this is more of a question of personal preference. Thus far my method has been to start with a paper space of 1920X1080 and resize the controllers to all fit within that space as best as possible just for consistency's sake, and then I save all the SVGs with the same 1920X1080 paperspace but for the final png files that go onto this page and subsequently the retropie wiki I've resized it to page content so there isn't all this extra white space. Would you prefer I resize the svgs to page content as well rather than 1920X1080 paperspace? |
|
Your current approach with having a fixed page size of 1920x1080 for the vector-based formats and then exporting with the page fit-to-content is totally fine with me! Maybe I should have gone for a fixed page size for the controller sources as well. I do try to construct the controllers such as that the relative sizes between them somehow reflects the real proportions (I have them in a single huge file and separate them from there). But when saving the single files I fit the page to the content (as you do for the raster graphics exports). If it's ok with you I'd propose we continue with the way the files are now. |
|
I figure as long as the proportions for the controllers are correct with relation to itself, that's most important as these are mostly going to be on their own pages rather than being with other controllers. So how you've done it is great :) I should be able to redo all the controllers and finish up the ones you just added by the end of the day. Once everything is finished we can discuss the best way to add controllers to the RetroPie wiki. I'd also like to get these on the libretro wiki if at all possible. |
|
I will try to finish the rest of the controllers tomorrow I hope. I also thought about asking the Libretro project if they were interested in the graphics. I think it would make a great addition to their wiki as well...the tables they currently use are ok, having the controller as a base for button placement would make a nice addition though imho. Lakka.tv does have some controller art though that they use in their CrossMediaBar-inspired menu...or alt least it seems from the screenshots/mock-ups I have seen. I haven't tried Lakka myself yet... |
|
Sounds good, I haven't checked out lakka either, I've seen videos on youtube of it, but never installed it myself. So a couple questions on retroarch controls- the documentation is kinda sparse (quite frankly this is probably the first real documentation on it) For Virtual Boy- is the right dpad used by the right analogue stick? (I don't have any controllers with an analogue to test) Are Dpad controls interchangeable with Analogue sticks? this changelog seems to suggest that they might/could be: http://www.libretro.com/index.php/retroarch-1-0-0-2-changelog/ |
|
I am not completely sure regarding the Virtual Boy mappings, but I can test it on my system since I am using an Xbox 360 pad as my main control right now. As for the Dpad controls and analogue sticks it always seemed to me that it would make a difference with different Retroarch cores. I have an open issue with RetroPie that includes a kind of similar "problem": when using my Xbox 360 controller with the wireless receiver a specific RetroArch autoconfig file is used that maps the Dpad as an analog input (and thus to a RetroPad *_axis mapping). At least for the cores I tested this seems not to work for me (no directional input possible). I have changed my driver configuration to use the Xbox 360 digital dpad as digital inputs and the shoulder buttons as analog inputs and use a modified autoconfig file for this. For me this does seem to represent the real controller much better than the default config that is currently used. I also talked to the RetroArch people about this but couldn't get any definitive answer. There is also another open issue from yesterday at RetroPie I think where someone seems to have the same problem with his wireless controller. Not sure if I may have misunderstood your question though ;) It would theoretically be possible to map an analog stick to the (analog version) of the RetroPad Dpad mappings...in my experience not all cores can use this though... |
|
Yeah from what I've read it hasn't been very clear- the only one that really seems to work on switching from dpads to analog sticks is the PlayStation and that's only after the retroarch.cfg is changed to one or the other, rather than it being automatic. I was mostly just curious as all my diagrams have dpad inputs and just wanted to make sure I wasn't putting dpad when it should have been analog. |
|
Nah, I think it's totally fine to map all those pads as digital pads! As much as I like RetroArch and the idea behind it, their documentation in regards to controllers and controller configuration is very lacking imho. When debugging my pads I was hoping for some kind of overview over their variables regarding controller config files, but couldn't find anything except the joypad config program that produces those files (no real API reference). Perhaps we can improve that a bit with our efforts... |
|
Yeah documentation is lacking a lot- I think part of it is that libretro/retroarch are typically used in the backend and managed through things like emulationstation/lakka. but what we're doing will definitely help. In regards to the Dpad question, I guess Floob answered my questions with his latest video: https://www.youtube.com/watch?v=mEg_OrlMUFU he shows how to use the analog with with the dpad as well- looks like its interchangeable for most if not all the retroarch emulators. good to know. |
|
Ah, yes, that's good to know! |
|
Also in regards to controller configs it looks like they recently added a core remapping option in the rgui where you can change the default core inputs so that instead of the default buttons on the diagrams it would allow people to map the retropad controller differently. It doesn't work on the current build but it is there in the menu. http://blog.petrockblock.com/forums/topic/core-input-remapping-options/ |
|
That is an amazing option, one I have hoped for for a while. For me, the standard mappings of almost any 2 button console to be A and B contradicts with the way I hold a (modern) gamepad. I'd much rather have the 2 buttons at the tip and the bottom of my thumb... |
|
I just tested the new build (retropie RC1) with the core input remapping options and it worked pretty well, unfortunately its only on some emulators so imame4all libretro still needs to be modified manually in order for the coin insert button to work, but I think fba-libretro has core input remapping. |
|
Hi and sorry for the delay. My wedding took some time away from the project ;) I still haven't tested the core remapping options but it is good to know that it seems to work now. What I would still love to have is some kind of emulator mapping graphic once an emulator is started. I will detail that in another issue... |
|
well congratulations!- your marriage is far more important- gizmo98 just got married as well, and I just had my one year anniversary :) I think a graphical interface is a brilliant idea- It would be cool as part of the retropie project but as far as coding goes I think it would be far more beneficial for it to be directly integrated into retroarch rather than specific to retropie (which I'm guessing you've probably already considered) I'm starting a programming course soon so maybe after i finish it I may be more useful in the coding department. |
The following is a list of all the consoles RetroArch Emulates: Items in bold indicate that InputStation diagrams have been created and added to the RetroPie Wiki.
RetroArch Consoles
Non RetroArch Consoles:
Note: Will add final products to new section (InputStation Controller Diagrams) of each emulator page in the Retropie Wiki
3do
Atari 2600
Atari 7800
Atari Lynx
Atari Jaguar
Gameboy
Gameboy Color
Gameboy Advance
Game Gear
Mastersystem
Megadrive/Genesis (3 Button)
Megadrive/Genesis (6 Button)
Megadrive/Genesis (6 Button) Arcadepad
Nintendo 64
Nintendo DS
NES
Neo Geo
Neo Geo Pocket
PS3
SG-1000
Super Nintendo
Sega Saturn
Turbografx16
Videopac/Odyssey2
Vectrex
VirtualBoy
Intellivision
Sega Dreamcast
Xbox 360
PlayStation 3
The text was updated successfully, but these errors were encountered: