Forum Replies Created
-
Posts
-
Not quite, but that doesn’t matter. Change the imgmount line to:
imgmount d /storage/emulated/0/Dkeep1/data/game.gog -t iso -fs isoRight, we’re getting there. The image file must be placed inside your DKeep1 folder, and labelled game.gog. That’s the way the GOG installer copies it during install.
Lol, this is getting more complicated than I’d thought. I hate it when apps try to be clever…?
Ok. Replace the [autoexec] section in your expert settings wih this one:
[autoexec]
@Echo Off
mount c: /storage/emulated/0/Dkeep1
c:
imgmount d /storage/emulated/0/Dkeep1/game.gog -t iso -fs iso
keeperThe file behind my link is a very basic .mgc file that you can import into MagicDosbox (tap the orange + symbol, then “Import profile”.
I’ve set the mountings so they (should) match your game folder.That’s because your mountings aren’t correct. In which folder have you stored the game on your sd card?
For example: on my phone, it’s “DOSGames/DKeeper” on the internal sd card.
Don’t worry, we’ll get this sorted out. ?Ah, sorry for the confusion. I’m using Roland MT32 midi, which requires MT32 ROM files, which I can’t post here for legal reasons.
If your game is set up to use Soundblaster music, you don’t have to change anything, just ignore this. ?OK. So, the GOG version has a litlle quirk. It comes completely preinstalled, and bundled with DOSBox. The problem is, that it’s installed to a virtual C root drive, and has issues with CD detection. It needs a “-t iso -fs iso” extension, and everything must be in the correct folder. DKeeper’s own config.cfg file can be edited, but at least in my case, this messed things up even more.
My workaround is to activate expert settings. Mind that I’ve set an MT32 ROM path and my own path settings under [autoexec], which you’ll need to adjust. Your S6 doesn’t have an external sd, so the basic mounting (storage/emulated/0/) should be correct. Simply copy & paste the following into your expert settings, overwriting everything that’s in there, adjust the mountings, and tick the check box “expert settings”:
[dos]
machine=svga_s3
memsize=64
vmemsize=4[render]
frameskip=1
aspect=false[cpu]
core=dynamic
#valid cputypes (Ykhwong SVN):
# a)auto
# b)386
# c)486
# d)pentium
# e)386_prefetch
cputype=auto
cycles=max[mixer]
androidFasterAudio=true
blocksize=1024
prebuffer=10
rate=44100[midi]
mpu401=intelligent
mididevice=mt32
mt32.romdir=/storage/emulated/0/MagicBox/MT32ROM
mt32.thread=on
mt32.analog=0[speaker]
pcspeaker=true
pcrate=11025
tandy=off
disney=false[sblaster]
sbtype=sb16
sbmixer=true
oplmode=auto
oplemu=fast
oplrate=22050[ipx]
ipx=false[serial]
serial1=disabled
serial2=disabled
serial3=disabled
serial4=disabled[dos]
xms=true
ems=true
umb=true
keyboardlayout=auto[joystick]
joysticktype=none[autoexec]
@Echo Off
mount c: /storage/emulated/0/DOSGames/DKEEPER
c:
imgmount d /storage/emulated/0/DOSGames/DKEEPER/game.gog -t iso -fs iso
keeperCould be bad mountings or an install error. I’m assuming you’re using your own ISO file, created from your own physical copy of the game…? Because downloaded stuff is broken quite often, and causes a whole lot of issues. If you want to make sure: the GOG version of Dungeon Keeper Gold (5.59 €/$) is running fine. I’m running the DOS version, with Alt+R ingame to switch to SVGA resolution.
Are you using expert settings? If so, could you please post the whole contents of your config?
If not, could you upload your Dungeon Keeper .mgc file somewher (Long press game icon -> Export, file is stored in /sdcard/MagicBox/Exports) and post the link here?That’s what I was thinking of. It would be a PITA to create all these widgets, though. But you’re right, I take back the “impossible”, and replace it with “horribly tedious”. Not a fault in mDosbox, but the game’s UI is… challenging. ?
What games in particular are you talking about? Maybe there’s a workaround for your issue. If there aren’t too many buttons, you can e.g. create widgets that are thicker and easier to tap.
Hi Tony,
I think the large dead zone is a good idea, and can solve most of the issue.
For the last bit of accuracy, maybe you can add a tiny (user-adjustable?) input delay: let’s say, I want to move to the top left position. This will take ~50-100 ms, I guess. So, if mDosbox notices beginning analog joystick input, it waits for ~50 ms, to see where the movement ends.
Of course, you could also extend the deadzone further, something like this should also do the trick:
It doesn’t get any more precise when you’re playing with an analog joystick, maybe your first solution in the beta was already what rcoltrane is talking about.
