Forum Replies Created
-
AuthorPosts
-
Al exKeymaster
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.Al exKeymasterMight be an issue with the obnoxious Google file access restrictions. Do you run the game from internal storage or from an SD card?
Al exKeymasterOof, 349 is insane! What’s that, Pentium 400 speed?
Al exKeymasterWell, 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 😉12. July 2023 at 15:09 in reply to: Use 386mb RAM Build for Fallout 2 Restoration Patch WITH controls? #10394Al exKeymasterCan’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.
Al exKeymasterNice 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.Al exKeymasterThat was possible in Samsung’s old game tools, which were great. Then they replaced it with the bs app we’re stuck with now. I think it only adds games that have been installed through Google Play, or the Samsung store. 😐
Al exKeymasterAdded, thanks! 🙏 I took the cpu specs from GSMArena, is that the correct one (Snapdragon 480 5G)?
Al exKeymasterIt’s actually very easy. All you have to do is tap the orange “+” icon on the left of the screen, then “import profile”, and select the .mgc file from wherever you’ve stored it on your phone.
Next, edit the profile so you’re pointing it to the main program and setup .exe files on your phone. Done. 🙂Al exKeymasterNo, you import the file as it is.
Al exKeymasterMh, I just checked my GoG page, and it should indeed by the standard CD-ROM version. Onle WC4 is the DVD version, I think.
Launch problems in any game might be related to storage access restrictions implemented by Google with the Android 12/13 updates, so it might be worth running the initial DOSBox setup again.Before you do so, and start moving/copying game files all over your phone, you might want to check your mountings, though. I have my game stored on an external sd card, and it’s running fine.
The game itself as well as the DATA.DAT (the CD-ROM image file from GoG) is in a subfolder called “/Games/PC” on my external sd, which is labelled “0000-0000”. For reference, these are the contents of my expert settings section:
[dosbox]
machine=svga_s3
memsize=32
vmemsize=4[render]
frameskip=0[cpu]
core=dynamic
cputype=auto
cycles=max 105%[mixer]
blocksize=1024
prebuffer=5
rate=48000[midi]
mpu401=intelligent
mididevice=synth
synth.sample-rate=48000
synth.gain=2
midiconfig=/storage/emulated/0/MagicBox/MidiROM/SGM-V2.01.sf2[speaker]
pcspeaker=false
pcrate=11025
tandy=off
disney=false
[sblaster]
sbtype=sb16
sbmixer=false
oplmode=auto
oplemu=fast
oplrate=22050
[joystick]
joysticktype=none
[dos]
xms=true
ems=false
umb=true
keyboardlayout=auto[autoexec]
@Echo Off
mount c: /storage/0000-0000/Games/PC
imgmount d /storage/0000-0000/Games/PC/WC3/DATA.DAT -t iso
d:
wc3Al exKeymasterIt’s available on Google Play as a separate app. Compatibility and the complete Dosbox code are identical, but you get a lot more config options in the full version.
Al exKeymasterHuh, that’s a weird issue. But glad you could figure it out. 🙂
Al exKeymasterUsually, you’ll set the folder with your DOS games as root folder in Dosbox. In my case it’s this line (from expert settings, but you can also set it up in the GUI):
mount c: /storage/0000-0000/Games/PCWhich means, I have a folder called “Games” on my sd card (/storage/0000-0000), in which I keep several subfolders (C64, Amiga, SNES, PC, etc.). So I mount /Games/PC as drive C in Dosbox. From there, I launch the game like I would do on a real DOS PC:
cd synd
main (<- that's the game exe file, I avoid .bat files whenever I can). No matter where you keep your game, the folder containing your "Synd" folder should be mounted as C:, do not mount "Synd" itself as C drive. I hope this makes sense. 😉Al exKeymasterHi, and welcome! 🍻
I just tried with my own copy of the game, and I can save/load just fine. If you’re running your game from a folder on your SD card (like I do), you’ll probably have to use the “Public storage” option. Google really f***ed up file access in their latest OS versions. 😐
Also, make sure your game files aren’t set to read-only. -
AuthorPosts