[Al ex]

Glad you got it working. ?
Absolute mouse emulation is a bit of a pain in the ass. Obviously, there were no touch screens back in the early days, so there are lots of compatibility issues. Programmers did a lot of weird stuff to mouse implementation in particular (just try to make absolute mouse work in Lemmings…), and it’s impossible to have a perfect solution for this.
You can adjust mouse settings in advanced settings, there are lots of tweaking options. In some cases though, you’ll want to stick with relative mouse. This is a 1:1 mouse emulation and will always work.

[Al ex]

Any kind of error message? Maybe you have to reconfigure sound settings?

[Al ex]

Elite First Encounters runs without any issues in Magic Dosbox. What exactly isn’t working for you?

[Al ex]

You can do that with the Dradly Strike widget. Configure it to launch at start, then enter the required key press sequence, and add some delay between each key press (the “Rest” function in the Dwadly Srrike actions).

[Al ex]

It works just fine with absolute mouse. If you’re using relative mouse, set gestures = long press, and map it to left button.

[Al ex]

Thanks, I’ve added the game to the list, along with your tweak. ?

[Al ex]

Lol, yeah. My phone’s a mess, too, all rooted and automated, but at least I configured it myself, instead of having it all superimposed on me by Google and Samsung. ?
That second score of yours looks fine, I’ve updated the list. ?

[Al ex]

I wonder if this is caused by an Android OS setting? IF it also happens in Chrome, at least it’s not a Magic Dosbox specific bug. Maybe there’s some way to bypass this, though. Can you reproduce this behaviour in games and/or apps other than a web browser?

[Al ex]

I’ve added your value to the list. Btw, which chipset (Exynos or Snapdragon) and OS version are you running on?

Screen recording will do no good, it only hampers performance. And after a couple of benchmark runs, performance will go down due to thermal throttling, that’s expected, and nothing to worry about.

[Al ex]

730 realtics. 🙂
2134 gametics is the amount of game time the demo is running, realtics says how fast it actually ran on your device.

[Al ex]

You’re welcome, hope it’ll work fine from now on. Win9x in Dosbox is a buggy mess, it’s still highly experimental, even after all these years of unofficial support.
Come to think of it though, it was also highly experimental on real PCs back then. ?

[Al ex]

Maybe try cputype=pentium_slow?

[Al ex]

My two cents: wav, mp3, flac, ogg, maybe m4a.

[Al ex]

I can do some more testing, still got my S7 edge here. @zebumper is yours an Exynos or a Snapdragon phone?

[Al ex]

So, I ran the benchmark three times for both configs (Pixel Trap ON & OFF):
Pixel Trap enabled = 13.5 fps / 11.7 fps / 11.1 fps
Pixel Trap disabled = 13.6 fps / 12.7 fps / 9.9 fps

Interestingly, while the best result for both was basically identical, I got the worst result by far running the timedemo without pixel traps. But that was the last benchmark run I did, so all the lower values are obviously just a result of cpu heating. I kept running those benchmarks in rapid succession, and that really squeezed the crap out of my phone. ?

If you want to do some more in-depth benchmarking, you can also try the DOS benchmark suite from Phil’s Computer Lab: https://www.philscomputerlab.com/dos-benchmark-pack.html

[Author]

Posts