[shmoopty]

I noticed the same issue after moving from RetroPie 3.5 on a RP2 to RetroPie 3.6 on a RP3.

On the initial controller configuration screen, some buttons were completely ignored, while others weren’t. I mashed the controller buttons and couldn’t see a pattern as to which buttons were getting ignored.

This may need some attention.

[shmoopty]

I wonder if your SD card is the cause. Do you know what class the card is?

A Raspberry Pi 2 should run these games smoothly, at least with a class 10 card. I haven’t tried slower cards.

[shmoopty]

Just put the file there and start RetroPie up again.

[shmoopty]

Quick answer – You can use your controller. [See this post, linked from the top of the thread]

[shmoopty]

[quote=118850]im running retropie on my rpi3.[/quote]

(thumbs up)

[shmoopty]

I’m somewhat concerned that no one has claimed success in running RetroPie yet.

Perhaps a software bug. Perhaps a first-run manufacturing defect. Or perhaps simply no one has taken the opportunity to report their success.

I suspect I’ll get mine in the next day or so. I will report on the results.

[shmoopty]

It sounds like a great excuse to make a new project from last month’s Pi.

Perhaps you know of a car that needs a touchscreen Kodi console? That bathroom mirror could become one of those smart mirrors.

If you have a Pi 2 now, the 3 will fit in the same cases.

[shmoopty]

I have tried the “-bank” and “-fastboot” options, with success.

Although “-fastboot” only works on select ROMs. “lair”, for example, works with it. But I don’t think “dle21” does.

[shmoopty]

The video should look the same. If you have fuzzy video, you probably have fuzzy video files. Copy the video file to your computer and open it to check. :)

This build works on the new Raspbian Jessie, as well as future platforms since the build steps are no longer a mystery.

You can map both keys and joystick buttons as well, when you install the controller mapping file in [this post]. That file is still waiting in queue to get testing attention before it’s installed automatically with daphne. By default, the button that you have chosen for “select” will exit.

[shmoopty]

Agree that another shutdown option would just be option bloat. RetroPie has an unusually clean interface and that’s just beautiful.

I haven’t pulled down the SQLite branch yet, so I don’t yet know if that branch imitates the main branch in saving ALL metadata when it quits, or whether it just saves changed metadata as it changes. If it’s the later (now or in the future) I suspect that quitting would be very fast.

[shmoopty]

Keep me in mind if you need to throw bodies at it.

– Shmoopty

[shmoopty]

herbfargus, is there policy posted anywhere regarding pull requests to RetroPie’s fork of EmulationStation?

I appear to be a ROM hoarder too, but I’m not above taking a crack at improving that quitting time.

Related – I know that XML is popular here, but a single SQLite file could be written to as these changes happen rather instantly. Has that idea been raised/dismissed yet?

[shmoopty]

The successful builds have also been on a Raspberry Pi 2. The mystery is what makes your Pi different. Compiling software can be a very intensive process, so if you have a Pi that almost always works, compiling would easily be one of those rare times it fails.

If you share some more info, you may be able to solve this and help others in the process.

Do you have the newest firmware? ( <– click) In RetroPie, F4 will drop you to a prompt. Try installing daphne again after this.

What is the AMPerage output of your power supply? The very tiny print on the power brick will always include the text “Output: x.xA”, where “x.x” is frequently “2.1” or “1.5” or “0.7”… what does yours say?

What is the temperature of your CPU? Typing retropie_welcome at a prompt will show you the temperature while it’s resting. If you SSH into your RPi, you can check it again while it’s building. I’m wondering if your Pi is getting too hot or is in a case that doesn’t ventilate well.

Is it possible that during a late night, you overclocked it and forgot that you did that? You should check.

Good luck!

[shmoopty]

gcc/g++ “internal compiler error” is almost always an indicator of unhealthy hardware. In my experience.

Are you overclocking your Raspberry Pi?

[shmoopty]

[quote=117765]I get an error when I try to install daphne from the experimental menu. It’s says could not install daphne.bin not found.[/quote]

