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

×
Hello!
Just bought Blood 2 - The Chosen and it runs but unfortunately the screen flickers constantly which makes it basically unplayable.
I already tried what's mentioned here:
http://www.gog.com/forum/blood_series/blood_2_screen_flicker
Unfortunately it only gets rid of the flickering for a few seconds after launch and then it returns just like without the +MaxFPS 60 commandline. Any ideas?
Post edited April 14, 2014 by Captain_Shiny
avatar
Captain_Shiny: Hello!
Just bought Blood 2 - The Chosen and it runs but unfortunately the screen flickers constantly which makes it basically unplayable.
I already tried what's mentioned here:
http://www.gog.com/forum/blood_series/blood_2_screen_flicker
Unfortunately it only gets rid of the flickering for a few seconds after launch and then it returns just like without the +MaxFPS 60 commandline. Any ideas?
Make your AUTOEXEC.CFG read-only. Also, IIRC I think there is a defaults.cfg file, where you can add it as well.
avatar
Captain_Shiny: Hello!
Just bought Blood 2 - The Chosen and it runs but unfortunately the screen flickers constantly which makes it basically unplayable.
I already tried what's mentioned here:
http://www.gog.com/forum/blood_series/blood_2_screen_flicker
Unfortunately it only gets rid of the flickering for a few seconds after launch and then it returns just like without the +MaxFPS 60 commandline. Any ideas?
avatar
DustyStyx: Make your AUTOEXEC.CFG read-only. Also, IIRC I think there is a defaults.cfg file, where you can add it as well.
I think you missunderstand. I entered the launcher, went for the advanced options, checked the "Disable Directx 6 commands" and "Always specifly these command-line parameters" checkboxes. And then I entered "+MaxFPS 60" (without ") in the command-line textbox. When I do that the flickering doesn't appear right at startup as it does without the commandline but a few seconds later.
But I just tried it over the autoexec.cfg and default.cfg with read-only checked and that just does the same.
Oh, my GPU is an NVidia GTX 760, btw.
Post edited April 14, 2014 by Captain_Shiny
avatar
DustyStyx: Make your AUTOEXEC.CFG read-only. Also, IIRC I think there is a defaults.cfg file, where you can add it as well.
avatar
Captain_Shiny: I think you missunderstand. I entered the launcher, went for the advanced options, checked the "Disable Directx 6 commands" and "Always specifly these command-line parameters" checkboxes. And then I entered "+MaxFPS 60" (without ") in the command-line textbox. When I do that the flickering doesn't appear right at startup as it does without the commandline but a few seconds later.
But I just tried it over the autoexec.cfg and default.cfg with read-only checked and that just does the same.
Oh, my GPU is an NVidia GTX 760
Nope, I didn't, just going from prior experience. Blood II kinda forgets things between level changes, because it overwrites the .cfg files during game-play. Making it read-only should keep it in place. Sorry that didn't work for you. You can always enter it in manually by pressing ~ to bring down the console... it gets annoying quick though.
avatar
Captain_Shiny: I think you missunderstand. I entered the launcher, went for the advanced options, checked the "Disable Directx 6 commands" and "Always specifly these command-line parameters" checkboxes. And then I entered "+MaxFPS 60" (without ") in the command-line textbox. When I do that the flickering doesn't appear right at startup as it does without the commandline but a few seconds later.
But I just tried it over the autoexec.cfg and default.cfg with read-only checked and that just does the same.
Oh, my GPU is an NVidia GTX 760
avatar
DustyStyx: Nope, I didn't, just going from prior experience. Blood II kinda forgets things between level changes, because it overwrites the .cfg files during game-play. Making it read-only should keep it in place. Sorry that didn't work for you. You can always enter it in manually by pressing ~ to bring down the console... it gets annoying quick though.
Oh, I see. Unfortunately I can't find the key to open the console - I have a german keyboard layout.

Edit: Okay, I found the key (what a pain - had to change the Keyboard scheme to US for the key to trigger) and tried it via console and it reduces the flicker but it still happens way too often. Guess I'm out of luck with this one.
Post edited April 14, 2014 by Captain_Shiny
I love Blood 2.
Captain_Shiny, a few other thing you might try:

Aside from the disable DirectX 6 commands, you can also try ticking
• Enable optimized Surfaces
• Enable poly gap fixing (slower)
• Enable triple buffering

In your video card settings:
• Disable v-sync.
Note: The last time I suggested it, it didn't help, but who knows, others seem to have had luck with it.
Post edited April 15, 2014 by DustyStyx
avatar
DustyStyx: Captain_Shiny, a few other thing you might try:

Aside from the disable DirectX 6 commands, you can also try ticking
• Enable optimized Surfaces
• Enable poly gap fixing (slower)
• Enable triple buffering

In your video card settings:
• Disable v-sync.
Note: The last time I suggested it, it didn't help, but who knows, others seem to have had luck with it.
Alright, thanks for your help but unfortunately nothing seems to work (and those game options were already activated by default, btw). Every fix is only temporary for a few seconds and then the flicker sets in again. And by now I tried almost all driver settings and ingame options. With deactivated V-sync, the flickering occures partially between the screen tearing lines, btw.
Post edited April 15, 2014 by Captain_Shiny
avatar
Captain_Shiny: Alright, thanks for your help but unfortunately nothing seems to work (and those game options were already activated by default, btw). Every fix is only temporary for a few seconds and then the flicker sets in again. And by now I tried almost all driver settings and ingame options. With deactivated V-sync, the flickering occures partially between the screen tearing lines, btw.
From bad to worse then, sorry.

I haven't had any problems with the graphics (AMD APU systems with windows 8.1) though I did have a problem with wonky mouse control, where my mouse view was effectively limited to a 30° cone in front of me.

Not sure if you are keen on trying one last thing. There is a graphics wrapper called nGlide, which allows 3DFx rendering on modern systems. Once installed change your 3D Card option to a 3DFX Banshee. It helped a lot with my mouse view, though it is still a little sluggish.

http://www.zeus-software.com/downloads/nglide

Addendum: okay, the glide wrapper thing probably isn't going to change anything. Blood only has a Direct3D and Software rendering options. I think the mouse-look issue I had was fixed with Windows 8.1 update 1. I tried it again on separate computer with a fresh install of windows 8.1u1 and a old Radeon card. All it needed was the DirectPlay add-on and Blood2 was working fine.
Post edited April 15, 2014 by DustyStyx
avatar
Captain_Shiny: Alright, thanks for your help but unfortunately nothing seems to work (and those game options were already activated by default, btw). Every fix is only temporary for a few seconds and then the flicker sets in again. And by now I tried almost all driver settings and ingame options. With deactivated V-sync, the flickering occures partially between the screen tearing lines, btw.
avatar
DustyStyx: From bad to worse then, sorry.

I haven't had any problems with the graphics (AMD APU systems with windows 8.1) though I did have a problem with wonky mouse control, where my mouse view was effectively limited to a 30° cone in front of me.

Not sure if you are keen on trying one last thing. There is a graphics wrapper called nGlide, which allows 3DFx rendering on modern systems. Once installed change your 3D Card option to a 3DFX Banshee. It helped a lot with my mouse view, though it is still a little sluggish.

http://www.zeus-software.com/downloads/nglide

Addendum: okay, the glide wrapper thing probably isn't going to change anything. Blood only has a Direct3D and Software rendering options. I think the mouse-look issue I had was fixed with Windows 8.1 update 1. I tried it again on separate computer with a fresh install of windows 8.1u1 and a old Radeon card. All it needed was the DirectPlay add-on and Blood2 was working fine.
Alright! Figured it out! After reading an unrelated thread somewhere about some game flickering because of speedfan (fan control tool), I tried it without having speedfan run in the background and it works! It runs like a charm and I don't have any stability problems, either.
Btw, support told me that it's not runnable under Windows 7 but I didn't have any further issues, yet - runs great so far.
avatar
Captain_Shiny: Alright! Figured it out! After reading an unrelated thread somewhere about some game flickering because of speedfan (fan control tool), I tried it without having speedfan run in the background and it works! It runs like a charm and I don't have any stability problems, either.
Btw, support told me that it's not runnable under Windows 7 but I didn't have any further issues, yet - runs great so far.
Awesome! Now, how how the devil would a fan control tool make game performance stable?
avatar
Captain_Shiny: Alright! Figured it out! After reading an unrelated thread somewhere about some game flickering because of speedfan (fan control tool), I tried it without having speedfan run in the background and it works! It runs like a charm and I don't have any stability problems, either.
Btw, support told me that it's not runnable under Windows 7 but I didn't have any further issues, yet - runs great so far.
avatar
DustyStyx: Awesome! Now, how how the devil would a fan control tool make game performance stable?
Well, performance was fine. The screen was just flickering like a broken television. I suspect it's because of the autostart symbol in the lower right which shows the current CPU temperature and thus changes all the time - that must have somehow interfered with the game so that the flickering occured. Well, if I exit the tool, it runs fine so it's all good, now.
Post edited May 03, 2014 by Captain_Shiny
Yeah this happens with Origin turned on while u play. That notifier that tells u when somebody logged on or off really messes with the whole screen while playing Blood 2.
Interesting. One more thing to throw into the trouble shooting toolbox. Thanks guys.
The corners of the screen flicker and you can see the window. It didn't do this before...