Forum Replies Created
-
Posts
-
Funny. This looked like a mock-up, and that lead to the latest development, which will allow you to set custom backgrounds for telescope widgets. Pretty neat, if you want e.g. to draw a nice border around an enlarged screen portion. This feature will also be a part of the upcoming v53.
Lol, RetroArch is completely unusable with its broken UI. Hope you get this one running, it’s the best Dosbox app I’ve ever used. And I’ve used about all of them. 😉
OK, the Mediatek variant. Seems recent enough, Cortex-A53 with Mali 720 gpu – nothing exotic, so it might just as well be a software issue. Maybe the crash report will give some insight.
That will be either Andosbox or Dosbox Turbo, I guess? All these ports share a lot of code. Magic Dosbox is by far the most advanced and complex one, but it sounds a bit like it.
That’s one for people with more insight than me. Tony, the dev, is around here often, so have a good night, and stay tuned tomorrow. ?
Hm, that’s weird. Have you tried to restart your phone?
And if you are rooted, could you perhaps provide a logcat?Now I understand the problem. Yes, you can tap the “Mouse navigation” entry in the Deadly Strike action list to change the behaviour.
Mind that in several other Deadly Strike actions, like e.g. Ghostly Presence, a cogwheels icon will appear to the right, which you can also tap for even more settings.
Multiple layers will suffice. If layers can be named like widgets, and changed with a dedicatet widget, it’ll be even better: I could create the necessary layers, label them Hornet/Scimitar/Raptor/Rapier for easy reference, and then switch according to the ship I’m flying atm.
That’s a great list. ?
Played through QfG1 in mDosbox, too. Was the first time I’ve ever played it, btw.
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
