Hi, not sure if I’m asking this in the wrong place but here goes.
I’m using EmulationStation on a Windows10 PC and I have added a number of sections and additional standalone emulators for Gamecube, Wii, PS2, PS3, Xbox, Xbox 360 and 3DS. I have managed to make system artwork for all of these but I am unable to source additional controller artwork (red outline controller images). Can anyone help?
Thanks
These are probably custom by the theme author. Which theme are you using?
Can I assume Carbon and it’s SVG controller images?
Yes, those are the ones.
I’m also having difficulty getting Xbox logos to show correctly, they show up as black and white despite being colour images. Can anyone advise?
The system and controller images that Carbon uses are actually vector SVG files.
I think I know where the author sourced his logos from but the controller images would have to be created.
I use Carbon myself, (Although on an ODROID using Batocera.) I think I can justify making room in my schedule to do the controller images. I will also do the system images.
I can obviously only do one at a time and will probably have to split my time between multiple projects.
If you could choose only one system which would it be? I will do that one first.
If that one meets your approval, and you are patient, I will do the rest as I have time.
Here is a 10 minute WIP on a Game Cube controller.
Obviously it needs buttons, sticks and a d-pad, but these things should be pretty quick work.
Another 10 minutes.
And done in another 10.
The system graphic will be even quicker.
I can modify the theme xml files for drop-in convenience and add this to a folder in my repo for testing. (If you want. 
)
We would have to decide on a folder naming convention for the new systems if one doesn’t exist, (Something in line with the existing ones.) if there is any hope of doing a PR and getting these included in the theme permanently. (Which would be cool!)
I have added this one to my Front-End-Assets repo. (Including SVG system art and supporting xml.)
If this one works for you I will move forward on this project.
Thanks for the inspiration!
Edit: I usually include the source in my distribution but since the final output is vector, there is no need. 
Wow, fast work, thanks. I was going to suggest that Gamecube would be best for a first choice. Unfortunately the SVG file doesn’t seem to work with my EmulationStation. If I can work out why it may explain why I’m having issues with other SVG files.
There is a Github for Carbon here: https://github.com/RetroPie/es-theme-carbon
Going through the newer systems these are the incomplete ones that I have identified. I’ll try to share what I have as well. Parenthesis indicate system names I have used. Scraping can be done successfully from Screenscraper and Thegamesdb using these.
It may be the SVG format.
Let me do some research. (It may have something to do with internal CSS etc.)
I have changed export options. Try it again please.
Here is a PS2 controller.
I will wait to add it to the repo until we figure these problems out.
If need be I will load the SVG into Inkscape and export it from there.
I can supply all the system art myself. (I usually work independently. Plus I have access to very high quality vector source.)
Edit: I did some research and exported the SVGs again. Here’s hoping.
Your folder naming scheme works for me with the exception of the Game Cube, which I think should be gamecube.
For the 3ds I think a simple modification of the nds will work.
I was having a little trouble with it then I downloaded it again and it worked perfectly. I think I may have had some version cached.
I absolutely agree about gc/gamecube but I didn’t invent it, gc is the current Carbon theme name for Gamecube. if changing it won’t cause confusing then you have my support at least.
Happy for you to do the system art, I wasn’t happy with my custom work and I doubt anyone else would be.
I think it may have more to do with the final change I made after R&D. ES seems to want everything grouped together.
If that the name Carbon is currently using then I will by all means change it.
So it seems we are good to go. 
What did you think of my system art?
Thanks again for the inspiration. This will be a fun little project, almost a mini vacation from my usual photo real work for the Mega Bezel.
If you are not familiar with that project then stop by the thread for a read.
https://forums.libretro.com/t/duimon-hsm-reflection-shader-graphics-feedback-and-updates/28146
It looks fantastic, it fits perfectly with the existing theme.
I think this will get a lot of use going forward as the Raspberry Pi/Retropie community advances. People are already experimenting with Gamecube on the Pi.
That is good. I am going to work on this for the next couple of days and see how quickly it goes. If all goes well I’ll do a PR (After I learn how.) and see if we can get them included in the theme.
I look forward to it, Thanks.
Just in case people are interested, this is how I got the various systems working.
Nintendo Gamecube: Has an existing Libretro core, Dolphin.
Nintendo Wii: Also uses the Dolphin core. I couldn’t get the Wiimote to work with the Libretro core so I used the standalone Dolphin app with the following command [location of Dolphin executable] -b “%ROM_RAW%”.
Nintendo 3DS : Has an existing Libretro core, Citra.
Nintendo Wii U: I used the standalone Cemu app. My games are in Loadline format so I wrote small batch files to point to the executable game files. The batch file text follows this format [location of Cemu executable] -f -g [location of .rpx file] The .RPX file is usually in a subfolder of the game rom named CODE. Use “%ROM_RAW%” in es.systems.cfg to open the .BAT file.
Sony Playstation 2: Has an existing Libretro core, PCSX2.
Sony Playstation 3: I used the standalone RPCS3 app. Follow the instructions for Wii U batch files except the batch file text is just [location of RPCS3 executable] [location of EBOOT.BIN file]. With disk games the EBOOT.BIN file will usually be in the USRDIR subfolder of the game rom. With EPUB games it will be in the RPCS3 app folder, usually in RPCS3\DEV_HDD0\GAME[name of game]\USRDIR
Microsoft Xbox: I used the standalone XEMU app with the following command [location of Xemu executable] -full-screen -dvd_path “%ROM_RAW%”
Microsoft Xbox 360: I used the standalone XENIA app with the following command [location of Xenia executable] --fullscreen “%ROM_RAW%”
If anyone has a less clunky way to load Wii U and PS3 games please do let me know, Thanks
I use Rocketlauncher as an abstraction layer to launch PS3 & Wii games. The front end calls Rocketlauncher in the traditional manner, like it would any emulator. The internal Rocketlauncher module takes care of the messy work.
Are they on the same repo? I can only see your Gamecube work.
I probably forgot to commit. I’ll check when I get home.
OK, they are up now. 
Here is an XBOX controller.
For authenticity I went with the original “Duke” controller.
It is in the repo.
Here’s the XBOX 360!
It’s in the repo. 
The forum won’t let me reply again without waiting for someone else to reply first, so I will just add this last one.
The 3DS. This completes the request!
This one is just a modification of the existing NDS controller graphic, so it may not exactly measure up to the others, but will of course fit right in.
I am thinking I may make a slight change to the XBOX controller. I like the solid “X” on the 360 so much that I may solidify the “X” on the XBOX and add the XBOX text below. I will make the change and get your opinion.
I felt the lines were too thick on the 3ds so I made them thinner. Not as easy as it sounds because the author converted all the paths to fills. (Maybe there is some SVG benefit?)
Here is a shot of what my XBOX change looks like.
Let me know what you think. 
(Personally, I think it looks unfinished the old way.)
They all look great. The new 3DS image does look that bit better with thinner lines.
I am having one small issue, the Xbox360 system logo is just solid black in Emulationstation. I had similar problems my Xbox logos I made and with a Switch logo I’m trying to create.
.svg){kind=link}