Computer buses then were slow (ISA, EISA, VL-Bus) so it was more comfortable to do it this way (and such engines/ports easily recognisable: HoM). Things are first drawn into memory buffer and only when completely rendered and polished, then flipped into framebuffer on videocard. virtually any port I've tried)ĭoom engine itself has slight delay. Well, for one, it doesn't feel very smooth (definitely not as smooth as. Try to set up PCem some time and get back to me on that one. There's some weird optimization bug that makes it perform worse on a newer computer? Possible I suppose.Īs far hard to set up, well, sure compared to the pop-in-and-go you get with NES/SNES/Genesis emulators but so were actual DOS machines more involved to set up than those. Again, a 10-year-old computer runs DOSBox just fine 99% of the time. You're running it on some sort of absolute POS of a computer.
In which case that's Doom's fault, not DOSBox's.
#Dosbox dos emulator has stopped working doom full#
You're used to ports with uncapped framerate so vanilla Doom seems choppy even at full performance. The other settings mostly should be fine at default.
For Doom you usually want dynamic core and max cycles in my experience, and maybe setting the sensitivity higher than 100 so you can get decent mouse response without doing the sensitivity hack in Doom's own config. You set it up incorrectly (or whoever packaged things up for some crappy digital re-release did, if you didn't touch the settings - I've seen cases of this, too). It runs just fine on my computers from ~10 years ago, both of them. It always baffles me when people say DOSBox has bad performance.
0 kommentar(er)
