I think you resolved the issue fairly well for now. I have now found slowdowns, too, at 1024x768; it seems consistent with your results on the faster machine. I haven't yet been able to reproduce some of the other issues fully, especially the high range of cycles (20k versus 500k) used throughout …

Oh boy here we go: This happens, only on this section, randomly. http://speedy.sh/4Nh3f/DosBox-2014-03-26-05-14-26-864.avi *These explosions are NOT something I saw for the first time, so I can't say it's them, as they do seem like they are causing real havoc. **Please notice that the game itself …

I'm using a slow core2duo system with a relatively old ATI video card. Told you there is something else besides CPU itself :) since you can run it on that rig - not that it sounds impossible or something. Your test in running a virtual machine is admirable. That should troubleshoot most problems …

http://imgur.com/a/rzHYC 500k cycles... Ran directly with dosbox.conf, not using OUWB launcher. Then I tested it in WinXP SP3 x32 in a virtual machine - same results. DOSBox Daum is the latest from Ykhwong page dated January 27.2014 - normal dosbox.exe, not _x64 version. PS: I started using 5xBR …

DOSBox Daum latest Win7 x64 3.6Ghz i5 8GB Ram with OUWB Launcher (same results if I do everything manually, even without sound) # This is the configuration file for DOSBox SVN-Daum. (Please use the latest version of DOSBox) # Lines starting with a # are comment lines and are ignored by DOSBox. # …

It seems that you do not enjoy troubleshooting problems since I offered openglnb and openglhq methods, too, but you hadn't tried those. The scaling Output type doesn't really concern me on 800x600 and above - all OGLs at that point are indiscernable. The very idea of stretching a low rez into a …

dgVoodoo2 worked nicely for me with unforced res (800x600 ingame) and msaa, even on a low-end video card. Forced res or antialiasing causes messed up rendering because the game renders very thin, 1 pixel Wide vertical triangles (It comes from the raytracer of the Build engine). However there is an …

And I'll give dgVoodoo a try, since Glidos has that logo, and dgVoodoo is still maintained.

After further thought, as I can't test it, I think the 3dfx binary will limit the physical resolution to 800x600, whether in Glide or the internal 3dfx emulation modes. However, there is a 3dfx scaling technique which would scale to your monitor size and may produce good results; documentation here …

http://www.dosbox.com/wiki/GAMES:Blood http://www.dosbox.com/comp_list.php?showID=679&letter=B Those two links provide dosbox configurations for running Blood. For comparison, did you try a plain version of dosbox, 0.74 and SVN, instead of the Daum build? Are you running the 3dfx binary for the …

You haven't configured the cycles setting properly. Also, I verified that the arithmetic result by Hal is correct, and therefore it is not a dosbox bug as asserted again by the OP. I apologize that I thought this is a bug. But I've tried every possible cycles setting, you can see above your post …

That game is available for sale here: http://www.gog.com/game/one_unit_whole_blood. It provides support for non-technical users and those unable to configure dosbox. Also, it is not a dosbox bug that higher resolutions use an ever growing number of pixels, it can be solved with arithmetic as Hal …

800x600=480000 1280x1024=1310720 2,7 times as many pixels that need to be calculated and shown. Here's the deal: I've managed to find out that the game runs around 500k cycles, core and cpu is on Auto. According to Wiki, using too many cycles will result in sound stuttering and game slowdown, which …

Hi, I'm playing One Whole Unit Blood (ye olde Blood 1), and the setup.exe/setmain.exe allows VESA resolutions up to 800x600. And the game plays perfectly on 800x600. Yet, in-game options allow few resolutions above 800x600, with max. being 1280x1024. When playing on 1280x1024, there is a visible FPS …