Your specific problem was mentioned earlier in the output. You may have overlooked it. That message just indicates that it was unable to finish.

If you copy the complete output somewhere, such as pastebin.com, I’ll help take a look at it.

[shmoopty]

[quote=117692]Easy to set up (need to rebind the controls but hey that is for another day).[/quote]

I’ve added controller rebinding details to my summary post. I’ll update it when appropriate.

https://www.petrockblock.com/forums/topic/dragons-lair-space-ace-etc-anyone-interested-in-daphne-laserdisc-system/page/2/#post-117516

[quote=117692](video skips scene etc and no prompts for actions)[/quote]

That could mean a lot of different things. Are you talking about the skipped drawbridge scene in DL1? Are you talking about the text hints given on the “easy” setting of DL2?

[shmoopty]

Are you referring specifically to Dragon’s Lair?

As I understand it, the arcade ROM intentionally ended scenes too soon to account for laserdisc seek latency. The dle11 and dle21 ROMs fix this scene cropping, but as a result makes it less like the arcade experience.

How are you adding the latency parameter?

[shmoopty]

cfx69, since you’re testing the more obscure titles I’ve put together a compatibility list to make it easier to share notes with everyone.

https://docs.google.com/spreadsheets/d/1Hy2VpPXgs4a9imeu0_w3SpehKEkhUNOLzD1jhcgwS3o/edit?usp=sharing

Also, if there’s an outstanding issue that can be fixed this may help zero down on the issue.

[shmoopty]

Daphne is now live in RetroPie’s “expermental” menu:.

Here’s a rundown for visitors that don’t want to sift through 60+ comments.

It’s available now. From “retropie-setup”, choose “Update RetroPie-Setup script”. Then “daphne” will be available under “Experimental packages”.

Here’s the wiki:
https://github.com/retropie/retropie-setup/wiki/Daphne

Supported themes currently include carbon, simple, simple-dark, clean-canela, and clean-canela-dark. If you’re currently using one of those, be sure to update it! More themes to come.

Supported gametypes are listed here. Some of the more obscure ones are a real trip! Please share your discoveries!
https://docs.google.com/spreadsheets/d/1Hy2VpPXgs4a9imeu0_w3SpehKEkhUNOLzD1jhcgwS3o/edit?usp=sharing

Controller mapping will be automatic soon, but meanwhile you can manually add the not-yet-official auto-mapping module (click!) /opt/retropie/supplementary/emulationstation/scripts/configscripts/daphne.sh
or you can just manually edit the file /opt/retropie/configs/daphne/dapinput.ini.
It works well on Raspberry Pi 2. Currently too slow on Raspberry Pi 1.

[shmoopty]

[quote=117216]If it was done as a input configuration script as we do for retroarch etc that would help – see https://github.com/RetroPie/RetroPie-Setup/tree/master/scriptmodules/supplementary/emulationstation [/quote]

Hi again, buzz.

Bash scripting is not my proudest skill, but I did a few dry runs with this controller config and it seemed to do the job right. Since daphne has no in-game interface for controllers, it also allows for input tweaking for those who might be inclined.

daphne.sh (pastebin)

The “onstart” function will create three self-documented files in $configdir/daphne/ if and only if they don’t already exist.

dapinput.ini will store default input configuration.

dapinput-forcekey.ini will store entirely optional keyboard mappings that won’t be overwritten by future input configs.

dapinput-forcejoy.ini will store entirely optional joystick mappings that won’t be overwritten by future input configs.

The “map” function will map the joystick buttons unless those controls have been manually added to the “forcejoy” file. End result – controls work normally the first run and you can still tweak them later.

I’ve seen retropie emulators map either “insert coin” or “exit” to the select button. Since Daphne uses both and can’t map button combos, I’ve somewhat arbitrarily mapped select to “exit”; A B X to the three gameplay buttons; and Y to “insert coin”. If something makes more sense to you, your call.

Cheers,

– Shmoopty

[shmoopty]

