Forum Replies Created
-
Posts
-
As a little heads-up: lDosbox suffers from the exact same issue. So it’s not related to Magic Dosobox in particular, but seems to be a problem with the 64bit (dynrec?) core instead.
Older Dosbox ports, as well as the 32bit build of Magic Dosbox, are working, but there’s a huge issue with that: Google will drop supprt for all 32bit apps in 2021, which means developers won’t be able to upload new 32bit apps, or updates to existing ones. So the move to 64bit is kinda mandatory. ☹️
It’s working in Andosbox. Sluggish as hell, but I was able to load, play, exit the game, and reload.
Yikes! ? It used to work, I know because I’ve played this game quite a lot, and even built a profile for it. But I’ve just tested with my version (CD-ROM, from a games collection box), and I’m getting the same issue now.
There is an “Enable debug” option in Global settings, but I’m not sure if and where debug data is stored. But you can give it a try, and look in the .MagicBox or /Android/data/bruenor.magicbox folders.
Concerning old stuff on modern phones, this one here is also quite neat. ?
Hi, and welcome! ?
Interesting use case you got there. Unfortunately, I can’t answer your question myself, but I’ll pass it on to Tony, the Magic Dosbox dev. Stay tuned!Oh my… I already saw a performance loss in Nougat compared to Marshmallow on my S7 edge back then. Fortunately, my S9 is still on Oreo. I haven’t switched because XPosed Framework hasn’t been released for Pie yet. ?
He’s talking about the game.ins file. GoG have a habit of renaming iso files to something unrecognizable. ?
Dang. Google are notorious for “fixing” things that ain’t broken. The way they’ve been messing up sd card support over and over again, ever since KitKat, is maddening.
Anyway, in this case, it seems they added official support for the Dualshock 4 in Pie, which messed up your bindings. Nevermind that gamepads have already working for many years, let’s fix it anyway! ?You might want to try different connection methods (i.e. bluetooth / usb). At least on Oreo, I get (slightly) different mappings then.
A possible solution would be a remapping tool, if there’s a working one. You can try GameKeyboard+ by Locnet, but you have to buy it, and it’s rather wonky. Another tool I found via Google is this one here. The website is in German, but Google Translate should do the trick. Liek GameKeyboard+, it’s a keyboard app that needs to be activated in the IME settings of the phone.
It’s from 2013 though, so I’m not sure if it will actually work. Also, even though it looks safe, I would advise a virus scan prior to installing this.Alriht, I received an answer. There haven’t been any changes to joystick functionality, so it does at least look like an OS issue. You could of course provide a link to your game profile here, so we can check it for anything unusual.
From my experience, joystick mapping can get screwed up sometimes. My gameped, a GameSir G4s, can be paired in 4 different modes, and each one behaves differently. I also get weird button misconfiguration in SNES9x EX and some other emulators when I connect via bluetooth instead of USB cable. That messes up my L1/R2 and L2/R2 buttons, for example.
