Reply 100 of 124, by Delphius
Ok thanks for the testing, the default values in speedset are mostly pulled from ‘dosbox performance’ wiki. I would guess 80000 cycles is far too high at that point you might as well be using frameskip. When you add the usb cdrom does mnthelp see a new device?
I don’t think changing video memory setting will do anything other than make less memory available to the system because If I understand it correctly Xvesa really isn’t using any GPU acceleration. It’s probably possible to make some Linux tweaks for this specific hardware, but I’d also like to keep Dosbox Distro as compatible as possible. I think ALaricD is onto something with screen size / scaling since basically the cpu is doing all the work scaling 320x200 up to 1024x768 but at two different points (dosbox normal2x, then xvesa scaling 640x400 to 1024x768).
I haven’t tested hacking to terminal, but I think if you modify one of the script files to just launch terminal it might work. Try mounting a drive to ~/.local/bin/ then I would guess you could modify almost any of the script files to run xterm/aterm. bbs.sh is basically a terminal (just checking if window title is telnet), I would guess you could modify that, the alt-enter to the terminal after it goes back to dosbox. If you end up fighting with the window switching maybe modify something designed to run in background.
I agree that 80000 cycles seems a bit high for this type of thing. Which makes me think something needs to be better optimized. I think in my days of testing dosbox through retropie on my raspberry pi 3, it seemed like 14000-20000 cycles was sort of a sweet spot for most of these games. I think the thin client is capable of performing better than that. You might be on to something with the scaling set to 1024x768 as well. I havnt personally had any issues with running this at 640x480 on modern devices, but usually no lower than that. I think it would also be worth using opengl extensions instead of overlay if it isnt already set as well.
I have been trying to live boot the thin client in to 32-bit lubuntu or linux mint as well, but I havnt had much luck yet.