-
Content Count
363 -
Joined
-
Last visited
Content Type
Profiles
Forums
Calendar
Downloads
Store
Tutorials
Member Map
Everything posted by Sting
-
Issues with Hyperspin booting into Retroarch instead of the game
Sting replied to herosdroid's topic in HyperSpin Android
Further to this, you need to launch a game through Hyperspin from a system that doesn't need a BIOS file. And then once launched through Hyperspin, go to the settings menu and point it to your BIOS folder -
Bezel/overlays are available to use on any core in RetroArch
-
Here's the complete path, it could be on your internal or external drive, I'm not sure how to change the directory settings, so you may have to check both (Android/media/com.nvidia.nvgamecast/Game Recordings/)
-
It's an emulator update that's broke it :/
-
Don't think the developer is going to help :/ "Sorry, but this is very problematic. In current state of project (license check & load process) I can't to do this easy. And I have more priority things for develop at this time"
-
I've just had a quick go, and all I'm getting is a black screen :/ Gonna have another go later, but I've also just emailed the developer
-
Leave it with me, I'll have a look this weekend
-
Try this exe=ru.vastness.altmer.real3doplayer/ru.vastness.altmer.real3doplayer.EmuActivity
-
Hello Loueradun, can you do anything with this??? kickstart_rom_file=/sdcard/Download/Amiga/kick.rom chipmem_size=1 bogomem_size=2 use_gui=no nr_floppies=2 cpu_type=68000 cpu_speed=real cpu_compatible=true ntsc=false chipset=ocs immediate_blits=false gfx_linemode=double gfx_framerate=1 sound_output=normal sound_frequency=44100 sound_channels=mixed sound_interpol=none show_leds=true floppy_speed=100 gfx_center_vertical=smart gfx_center_horizontal=smart gfx_color_mode=16 floppy0=/sdcard/Download/Amiga/Rick Dangerous.adf It's a (.cfg) to directly start Amiga games with the UAE core in RetroArch, can't get it to work though. All I get is a black screen :/ sample cfg.zip
-
No worries, really need to put path in a thread
-
Just checked mine, and there in (.cdi) I must of run into the same problem when I set it up, and stuck to (.cdi)
-
Does your Dreamcast wheel go from (AtoZ) of the game names??? And as Badhemi says "you can't use subfolders in android". Everything must be unpacked in your ROMs folder.
-
Would love to know if anyone gets this working on Android
-
Have you checked your database??? Here's what Reicast says about (.cdi) files on the playstore.
-
Mines set up like the Donkey Kong tutorial, but I'm sure you can use them per game with the Vectrex core
-
Don't think it'll be a (.ini) issue, might be a database issue if it's not showing up in your wheel. Run your database through this website: (http://www.xmlvalidation.com) just to check for errors. Also (.cdi) aren't recommended with Reicast, I think there's compatibility issues.
-
Here, rename them to match your ROMs (.art and .png files) vectrex_overlays.zip
-
Looks great mate I'd try using a usb keyboard with a otg cable, if you're using it with a tablet.
-
Yeah your right, the parameters are for launching a process within the app, so you'll need to email the developers for this information
-
That's what I thought you meant, didn't know you were trying to launch it from the system wheel
-
It was taking forever to upload to here, so uploaded to Mega. I know some systems are a nightmare to get running, but this is definitely not one of them, because most of the settings are blank https://mega.nz/#!QUIG0IrS!eS6feA8t_akXlNXll0WN1xe4a_NR6h2NEAqYJje83ts
-
Just did a quick video to show you it working and my settings, it must be something really simple. The Android wheel is one of the easiest to setup because it does everything it's self. I've not got a Kodi wheel or system theme setup, so just tagged it to the end of my Android database (.XML).