That’s great news! It’s a relief to see it working for others – that means no detail was overlooked.

I still promised to write a script so that your emulationstation controller assignments just magically carry over to daphne. I’ll have time soon for that. In the meantime, you can edit /opt/retropie/configs/daphne/dapinput.ini … I left some notes in that file.

[shmoopty]

Yes, this should be accounted for if I did everything right!

The directory “roms/daphne/lair_f.daphne” would appear as a emulationstation entry and would have a framefile “lair_f.txt” that’s either a copy or a symlink to your Dragon’s Lair frame file.

The separate directory “roms/daphne/dle21.daphne” would appear as a different emulationstation entry. It would have a framefile “dle21.txt” that’s either a copy or a symlink to your Dragon’s Lair frame file, and a text file “dle21.commands” that contains the text -bank 0 11011000 -bank 1 01110111.

[shmoopty]

[quote=117295]You know, I didn’t even think about that. I’ve got licenses for all my old Pi’s from back when they were used as XBMC boxes. I’ll have to dig thru some old emails and pull the keys and see if it makes a difference.[/quote]

For what it’s worth, I did not have to purchase an mpeg license to get good performance. I didn’t even know such a process existed.

I think your first two suspicions are sound. It’s the speed of the SD card or the Speed of the Model 1 hardware, I’d bet.

Do you know if your SD card is class 10 or 6 or less?

I wonder what you’d see if you replaced that m2v with a heavily downsampled version of the same video.

If it turns out to be the hardware, herbfargus’ early link in this thread may be the answer: https://www.raspberrypi.org/forums/viewtopic.php?f=33&t=57721 but that would require code rewrites.

[shmoopty]

[quote=117270]Where is the command line text so I can add my switches, and -nocrccheck, -no[whatever], etc.?[/quote]

I noticed that the extra command-line options in the official experimental installer aren’t implemented correctly yet, so stay tuned! But to answer your question, for a particular engine like your desired “dle21”, you’ll want to put any extra command-line options that you want in a text file at “roms/daphne/dle21.daphne/dle21.commands”

If you want to manually fix it now, edit “/opt/retropie/emulators/daphne/daphne.sh” and at the end of the last line (after “-fullscreen”) add ” $params” without the quotes.

Or wait until someone here says it’s fixed and install daphne again.

I can confirm that I’ve run it with your settings, so GOOD LUCK and let me know if you’re still stuck.

[shmoopty]

[quote=117262]I’m working on documentation right now:

https://github.com/RetroPie/RetroPie-Setup/wiki/Daphne

I haven’t tested dragons lair but I did get astron working. I don’t know how well it will work on a pi 1
[/quote]

Looks great so far. I’m now a respected ASCII artist! :)

I’ve tasked myself with getting a script to make the joystick controls match what emulationstation thinks is right.

I have now run Dragon’s Lair with success via the official setup script.

[shmoopty]

How did it look on the Pi B?

I just finished testing out the install produced by the official experimental emulators script. It seems to be playing everything I have. There’s one typo that I need to patch – the controls config file is ending up in the wrong location.

Move the file “/opt/retropie/configs/dapinput.ini” to “/opt/retropie/configs/daphne/dapinput.ini” — then it will affect the controls.

Edit that file to map your controller buttons. You’ll see my notes at the top of that file.

With luck, soon, I’ll get that config file to auto-update so it matches everyone’s emulationstation config.

[shmoopty]

I’m probably not the only other person interested in hearing how a Model B holds up. Thanks for taking the plunge!

What is the framefile named? If it’s in the directory “lair.daphne”, the launch script will assume that the framefile is named “lair.txt”. Same base name as the folder.

Let me know if that was the problem.

– Shmoopty

[shmoopty]

Ha – no, I overlooked that. Thanks for the direction.

[shmoopty]

Cool. I’ll do a pull request with the controller setup when I have the time to do it up properly.

