It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Hey guys. While I was playing OUW Blood (I'm playing the installed from CD w/ DOSbox 0.74). Sometimes whenever I take damage, pick up ammo, or firing weapons. The numbers in the stats HUD either flash or don't change for awhile. So I used the "-" "=" keys to change the screen size. And the HUD turns itself into a hall of mirrors. Here's the attached pic of what it looks like. Has anyone have this problem? Do I have to change the settings in DOSbox to fix this problem?

Here's my laptop specs:

Pavilion dv7-3160us Entertainment Notebook
Windows 7 Pro 32-bit
4 GB RAM
AMD Turion II Ultra Dual-Core Moble M620 2.50 GHZ
ATI Mobility Radeon HD 4500 series
Attachments:
Post edited November 05, 2010 by DustFalcon1985
This question / problem has been solved by DustyStyximage
In your Blood.cfg file, is your screen mode set to S3 optimized (ScreenMode = 5), if so change it to Vesa 2.0 (ScreenMode = 1). Even tho, DOSBox has a machine=svga_s3, setting, the combined results can be really bad (color pallet distortion mostly).

It wouldn't hurt to try changing the output= setting in the DOSBox conf file. (ddraw, opengl, overlay, etc.)
avatar
DustyStyx: In your Blood.cfg file, is your screen mode set to S3 optimized (ScreenMode = 5), if so change it to Vesa 2.0 (ScreenMode = 1). Even tho, DOSBox has a machine=svga_s3, setting, the combined results can be really bad (color pallet distortion mostly).

It wouldn't hurt to try changing the output= setting in the DOSBox conf file. (ddraw, opengl, overlay, etc.)
I'm looking at the blood.cfg right now. Should I replace the one in a blue circle or the one in a red circle?
Attachments:
bloodcfg.jpg (277 Kb)
avatar
DustFalcon1985: I'm looking at the blood.cfg right now. Should I replace the one in a blue circle or the one in a red circle?
Edit: I didn't see your screen-capture. I see it is already set to Vesa 2.0. Any line that starts with the semi-colon ";" is commented out. So, it is something else. What do you have set in your DOSBox conf file?
Post edited November 09, 2010 by DustyStyx
What resolution are you using? Unfortunately some high resolutions fail. The best resolution (with a 4:3 image size) is 800x600, higher ones have lots of bugs.

Configure resolution using gog file "grafic mode setup" better than during the game.
Post edited November 09, 2010 by tejozaszaszas
avatar
tejozaszaszas: What resolution are you using? Unfortunately some high resolutions fail. The best resolution (with a 4:3 image size) is 800x600, higher ones have lots of bugs.

Configure resolution using gog file "grafic mode setup" instead of during the game.
His blood.cfg file is set at 640x480. But yes, there are some resolution oddities between Blood and DOSBox, so setting it at 800x600 could fix it.
avatar
DustFalcon1985: I'm looking at the blood.cfg right now. Should I replace the one in a blue circle or the one in a red circle?
avatar
DustyStyx: Edit: I didn't see your screen-capture. I see it is already set to Vesa 2.0. Any line that starts with the semi-colon ";" is commented out. So, it is something else. What do you have set in your DOSBox conf file?
Can you specify which settings in the DODbox.conf? Like memsize, output, machine, etc?
avatar
DustFalcon1985: Can you specify which settings in the DODbox.conf? Like memsize, output, machine, etc?
These are the changes I've made to the default DOSBox.conf file.

[sdl]
fullscreen=true
fullresolution=1280x800 (Change this to match your resolution)
windowresolution=original
output=opengl

[dosbox]
machine=svga_s3
memsize=38 (Blood can use up to 36MB of RAM, and DOSBox uses 2)

update:
DustFalcon, rene.redfield recently made a post about changing the machine value in dosbox.conf to use the "machine=vesa_nolfb" setting, to fix the screen flicker people experience when running Blood on hi-resolution. It seems to fix the HUD render issue you were experiencing as well.
Post edited May 19, 2011 by jurijchrul
avatar
DustFalcon1985: Can you specify which settings in the DODbox.conf? Like memsize, output, machine, etc?
avatar
DustyStyx: These are the changes I've made to the default DOSBox.conf file.

[sdl]
fullscreen=true
fullresolution=1280x800 (Change this to match your resolution)
windowresolution=original
output=opengl

[dosbox]
machine=svga_s3
memsize=38 (Blood can use up to 36MB of RAM, and DOSBox uses 2)

update:
DustFalcon, rene.redfield recently made a post about changing the machine value in dosbox.conf to use the "machine=vesa_nolfb" setting, to fix the screen flicker people experience when running Blood on hi-resolution. It seems to fix the HUD render issue you were experiencing as well.
Ok. I've put these settings in now lets see what happens.
What about the CPU setup in the Dosbox.conf DustyStyx?
avatar
DustFalcon1985: What about the CPU setup in the Dosbox.conf DustyStyx?
Try it. I've not had an occasion to play with it much, sorry.

You might try changing your output to overlay, in the DOSBox config file. There have been other who have posted that they have had good results using that setting.
Post edited June 02, 2011 by DustyStyx
I fixed the HUD flickering for now. Now I need to fix the lag spikes in Blood. I made a new topic about it.
This just in. I downloaded Skulldog's Blood DOSBox launcher and now the game works fine now! I give all my thanks to Skulldog.