Closed ner00 closed 2 years ago
This core has not been maintained for years now. It's not even provided in the core downloader.
Use dosbox-pure or dosbox-core, whichever one suits your preferences.
This core has not been maintained for years now. It's not even provided in the core downloader.
Use dosbox-pure or dosbox-core, whichever one suits your preferences.
My mistake, this ticket should have been opened in dosbox-svn instead.
This core has not been maintained for years now. It's not even provided in the core downloader. Use dosbox-pure or dosbox-core, whichever one suits your preferences.
My mistake, this ticket should have been opened in dosbox-svn instead.
dosbox-svn is also not actively maintained anymore :grin: However, it still gets important bugfixes sometimes, so it's not dead. But if you can (meaning if it's available on your platform), use dosbox-core.
I think that me defaulting to SVN stems from some inexplicable past issue where I got lucky with SVN where I was having trouble with core. I'll look into migrating to core and see how that goes. Thanks!
This might be expected to some extent, and in quite a few occasions, especially with 3D games that run higher resolution (640x480). I usually have to use insane cycle numbers, like 100000 cycles and multiplier 9, to be on par with the same performance of standalone DOSBox with only 3000 cycles.
So far I've gotten away with a decently playable games, that is until Tomb Raider at 640x480. No matter how much I tweak the cycles and multipliers I get substantial screen tearing even though the game is seemingly running smoothly otherwise.
This has been nagging me for a while but I never bothered much since I could adjust fine tune the gameplay to an acceptable state, which unfortunately is not the case with Tomb Raider.
Is there any workaround to have the core work more efficiently?