Forum Replies Created
-
Posts
-
800×600 is extremely taxing. Beloko’s ports are interpreters, similar to ScummVM, so there’s no emulation involved.
I’d suggest you use 640×400, and maybe an upscaling filter (normal2x).It should. Rooting or flashing a custom OS is always risky, and potentially buggy, but it’s still Android after all.
It seems like you have no experience with this kind of stuff though (forgive me if I’m wrong), so I strongly advise you to read all you can find about it beforehand. You can easily brick your device with just one false step during the process.
Alright, it’s back. That’s a weird one. ?
It’s as if you had only permission to write posts, but not publish them. And only in this particular, your very own, thread.
You can of course try to create a new one, and copy/paste the html content of your old topics.Yes. ScummVM only used the game data, and runs it independently from the original executable files, so it can easily implement its own mouse controls. Hence it is not an emulator, but an interpreter, and, while great for nostalgia, never 100% like the real thing.
Whereas Dosbox, and every other emulator, offers the full experience, including all flaws and drawbacks that were present in the original OS and games.Moonlight streaming does another thing, and I’m not even sure if it would work out for all DOS games. Because you would still have to deal with the weird input controls those devs of old were doing. So chances are that work put into a similar implementation would be ultimately a waste of time. ¯\_(ツ)_/¯
Unlike Dosbox, ScummVM doesn’t emulate games, but works as an interpreter. The advantage is that it’s not restricted by all the weird stuff DOS programmers did (to mouse implementation, for example ?).
On the other hand, emulators like Dosbox are much closer to the original, and just run games, whereas in ScummVM, the devs need to code support for each game individually.
Now that is weird. Maybe create a new game profile, and paste the settings I posted above? Forum software wouldn’t allow me to post everything, but I didn’t make any changes to the missing [joystick] and [dos] sections, and you’ll need to configure [autoexec] individually anyway.
My settings:
[dosbox]
machine=svga_s3
memsize=32
vmemsize=8[render]
frameskip=0[cpu]
core=dynamic
#valid cputypes (Ykhwong SVN):
# a)auto
# b)386
# c)486
# d)pentium
# e)386_prefetch
# f)pentium_mmx
cputype=auto
cycles=max[mixer]
blocksize=512
prebuffer=0
rate=44100[midi]
mpu401=intelligent
mididevice=mt32
mt32.romdir=/storage/emulated/0/MagicBox/MT32ROM
mt32.thread=off
mt32.analog=0
mt32.reverse.stereo=off
mt32.dac=1
mt32.reverb.mode=auto
mt32.reverb.time=5
mt32.reverb.level=3
mt32.partials=32[speaker]
pcspeaker=false
pcrate=11025
tandy=off
disney=false[sblaster]
sbtype=sb16
sbmixer=true
oplmode=auto
oplemu=fast
oplrate=44100Holy shit, fixed cycles are a nightmare! ?
I do get smooth sound and very good performance with cycles=max, though.That’s indeed odd. Is yours a Snapdragon or Exynos phone?
I’ll transfer my Daggerfall install to the S10 and see what happens.I guess you already tried different tweaks in expert settings? Like, cycles = max 80%, or prebuffer=20, things like that?
Which S10 variant? I might be able to test on an S10e with Exynos chip, and see if I can reproduce the issue.
It does sound like a throttling/downclocking issue. You can try to add Magic Dosbox to the games list in Samsung Game Launcher, and set it to performance mode.
