@mitu Forgot about this! Thanks for the reply! You're right the theme works fine with RetroPie 4.8 on the download page. I read that the theme would break....I don't dare update 4.8 though! (I may DD it beforehand and then try!).

Since you asked which theme it is (but it might be a little sketchy):

I certainly don't expect any support here for it.

Also when I installed 4.8 the slowdown when using shaders is much reduced and actually tolerable now. Happy days!

Next item on the agenda is to read up on overclocking the Pi3B+ because I wouldn't mind having run-ahead enabled.

Cheers mate!

@davidrasmu the default password for retropie is “raspberry”. But if you’re getting a rainbow screen and nothing else, something is wrong and you might have to reimage and start over.

@mitu Now Solved. A Big thank you for your help.

In the end I realised it was actually a faulty USB cable.
Swapped the cable and then the Xin-Mo was detected straight away. No need to install drivers. Configured the buttons for player 1 and was good to go.

I'm now going to research into joystick deadzones. There seems to be excess travel to activate the micro-switches which causes an in-game delay. I have Zippy joysticks but will research into an alternative that has a smaller deadzone for faster response delay.

I'm sure other people have experienced this, there must be a wealth of knowledge about better alternatives to the Zippy joystick.

Nevermind. I figured it out.

@mitu thanks but still could not get to work - I've found instructions on how to reformat a retropie SD card on mac, will just start again with fresh image :)

Thanks for the reply. I tried to do an upgrade, but it had many failed packages. So I ended up downloading the latest 4.5.1 Retropie image and building everything again from scratch.

@mitu that worked! Now I'm getting an error "1v10: VolumeControl::init() - Failed to attach to default card!" But the sound is working, so I dont know if it's a big deal or not.

@mitu Hi thanks for your help , I have worked out what the issue was.
When I put in username and password and deleted the # in front of userCreds I deleted the 'u' and
then changed it to UserCreds.

Linux is case sensitive so it did not like the change.

Put it back to userCreds and working fine

I also put [screenscraper] just above.

thanks
Jimi

@lostless I set the system to save from RAM every second and the issue appears to be fixed not just corrected. I was also getting little periods were the sound was muted and that also seems to have stopped. I was assuming that was a different problem and that was why I did not include that in the original question, but that has stopped as well. Great information thank you.

Could be a throttling issue. I have decided to move the amiga games one folder at a time into the roms folder.
So I will scrape all games beginning with A in the roms folder.
I'll then do the same with B etc and create a number of gamelist.xmls
I'l then do a merge of the gamelist.xmls and edit it to point to the correct folders.

A bit of work but it should hopefully do the trick rather than scraping all at once in different folders.

Regards
Jimi

@pegasus1130
I am dealing with a similar issue and I am now very, very close to getting it working. I found a post from a year or so ago which suggested that opening the retroarch GUI from within the emulator, then remapping from the "control" menu therein. For me, this involved hitting f1 on a keyboard to bring up the retroarch gui and then switching each button around according to the results of jstest, and finally saving a "core remap file". This let me fix everything but a few buttons. The issue that remains is that there is no listing in that controls menu for buttons 0 and 1, which are my C up and C right.

@rogeriol Please open a new topic and add the info requested in https://retropie.org.uk/forum/topic/3/read-this-first, don't bump old topics.

@mitu of course
Sorry

@RpiBeginner feels like a defective sd card for me

For future note: I removed the dependency to WiringPi now. Please see also https://retropie.org.uk/forum/topic/23328/powerblock-driver-quick-installation-fails/5.

@davidc100 Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

@dbrown1986 said in Running Rpi on a Ubuntu terminal...:

As it stands, I've attempted this but the terminal reports ES cannot start without a graphics driver (even when gnome and Nvidia drivers had been installed but disabled in favor of the terminal).

Yes, the drivers you installed work with X.org.

Ideally, what I'd like to do is to install only a terminal, apt-get only what I need and autoboot into ES on boot.

The RetroPie installation script should already do that - auto-login via the current DM and starting Emulationstation into an X.org session.

Is this feasible?

Not without X.org at the moment.

@mitu So when I got home I took the microSD card that was in the raspberry pi zero W that I think is faulty. And just moved it over to the new raspberry pie zero w that arrived in the mail today. And it seems to be working a lot better. It booted up just fine to EmulationStation and I’m not getting any of the button issues that I was having when I had it in the Retroflag GPi case. It occasionally gave input configuration crashes too.

I tested only one Atari game on it and it seems to be working (where as before I could never keep it from crashing long enough to run a game). However I’ve only started transferring games over and havent tested any others. Either way it’s not freezing like it was just a few seconds after loading up emulation station. And it has yet to crash. Which means so far that’s a really good sign.

When I’m done transferring the files over, doing a scrape for the game images, and can actually spend some time playing games on it. I’ll be glad and certain of what the issue was. But based on all the trouble I was having and I’m using the exact same microSD card with everything that was installed before. So far I’m convined that I had a faulty raspberry pi zero W.

@ignatius
That might happen if you run out of memory. Using raspi-config to set the virtual memory GPU memory split to 256 could help, and disabling the graphics option "Retain changed textures".

Unfortunately, the problem with this game seems to be rendering gameplay, the battlefield is missing it is all black.