@GadeEmbossed well it seems my issue wasnt the same as everyone else's with the controller issue, but I have this adapter USB to ps2 controller that i had plugged into my pi. the adapter has the option for using two controllers, so i just unplugged the controller from one port and plugged it into the other.

@BuZz said in Issues Upgrading Wheezy to Jessie:

You should start from a new RetroPie image (eg v3.8.1) which is based on Jessie (or try the 4.0beta2 image released on the forum here).

Wheezy is no longer supported.

Starting fresh has healed all ailments. Appreciate the advice.

@dankcushions said in Need guidance: Best MAME emulator to use for classic 80's games?:

i also got mouse/trackball support working :)

WOOT WOOT!

@dankcushions

I meant the setting in unibios at the start up applies only per game

Once I changed the cfg AND the bios in the gui, the unibios shows up at the start, like it supposed to be, but in the default MVS mode

So I have to access the unibios with A+B+C, change to AES.

When I restart this specific game, it keeps the AES configuration.

But when I start I game I have never started before, it comes up still with unibios, but again with the default MVS setting. So I have to alter every game once on the first start, to be sure every game launches in AES mode.

Ok, its not a real problem, I just have to change it once at the first start...

But I guess when I would write "AES" instead of "UNIBIOS" in the config, it would always boot in AES mode. Will try this maybe tomorrow

Sorry, maybe I expressed myself wrongly, my,english is a little rusty...

Retropieproject is so great! I love it! :)

I forgot to mention that I'm running RetroPie 3.8.1 on a Raspberry Pi 3.

@XD3l said in Latest Release Breaks Ability to Configure Cores in RetroArch Menu and Keep Settings.:

It's fixed now. I manually edited the primary config file to save per core, etc. And now each core loads and saves with the proper setting again!

I'm afraid you fixed it doing something else. Because the "configuration per core" doesn't mean much on RetroPie...

But if it's working now, why worry about it?! :D

Have you tried this scraper?
https://github.com/retropie/retropie-setup/wiki/scraper

Also, if you need more help please post this info:
https://retropie.org.uk/forum/topic/3/read-this-first

Please start a new thread and include all the info smudger483 did above
https://retropie.org.uk/forum/topic/3/read-this-first

It would be worth mentioning you have completed all these checks:
https://github.com/retropie/retropie-setup/wiki/themes#white-screen-of-death

So, the random select seems to be working, and displaying the subfolders from what I can see. Great!

However, now when I select Shutdown System, it goes to a black screen with a blinking _ underscore instead of shutting off.

Edit: the same thing happens when I F4 out to he command line. The command line never appears, only the blinking underscore and black screen.

@Hypo Have you added additional themes? That can cause problems with white screen problems in some cases. The default carbon theme is light and should work fine.

And I can confirm the ES Syntax error is now resolved! Thx.

I just had the a similar issue, running Retropie 4.0-beta2.

After rebooting, I got stuck to the "No gamepad detected" screen. I'm using a ps3 bluetooth controller, I see this every time I boot, while the controller is connecting to the pi, after which the main emulation station screen usually show up. That didn't hapen today.

I had a look at the emulationstation log file (~/.emulationstation/es_log.txt) and found the same error as you:

lvl1: requested mismatched theme type for [detailed.md_releasedate] - expected "datetime", got "text"

As well as a line confirming that my ps3 controller had in fact successfully connected , which lead me to think that I was stuck on the "No gamepad detected" for some other reason than no gamepad being detected:

lvl2: Added known joystick PLAYSTATION(R)3 Controller (instance ID: 0, device index: 0

I fixed this by running Manage packages > Update all installed packages in the setup script (using SSH), but simply re-installing the carbon theme in /etc/emulationstation/themes/carbon should do the trick.

Hope this helps!

@dankcushions .... That... makes perfect sense :/

Do you know if it's also possible to do for LR-FBA?

I'll dig into the link and have a play - thanks!!!

:)

said in Start Kodi with emulationstation link:

while [ true ]; do

What's the purpose of the "while [ true ]; do" line in emulationstation.sh? Won't this lock up system resources? (Isn't this basically an endless loop?)

@meleu

Even then I fear it resembling an Ingmar Bergman film, with 'PONG' substituting chess.

alt text

Edit: In this scenario, I'm obviously the guy on the left from 'Bill & Ted's Bogus Journey'

@Threepwood

@Zigurana's suggestion looks like a great solution.

Ha! I just noticed your name. "You fight like a Dairy Farmer!"

@ferdnand If you follow the "regular" process of setting up Daphne Loader on a PC/Mac, letting it download the media files, authorizing properly with a valid Dragon's Lair DVD, you should end up with a single video file (lair.m2v), a single audio file (lair.ogg) and a lair.txt that looks like this:

.

151 lair.m2v

This file basically references the video file and the number is the starting frame from the original laserdisc. Daphne knows, based on the frame numbers, where all of the scenes begin and end.

If you have a different set of media files (for example, you ripped mpeg2 video directly from an actual Dragon's Lair Laserdisc from your real Dragon's Lair arcade system), you need figure out the correct starting frame numbers for each of your media files. It can be done. Good luck. Google is your friend, but a good starting place is to learn everything you can about Daphne, laserdiscs and framefiles. Try this for starters.