I forgot to mention, here is a list of emulators that definiting don't work. N64 - Works but extremely slow. Dosbox - Does work eventually. Sega CD - Doesn't boot at all. Dreamcast - as with N64 PSX and PS2 - have not tried but suspect the same as N64 Amiga - emulator won't install Sega 32X - does work but is borderline slow. Some games work are very slow, others are fine. I think I will persue this one. Knuckles Chaotix is very slow. New emulators that work: Apple 2 - requires keybpard Colecovision - requires keyboard. Will try zx spectrum and C64 next. Regards

@mitu I got it working with the runcommand now. Only a small visual issue (no progress bar while downloading a game). But I found a bug in downloadAndExtract, and I opened a pull request :D https://github.com/RetroPie/RetroPie-Setup/pull/2628

Hey! A bit late haha So... I don't know much of cmake, but I ALWAYS like to start by the official website and documentation. I found an official tutorial on the official website: https://cmake.org/cmake-tutorial/ Not the BEST answer but I hope it helps... Cya!

@mitu oh wow, never thought about something like that! Thank Mitu, i will have patience next time! 😊

@wetriner said in ES Themes Menu Revision: @herb_fargus said in ES Themes Menu Revision: Another suggestion would be a culling to keep well maintained themes and leaves the others to an auxillary script. I think this is a good option as well. I also like this idea.

The RetroPie-Setup scripts use a helper script - joy2key - to navigate and enable buttons in dialog enabled scripts. Take a look here to see how it's started/stopped. You can source the RetroPie-Setup helper.sh or copy the functions you need from it in order to use it in your script.

Just my findings: commit 0343e3dbd8a22f64698e824e30b08e0887d77b6b Author: retro-wertz retro-wertz@users.noreply.github.com Date: Sun Mar 4 21:47:52 2018 +0800 Add missing variable to save state This is the commit that breaks the loading of existing state files from old pi's. And for anyone's future reference: here is the github issue regarding it: https://github.com/libretro/libretro-fceumm/issues/215

@herb_fargus said in Software dev questions.: @jcode said in Software dev questions.: All of my questions are dependable on what type of software i wrote? If it's software that includes links to roms or downloaders for them we obviously don't condone it because it will do nothing but damage the project and earn you a nice ban. But there are plenty of web/theme managers scattered throughout the forum so if it's similar to those I don't see an issue with sharing it with the community No...the software does not contain any illegal stuff. I would never do anything to hurt RetroPie and it´s community. Thanks for your answer.

I love this theme sooooooo much. I'm a proper 80's boy! Is there a way to extract the music from this image please Coin Junkie? I have FTP'd into the image but can't see the audio files? Thanks for the great Theme!

@haleice there is no variable that can be used for game images. You are limited to the media files specified in your gamelist.xml. Variables are only available for system related images or text.

I was scrolling through the commits of the recalbox emulation station build and I'm curious if the following commits can be merged (maybe just partially) into the retropie version. From what I've seen and understood, those should add support for themeable menus and add an extra menu to directly switch theme settings in the GUI. Main commit helpBox fix transition tag (not quite nessessary but would be nice to have)

@kkokkinos There are a few GPIO based controller drivers available in RetroPie: https://retropie.org.uk/docs/GPIO-Modules/ https://github.com/recalbox/mk_arcade_joystick_rpi I think you're trying to use the mk_arcade_joystick_rpi one ? If so, then you need to install it first from the RetroPie-Setup script (it's in the drivers section of the packages) and then configure it - as described on the Github page of the driver. You can ignore all the installation steps and just look at the pinout and make sure you connected the wires correctly, then jump to the Loading the driver section. There is no recalbox.conf file in RetroPie, that is part of the Recalbox image -a different project.

@mitu said in How to setup my game into raspberry pi?: the Emulators shipped in RetroPie support JavaScript based games (if your game is programmed in JavaScript), you'd need a browser to run it. RetroPie does not ship with a browser, but you can add it by install i see, cause this project im working on now required to be play on web browser(thus the .js format) and also on an arcade machine(where my problem come in, the installation on raspberry pi) So this mean my developer will need to code in perhaps in a coding language that can both run on web and in retropie ?

@tjsgaming look around here i found this. i want to get a ATB just to play around with but now its going to have to wait. at least i have a XU4 now to play with :)

I have the new image working with roms but my configuration section is empty except for "Arena toolbox"

@cyperghost yeah, I will try to do that

@pjft Thank you kindly, sir. The warm welcome means a lot, but there's no need to worry. I'm still somewhat swamped until after the holidays, but I do plan on keeping a tab open here to help out with the most recent round of spammers. Those guys are relentless.

I think this is a good idea, though not one to be taken lightly. Refactorings and cleanups are often double-edged swords, and while I am always supportive of investing time in such endeavors, I fear that we may introduce new bugs and/or remove code that was put there for a reason, even though it might not be at all apparent. If the scope is more or less well defined upfront (i.e. if we determine that we will look into the screensaver code, or something more), I'm fine with that. I'm not sure this needs to necessarily be a cross-coordinated effort, though - these efforts are always welcome as long as they're well tested, I believe. There are a few things on my plate that I'd like to look into, ES-wise, that don't fall into the "new developments" area but rather in the "fixing/improvements" area, namely (in no particular order): Document OMX and collections features, namely Predictive Profile (High 4:4:4) not working [EASY-ISH] Address textures defaulting to white after returning from an emulator. [MEDIUM?] Improve texture cache to reduce texture pop-in. [MEDIUM?] Fix or mitigate VRAM handling, especially on out-of-memory scenarios. [MEDIUM?] Try to get rid of the two video player options, but rather have a default hardware accelerated player for the Pi that works as intended (i.e. respects the actual layers, rather than being a separate process). [HARD] I honestly have no idea how to go about several of these, but I secretly hope that with a proper Windows and VS debugging environment I'd be able to make some progress here. Thanks for starting this.