Hi, is there anyway I can't limit my frame rate in build games to say.. 30?
And raising the resolution just makes the game run slower im the parts which is why I want the games capped to 30.
what exactly is the problem
looks like the game is running slowly in parts and you think capping the framerate will solve it ?
Guardian of the Sacred Five Terabyte's of Gaming Goodness
wrote:what exactly is the problem
looks like the game is running slowly in parts and you think capping the framerate will solve it ?
No, I want to cap the frame rate so the game will be more smooth (Dropping from 100 to 30 FPS for example.)
If you're playing Duke3D or Shadow Warrior, you could try a sourceport. If it's Blood, then you're SOL.
wrote:If you're playing Duke3D or Shadow Warrior, you could try a sourceport. If it's Blood, then you're SOL.
Damn 😢
does dosbox have a vysnc option ?
Guardian of the Sacred Five Terabyte's of Gaming Goodness
DOSBox SVN Daum has a frame rate limiter:
forcerate: Force the VGA framerate to a specific value(ntsc, pal, or specific hz), no matter what
I've checked it in Blood and it works.
11 1 111 11 1 1 1 1 1 11 1 1 111 1 111 1 1 1 1 111
I am running this on real hardware.
what system do you have and why is the game making such massive drops I remember build games being pretty smooth
Guardian of the Sacred Five Terabyte's of Gaming Goodness
wrote:what system do you have and why is the game making such massive drops I remember build games being pretty smooth
It's because of the software renderer btw.
Geforce4 MX 420 with 45.23 drivers
Pentium 4 @ 1.7 Ghz (Upgrading to a 2.8 Ghz soon)
383 MB of Ram (says Windows)
Display running at 1024x768 (Blood is at 640x480)
Soundblaster Live!
"Display running at 1024x768 (Blood is at 640x480)"
Are you not running in proper msdos
I ran blood on a p75 (o/c'd to 90mhz) and it ran fine, I dont see why a cpu slowdown utility wouldn't work for you if i could run it ok on a cpu that was less than 10% the power of yours
try a sourceport
http://sourceforge.net/projects/blood32/
Guardian of the Sacred Five Terabyte's of Gaming Goodness
wrote:"Display running at 1024x768 (Blood is at 640x480)" Are you not running in proper msdos […]
"Display running at 1024x768 (Blood is at 640x480)"
Are you not running in proper msdosI ran blood on a p75 (o/c'd to 90mhz) and it ran fine, I dont see why a cpu slowdown utility wouldn't work for you if i could run it ok on a cpu that was less than 10% the power of yours
try a sourceport
http://sourceforge.net/projects/blood32/
I also tried running in DOS mode, didn't fix it. And Build games don't go slower or bug out at higher clock speeds,
That isn't a source port, that is a recreation.
Also the FPS is jumpy because the CPU can handle some parts well and some not because of the software render.
and if you slow down your cpu the difference will be a lot less
Guardian of the Sacred Five Terabyte's of Gaming Goodness
That's bullcrap. Slower CPUs do not mean more framerate stability for high resolution lookup table overdraw FPS dips.
really he's getting drops of 60fps, if he slows down his cpu so he only gets 30fps do you think he will still get drops of 60fps ?
Guardian of the Sacred Five Terabyte's of Gaming Goodness
Because with a slow CPU, instead he'll drop from 40fps to 5-12fps.
which half the fps drop
Guardian of the Sacred Five Terabyte's of Gaming Goodness
