Forum Replies Created
-
Posts
-
The initial mode should be the one you save the layout with. So all you have to do is set absolute mouse in mouse settings, then save the layout.
Yes, great idea! I dismissed the idea of an invisible overlay UI when I created my Wing Commander profile for this exact reason. I’m so looking forward to this feature…
Oh yes, good addition. General Midi / MT32 has a big impact on emulation speed, about 10-20%.
And make sure to set prebuffer=0 (pre-set in my .mgc file). Doesn’t impair sound emulation, and on my old Snapdragon 805, it gave a nice boost compared to the default prebuffer=15.In some cases, the menus are awfully heavy on the emulation. Warcraft 2 is the best example, it’s a pain in the main menu, but running butter smooth even on weak devices.
Depending on your device, it doesn’t matter much. My S7 Edge (Exynos) can handle all this easily. But on Snapdragon cpu’s in general, or older phones/tablets, performance issues can occur.
I’d suggest you use either cycles=max 105%, or, more elegantly, the auto/limit cycle option:
cycles=auto xxx yyy% limit zzz-
• “xxx” is the minimum value, forced on the cpu if necessary, which can even lead to sound stuttering
• “yyy” is the max % value. 105% is the highest setting, and will tell Dosbox to run at max 105% whenever it can go faster than the initial “xxx” value
• “zzz” is the upper limit. It prevents Dosbox from exceeding a certain amount of cycles. This is useful to prevent speed inconsistency. You can set this to 1000000, but in this case, you might just as well use cycles=max 105%.I just saw that I made a mistake in my .mgc file: it says cycles=auto 30000 105% limit 30000, which is of course rubbish, because it forces Dosbox to run at 30000 fixed cycles.
So I’d suggest something like this: cycles=auto 10000 105% limit 30000
Great!
I was having identical issues in my Win64 Dosbox and Magic Dosbox, so when I had finally managed to setup this thing, I simply copied the game folder + the dosbox.conf settings to my phone + into my expert settings in Magic Dosbox. Adjusted mountings, done.
That’s my standard approach, because it’s much more convenient to fix such things on a big screen, with keyboard and mouse.Ah yes, the z.cfg… try this one, that’s the one I’m playing Daggerfall with.
Contents:
type dfall_huge
path C:\Dagger\arena2\
pathCD C:\Dagger\arena2\
fadecolor 0
mapfile d
rendergame 1
user 1
startMap 179
region 17
helmet 0
maxSpeed 200
#controls viewplyr.dat
controls betaplyr.dat
maps mapsave.sav
CHEATMODE 0
MagicRepair 1OK, question answered. 😉
Can you please post your mountings here?
Or you can try my config here: https://magicbox.imejl.sk/forums/topic/daggerfall-2/
You only have to adjust the autoexec section in expert settings. This config is 100% working with correct mounting commands. I do remember that I was having some general trouble getting this game to run in Dosbox, it’s very picky.Have you requested sd card access in Magic Dosbox Global settings? Google is using some crap file restrictions since Lollipop. Tap “Request permission”, then select your sd card from the Android documents manager.
If you’ve never done so before, you will probably have to tap the dot menu in the top right corner, and select “show sd card” (or something like this).
If you’re rooted, you can take a logcat, e.g. with Catlog (Play Store).
Another thing, and probably not the solution: have you requested sd card access in Global settings?
Strange, it should be working just fine. Try this config, and replace the mounting commands in Expert settings with your own.
No, can’t get it to work, I’ve also tried ctmouse. It does work with relative mouse, but this weird resolution breaks absolute mouse. Damn…
