But we shouldn't have to. More so for ND as they seemed to be so caring about things (as they have also re-released Titanic and Forsaken, along with Turok 1& 2.

I'm sorry for ranting but I just wish GOG would step up and say you need to provide our users with the same level of support that you give Steam. But with Blood ND are not doing that at all. I think that annoys me more than the glitch fest of their Blood.

I've given up on gog stepping up for anything myself. I mean, community members are having to post game update changelogs in a forum thread because gog does such a poor job of letting you know games have updated, and having to go remind devs and publishers to update the gog versions. That shoudn't be the customer's job at all as it turns buying here into a chore.

Edit: I'll leave it at that to avoid a thread hijack.

hi i don't know if this is the blog to help the devs fix bugs, but i was on the second level of episode 2 and the aeresol can weapon behaved oddly it would no longer fir in a straight line making me have to compensate by aiming to the left. the bug resolved itself on the next level, it was just so peculiar. thanks to the dev team for being dedicated to fixing this classic!

Blood: Fresh Supply just updated to 1.8.8-5. Seems NightDive is trying their damndest to fix this fast. Going into the game now to see if the window breaking bug is fixed.

I tested out the 1.8.8-5 patch. The good news is that the bug preventing windows being broken by pitchforks and guns is fixed. The bad news is that vsync no longer works properly.

When I started the game vsync was on, but the frame rate was stuck at 30 fps instead of 60 fps. I tried turning off vsync to test, but it didn't fix the frame rate. So next I restarted the game, but when I did that, I was no longer able to turn vsync back on. I tried using both the mouse and keyboard to try turning the option back on, but it refuses to turn back on. It's stuck at off.

Nevermind, I edited the config file to turn vsync back on and fixed this.

Last version 1.8.8-5 still broken graphics on Intel HD 4000
Windows 10 1903, Driver version 10.18.10.5059

There was a bug with that?...it was good on my end

just checked it out myself, The save slot thing still needs to be fixed but that's more of a minor thing.

Cryptic Passage, map 2, textures still messed up. Road is flashy moving wierdness, theater signs aren't what they should be.

While you're at it, make CP a separate chapter that you can play through, not just 'select-a-map'

A few more from my office retro gaming machine (ATI Radeon HD 6450, Quad-core 3ghz, Win7) on version 1.8.8.3 (latest offline installer as of writing this) :

- DirectX 11 doesn't respect the "Keep aspect ratio" of ATI Catalyst. If you select a 4:3 resolution like 1024x768 or 1280x1024 the game still fills the screen on a desktop resolution of 1650x1050 where Nblood will have proper black borders on the sides. Also, once you load a game, the menu will display, but you can't interact with it. It does nothing. It goes to limbo and never comes back until I kill it with task manager.

- OpenGL is just completely borked. If I select that, the blood at the top disappears and most of the graphical components aren't there with the exception of the menu text. Oh! And you can't actually interact with said menu. It's there visually but you can't do a thing with it. And... even the Quickload does nothing. Awesome.

I'm going back to Nblood until this has had a further updates. It's a shame. Despite what Civvie says, it's STILL not ready.

I'll post screenshots/logs when I get a chance.

In Overlook Mansion, cultists disappear inside the walls and then reappear randomly.

Version 1.8.8-5

- 1.8.8.5 now breaks the menu on my Macbook with a Nvidia Geforce GT 750M (Win7) as the previous version did on my desktop with the ATI HD 6450 (above). Once I bring up the menu, the game is essentially frozen and I have to kill it with task manager. What the hell is with the menu code?!?

I don't know how in the hell it managed to do this, but now ALL versions freeze at the menu after loading a save game. I did the following :
- Uninstalled 1.8.8.5
- Reinstalled 1.8.8.3
- Tested. Menu locks up. Killed in task manager. Restarted. Started new game. Saved a test save. Loaded test save. Confirmed lockup.
- Uninstalled again. Did clean install.
- Tested again. Menu locks up. Killed in task manager. Restarted. Started new game. Saved a test save. Loaded test save. Confirmed lockup.
- Deleted the previous configuration DIR. Let it recreate it.
- Tested yet again. Menu locks up. Killed in task manager. Restarted. Started new game. Saved a test save. Loaded test save. Confirmed lockup.
- Uninstalled again. Did clean install with 1.8.8.5.
- Tested. Menu locks up. Killed in task manager. Restarted. Started new game. Saved a test save. Loaded test save. Confirmed lockup.

This is writing configuration info somewhere other than its main DIR under %APPDATA% where it corrupts installs after the fact. 1.8.8.3 had a lot of issues but it at least was playable. Now it's completely screwed up to the point where somehow it retroactively made a previously working version no longer work. This is ridiculous.

Edit : Figured out the issue : Saves are highly tied to the version of the application. Previous saves loaded throw the menu into an unstable state such that the menu no longer works, even if developer mode is turned on in the console. IE - Perhaps in previous versions you could load old saves in developer mode and resave, but this seems broken between the last 2 releases.

Edit 2 : NOPE. Problem persists. Started a new game. Deleted all previous saves. If I save to the 8th save slot (save_07.sav), and ever load that save, the menu becomes inaccessible. It's flaky. Confirmed any save slot beyond the 7th has the same problem.

Games need more actual QA before they go out the door. Back when I was programming this sort of thing would get you in fairly serious "may lose my job" trouble. It's egregious that players are treated as veritable beta testers in this day and age.

Use the Manage Addons menu in the options, then you can activate Cryptic Passage as a campaign. It might fix the textures too if it has it's own resources.

Figured out the story with the menu not being accessible with the mouse after loading :
For whatever reason, the mouse is the issue. If you use the arrow keys, you can press down and it will be able to access any entry, including loading. This reenables the mouse being usable also.

The initial position is set off the screen (probably entry 0 or -1 in the menu list), making it look like it's frozen. The mouse cursor never appears or is left in the state that it's in when you're in-game. So, you literally have no way of accessing the menu with the mouse from that point if you don't press down on the keyboard.

Obviously this is a bug. I've seen a number of other people cite this same issue with the menu being inaccessible, so it's not just me.

Some more bugs with v 1.8.8-5

Tesla Cannon shots from Zealot/Elite Cultists (Blue Robes) ignore and do not damage player armor of any kind.

Bloated Butcher AI sometimes won't use its projectiles.