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

×
Just curious whether anyone else has had a display glitch.
Once I start the game, it periodically will briefly flash an empty window with a border, and black interior. This window fills the screen. It then reverts back to the 'regular' display without any problem.
It occurs fairly frequently - every few seconds.
I"m running
Vista 64
Nvidia 280 with latest drivers
Sound Blaster X-Fi.
Intel i7
It may be something in the driver settings - I'm not certain. I'm also going to check into possibly running it in a window, to see if this helps.
Any other thoughts would be greatly appreciated.
avatar
tnoyce: Just curious whether anyone else has had a display glitch.
Once I start the game, it periodically will briefly flash an empty window with a border, and black interior. This window fills the screen. It then reverts back to the 'regular' display without any problem.
It occurs fairly frequently - every few seconds.
I"m running
Vista 64
Nvidia 280 with latest drivers
Sound Blaster X-Fi.
Intel i7
It may be something in the driver settings - I'm not certain. I'm also going to check into possibly running it in a window, to see if this helps.
Any other thoughts would be greatly appreciated.

Try going into your game's directory (right click the shortcut then click open file location) and opening "AUTOEXEC.CFG" with notepad(make sure you uncheck the "always run as" check there XD) then scroll to the bottom and type in ["Maxfps" "60"] (without [ and ]). I havent purchased any of the monolith games from gog quite yet. But I own the original shogo mad game(cd version) from monolith. It uses the same engine as blood 2 so this cfg file is something I had to modify in order to get a similar bug in shogo to stop on vista. Chances are gog.com has already did this but im not sure. Anyways, good luck and have fun!
Post edited April 29, 2010 by Kil3r
Thanks for the suggestion. That does seem to help. I had to physically disable write priv on the file, otherwise every time I started the game, that entry reverted back to "MaxFps" "0". Not certain why. There doesn't seem to be a way to set this through either the advanced setup launcher, or through the program itself.
avatar
tnoyce: Thanks for the suggestion. That does seem to help. I had to physically disable write priv on the file, otherwise every time I started the game, that entry reverted back to "MaxFps" "0". Not certain why. There doesn't seem to be a way to set this through either the advanced setup launcher, or through the program itself.

Put the line back into the "cfg" in the directories. Go to the advance options from the Launch menu of blood 2. Check "Always specify these command-line parameters" and make sure "Disable DirectX 6 commands" is checked. If these options revert back like before, try running blood 2 in compatibility mode and do it all again. Ive had similar problems before. I hope this helps.
Having the flickering prob too.
I try to add the maxfps 60 line but cpu tells me I need permission from the administrator to edit. I thought I was the administrator! Anyone help? The game isn't crashing now but the flicker is annoying. Thanks.
The MaxFps entry seems to have fixed it. I decided to put it on the command-line, as otherwise I had to write-protect the blood2.cfg file. The game appears to recreate or update it each time it is launched, and it sets the "MaxFPS" entry in the file to zero every time.
avatar
dochuge: Having the flickering prob too.
I try to add the maxfps 60 line but cpu tells me I need permission from the administrator to edit. I thought I was the administrator! Anyone help? The game isn't crashing now but the flicker is annoying. Thanks.

If you are running Vista/Windows 7 and installed it to the Program Files or Program Files (x86) folder, this is normal. Vista & Windows 7 add additional protection to files in these folders
Also, as this file appears to be updated every time the program starts, you may be better off going to the advanced settings in the GOG launcher, and adding a +MaxFPS 60 to the commend- line.
That's what I did, and it's been working fine ever since.
Post edited May 02, 2010 by tnoyce