Forum Replies Created
-
Posts
-
I don’t think it’s an actual crash, it’s simply the [autoexec] section in expert settings pointing to the wrong directory. Adjust the path after “mount c” to where your dos games are stored, and it should work.
You can delete the “exit” command, or comment it out with a #, so Dosbox won’t exit automatically. I just put it there for convenience, so I drop back to the main menu when I quit the game.Any widget should work for any game, only the control scheme won’t make any sense in most cases. 😉
I’ve forwarded your issue, as this sounds like a bug to me. I just re-tested on my device, and the profile is working fine, which shoud rule out a version conflict (the profile is rather old by now).That’s pretty weird. Just to make sure, you have un-checked the “Expert commands” option at the bottom, right? Because otherwise, it will override any other settings you’ve made.
No problem, you certainly aren’t a nuisance. 😉
You don’t have to put the mgc into the game directory. It’s basically just a renamed zip file containing all the necessary files. You simply tap the + icon in Magic Dosbox, navigate to the file, and import it.
Try this profile, I re-exported it for testing without expert settings. It’s working fine on my device: https://1drv.ms/u/s!ArpMRx04ZUDUmdRzXtpJ6Ct3_0rDYgAnd if course, you should be using a legit version of the game, not an abandonware download, as these tend to be broken to some degree. 🙂
I think that in my profile, I’m using expert settings with an “exit” command at the end. So when the profile can’t find the game exe (which it most likely can’t, because my paths are different than yours), it will quit right out of the emulator again. Try unchecking expert settings, and pick your game.exe (or ultima6.exe, if you want to watch the into) from the UI. Hope this helps. 🙂
Could be possible. I’ve tested the game, basic game profile, no expert settings. Just picked the exe file, launched the game, and it worked fine. So it’s definitely doable. 👍
The cycles=max setting in Dosbox can act up in rare cases. If I use it in Screamer 2 for example, I’m forever stuck at the loading screen. It doesn’t seem to pick up speed for reason, and stay at its slowest setting.
So maybe it’ll help if you try a fixed cycle setting, like cycles=5000.
I’ll see if I can get my hands on it for some testing.Hey, no problem. It’s always good if an issue can be sorted out so easily. Broken downloads shouldn’t be a thing we’d have to worry about anymore, it’s not my first bugfixing step either. 🙂
Just did some quick testing, and got it to work. Fine tuning will be a challenge though, for such an ancient game. 😉
Anyway, make sure you enable joystick in the game profile (under “Edit”, where you also select Dosbox core, memory sound etc.). Tap “native 2axis joystick emulation”, then tick both “Enable” and “Timed”. And make sure to run the game at very low cycle settings (around 1000), it will start misbehaving at higher speeds.Might be an issue with the obnoxious Google file access restrictions. Do you run the game from internal storage or from an SD card?
Well, I’m blaming Samsung. They have full control over cpu / gpu governor and clock settings (which they profoundly messed up in the past). It’s just a sleeker, more casual-user-(read: idiot)-friendly UI that prevents any real proper of tweaking. I’m not an “everything was better in the old days” guy, but in the case of Android, it really was. That sweet time period around 2012-2016, when you could root the crap out of devices, and apply automatic cpu core and clock adjustments on a per-app basis, that was great. There was a great tool, can’t remember it’s name, that let you configure all sorts of stuff.
For example, as soon as I launched Magic Dosbox on my Note 4, my tweaks would shut down cores 2&3 completely, downclock core 4 to 800 MHz to handle light background load, and lock the first core to max clocks. The Snapdragon 805 was notorious for overheating and downthrottling, and the Note 4 usually scored around 2000 realtics in the benchmark, before it started to overheat (90+°C), and thermal throttle, rendering the device useless. With my extra tweaks, I could push it to 1370 realtics, with temperatures around 65-70°C, and no thermal throttling at all.
But hey, thank you, Google & Samsung, for taking away all these possibilies for no real reason at all.
/rant off 😉Can’t work, because the free version doesn’t support most of the features of the paid version. So naturally, if you copy a complex layout over to the free version, it’ll crash.
Nice boost to performance, I have to say. Getting 459 instead of 570 on an A52s now. I think I’ll also re-bench my old S9+.
*Edit* yes, S9+ is now around 720 instead of 891.
