[goodjaerb]

In my case I had to run the command sudo chattr +i emu.cfg to make the file completely unmodifiable. This means either you have to edit it first or if you need to edit it later you’ll have to do sudo chattr -i emu.cfg to allow modifications. I also changed ownership to root and made it all read only permissions to be extra safe.

I didn’t have to use a mapping as reicast chooses one on its own. If I ever set a mapping value reicast would say it couldn’t find it. I just had to make sure the value for evdev_device_id_1 pointed to my joystick.

[goodjaerb]

I can try that tonight. I just wish I knew if it was something wrong with my ubuntu based setup or with emulationstation. I’d say I’m a hobbyist developer but I’m not good enough with github to dig into the source and figure anything out.

I don’t have a pi2 but I have retropie on an old pi, if I can get reicast on there maybe I can see how it behaves, even if it doesn’t run well.

[goodjaerb]

That’s the thing. I try using the evdev_mapping_1 = yaddayaddayadda and I run reicast from /opt/retropie/emulators and in the output it says it can’t find the mapping file. If I only set the evdev_device_id_1 it works. But again that’s outside of emulationstation. If I set up my emu.cfg like yours, run emulationstation and then run dreamcast from within, emulationstation rewrites my emu.cfg and removes any device id or mapping I had in there.

[Author]

Posts