The “.daphne” naming convention is a little strange, but it’s a side-effect of daphne wanting to have a monolithic “home directory”, where roms, log files, config files, and other things go. A frame file (“.txt”) might be more intuitive at representing a game, but daphne also dumps “.txt” files of its own at that location.

Buzz, what is your take on discrete and non-breaking code changes to the repository? Some changes I’ve considered are:

– I would like to fix all joysticks going dead if joystick 0 disconnects. Detecting and reinitializing a replugged joystick would better match the rest of the RetroPie ecosystem. (This is an issue when bluetooth controllers go to sleep)

– Optional command-line parameters to break up the monolithic home directory so logs can go one place, while config files go a different place, etc. (Again, better matching the rest of RetroPie)

– My 10 button limit fix isn’t currently in your repo…

If pull requests like these would be considered, I’d start sending them over. But if the goal is to keep the codebase as-is, I won’t spin my wheels.

Cheers

[shmoopty]

That looks pretty clear. I’ll whip one up…

[shmoopty]

On a related note, buzz, if I could ask for your opinion –

I was on the edge of having the daphne launch script look at ~/.emulationstation/es_input.cfg and, if a controller entry matches what’s currently detected as “joystick 0” it would duplicate the button mapping for daphne.

Does that strike you as something that would be valuable for Retropie?

[shmoopty]

Hi, buzz. I’m glad I could contribute!

If this helps – those hard-coded optimizations were in the raspberry pi makefiles to match the style of the other makefiles that were already present. I never tried building without specifying march, mcpu, etc.

If I discovered that those flags were unnecessary and removed them from the repo, would that help you?

[shmoopty]

I haven’t tried Saturn specifically, but on Raspberry Pis that exist now, you should not have high expectations for emulation of 3D game systems. 3D hardware on game systems have historically been diverse and very specialized.

One notable exception is the original Playstation, which had 3D games despite having hardware that more resembled a 2D system.

[shmoopty]

[quote=117103]I pinged Rookervik and he’ll be updating his themes as well to add Daphne.[/quote]

Sweet! This is coming together much faster than I had imagined.

I may beat Dragon’s Lair yet. Gonna try again now.

[shmoopty]

What difficulty setting are your dip switches set to? I suppose I could look that up, but I’m all over the place right now.

Anyway, YES – I can confirm that I was able to run the game with your settings. I’m eager for feedback – currently the file system arrangement tells Retropie how to treat your laserdisc games.

Here’s what your game setup looked like, file-wise

roms
|-- daphne
|    |   (The folder below holds a laserdisc...".daphne"
|    |   tells emulationstation to add this to the menu,
|    |   and "dle21" tells daphne to use that game engine)
|    |
|    |-- dle21.daphne     
|    |    |-- dle21.command  (Optional extra command-
|    |    |                   line params!)
|    |    |-- dle21.txt      (Framefile must have same
|    |    |                   basename, like "dle21")
|    |    |-- lair.m2v
|    |    |-- lair.ogg
|    |
|    |                (All roms go into this roms folder)
|    +-- roms
|         +-- dle21

If you or anyone wants to be running Daphne in 15 minutes, here are the directions.

Keep in mind that you do this at your own risk, of course. And herbfargus might have some interesting insight when he’s back from holiday. But if you’re willing to stick your neck out and try something new, I appreciate any feedback you can offer.

Get a prompt up and enter these four lines.

$ git clone https://github.com/Shmoopty/daphne-pi.git
$ cd daphne-pi
$ ./build-daphne.sh
$ sudo ./install-daphne.sh

Then restart RetroPie.

That last line will clobber any changes you’ve made to es_systems.cfg, if you’ve made changes to it. Because I’m not editing your XML in my bash script. :)

More details will appear in a README in the new roms/daphne dir.

Also, if you install either clean_canela theme from retropie-setup, InsecureSpike has already made the Daphne menu look all pretty!

Tell me what you think! I’m curious how earlier model Pi’s do. I also feel like I’m close to getting daphne to match your preferred joystick config from emulationstation, but I’ll save that for after the feedback…

[Author]

Posts