reznnate

Sorry I've been away. Was hit hard by the pinball bug. I've reposted the alpha daphne core here: https://drive.google.com/open?id=1frcFNWPinSkfyafsBXsnfHd46_kS1yIY The threading behavior is not acceptable for a proper core, but it works okay for now.

Would love the chance to play around with it. Am hoping either UE4arm, Amiberry, or Retroarch PUAE is released with idealized support.

I understand the complications with making Amiga games work smoothly from a front-end like Hyperspin. However, I expected the support of Amiga CD32 would be easy and straightforward since it was a fixed console platform. Does anyone have this wheel and game-platform working properly on Android? When I looked at this previously, I gave up on PUAE and other emulators I expected to work easily. Of course, it could have been user error.

This sounds great! As an ex-Amiga 1000 and 2500 owner, I've wanted a clean emulation setup for ages. As your project progresses, please send progress videos. 🙂

I screwed up and didn't realize the core was still being ported. The current build is broken and sounds like it'll be another month or two. The beta version I posted previously has various problems so I'm actually waiting for the updated version myself. If anyone has root and wants the old, buggy build I offered as an alpha, let me know and I'll send it to you.

Sorry if I jumped the gun and if it's broken. I'll test this afternoon and confirm.

Info on compatibility here https://github.com/libretro/daphne

After a long while and effort, the Daphne emulator is now available for Android and Hyperspin. https://buildbot.libretro.com/nightly/android/latest/armeabi-v7a/ setup and compatibility details here: https://github.com/libretro/daphne

I'm not sure why the PS3 controller does this but I've definitely seen this behavior as well. On Shield, it's been the consistent behavior across Android L->M->N and now Android O. It would be interesting to note if it's different on Windows, Mac, or other Android devices.

DUDE!? What the heck happened? I hope all is well with family, health, etc. I'm disappointed you won't be involved with final, perfect Amiga Hyperspin setup too. I'm sure it will happen eventually, although it will certainly take longer without your support. I hope it's not simply 'trolls' that pissed you off. It's really disheartening to see your unabashed, positive enthusiasm end like this. I'm sad right now. Edit: I see thatman84 mentioned stuff at home. Take care. Once sorted, come back. This system is 30yrs old, we can wait a little longer...

Wanted to clarify that if you don't use a Retroarch nightly, you may see random crashes (particularly on startup) and audio corruption. A bug was fixed in new retroarch builds.

You'll need to copy the /pics and /sound files as well. Don't need /images or /cache or /ram.

If you have questions about the daphne.ini settings file, let me know. It's the same format as other libretro cores though. Otherwise, the hyperspin daphne setups point to roms.zip files as the way to load games. The core assumes files are in the same locations as the pc daphne downloader. Once difference might the framefile.txt files be in a folder named /framefile. I think the daphne downloader puts those files in /vldp folder.

Don't worry about taking it down -- particularly if you find an issue and video is the only good way to show it. I doubt many will 'stumble' upon it. The traffic here is low and so it's a great testing zone, particularly since we're all pretty hard-core too. :-) The core will be public soon enough so it's fine.

I did not develop this. But I know a lot of effort went into it and particularly making it a core that many could enjoy (versus a stand-alone .apk). Once code is open sourced, it will allow others to add features and fix any outstanding bugs. Please post concerns if you find problems that should be fixed immediately. To assist with perceived audio or input lag, I suggest putting your device/TV into a game-mode and avoid things like bluetooth headphones/speakers, etc. In Retroarch, setting audio lag to 32ms on Shield works well. For optimal video latency across cores, I use GL driver and these video options on Shield: Threaded Video - OFF, Vsync - ON, Max swapchain images - 2, Frame Delay - 1ms, Input Poll Type - Early. BTW - The 'seek delay' between video clips is there to emulate the actual laser disc timing. I think he intends a core option that will remove that if you wish.