Has the difficulty increased? I remember playing the original and I don't remember taking 70 damage the second I enter the line of sight of two cultists. Is something up with the enemy activation and hitscan?

Nope Blood has always been ridiculously hard, you must have played on a lower difficulty when you were younger ;)

Damn right it is: the sound on version 789 is broken so long as the cutscenes are on. Nothing I have tried to fix it works and I have found NOTHING ONLINE TO HELP ME FIX THIS GAME BREAKING ISSUE. The only sound fix I found rolls it back to an earlier version without FMVs and less options i.e. it was for a completely different bug in an earlier version of the sourceport.

Interesting, in my case version 0.789 doesn't play any cutscenes at all other than the Monolith intro logo. That's rather curios, as the DOSBox version plays all cutscenes fine, but doesn't play the Monolith logo.

Otherwise I find that by now BloodGDX seems to work almost flawlessly at 1920x1080 and also looks very nice. Mouse control is extremely smooth, something I even forgot I missed after having played the DOSBox version with bmouse for a rather long time. Now after playing BloodGDX, whenever I go back to DOSBox it just feels so sluggish.

I only had one problem on my Windows 10 machine: When using any resolution lower than 1280x1024 the fullscreen window isn't scaled properly, only taking up 2/3 of the screen in the upper left corner. Usually this can easily be fixed by choosing "Disable Display Scaling on High DPI Settings" in the properties of an .exe-file or its shortcut. In the case of BloodGDX it's not that simple as the game runs from a .jar- instead of an .exe-file.
I found a way around, though: You have to create a shortcut to the java.exe file, which you have to find first. In my case it's located at "C:\Program Files (x86)\Java\jre1.8.0_161\bin". Then right-click on the shortcut, select "Properties", and under "Target" add "-jar" and the complete location of the BloodGDX.jar. In my case that looks like this:

"C:\Program Files (x86)\Java\jre1.8.0_161\bin\java.exe" -jar "C:\GOG Games\One Unit Whole Blood\BloodGDX.jar"

Now, finally, in the same properties under "Compatibility" the high dpi scaling can be disabled. Et voilà, running from that shortcut BloodGDX now displays proper fullscreen at all resolutions. One caveat, though: Now BloodGDX creates a new .ini file in "C:\Users\USERNAME\M210Projects\BloodGDX" instead of the original Blood folder, which is also where the savegames need to be located. I haven't found a way to change this, as it still works like that even when the option to use the user folder is disabled.

Cutscenes still didn't work like this, so I suppose that really is just a bug. Also, after all that, I've found that BloodGDX doesn't look nearly as nice on lower resolutions as the DOSBox version, due to the new renderer I suppose. Oh well :)

Er, I can't get BloodGDX to launch at all. I installed the latest Java version and copied the contents of the BloodGDX zip to my GOG Blood folder. When I launch the bloodgdx.jar file, the BloodGDX window appears but I get a crash a few seconds later: Java(TM) Platform SE binary has stopped working.

I'm not sure what to try.

edit: I just
uninstalled Blood
uninstalled Java
rebooted
reinstalled the 64 bit version of Java using this link: http://www.oracle.com/technetwork/java/javase/downloads/index.html
reinstalled Blood
extracted BloodGDX.jar into my GOG Blood folder
double-clicked BloodGDX.jar

My computer acts like it knows I launched something but nothing actually opens. No errors or anything. I figured there might be a 32 bit version of Java or something but I don't see it at that link.

Out of ideas.

EDIT EDIT: It looks like RivaTuner Statistics Server is interfering with the launcher. If I configure it to ignore javaw.exe, BloodGDX works! Hooray!

Just found out about this "source" port, didn't expect much since every other source port was downright disappointing but this one is actually very good. So good in fact I can't tell im running on a reverse engineered/hacked port at all! I'm running in a 21:9 aspect ratio and its so smooth. The only graphic glitch ive seen so far was some flickering when jumping in certain scenes. And I can't seem to switch to the MIDI soundtrack for some reason, the CD soundtrack is playing though.

I can finally say goodbye to the DosBox version with all the ini tweaking, mouse driver fixes and fps slowdowns once and for all.

In some areas some of the Room-Over-Room stuff still doesn't render right and you get a bit of a HOM effect, but it's pretty minimal in the official stuff. I haven't tried turning off the CD music, but if you really want the MIDI soundtrack and the options in the menu aren't working you could always move or delete the .ogg files from your main folder. But yeah, BloodGDX is fantastic, even the few issues it has doesn't make me want to go back to DosBox.

Just finished the entire game. Apart from odd visual glitches on 2 surfaces (once in Spare Parts on a platform & once in The Opera House at the trapdoor), the game looks and plays great at 1080P 144FPS. The cutscnes work fine as well once you unpack them. A shame we can't get a proper sourceport, but in the meanwhile GDX is luckily indistinguishable from one.

has anyone gotten bloodgdx to work on mac? i've tried many things but can't get it to work :(

BloodGDX released the multiplayer
For now, you have to contact some friends for it, it uses IP host/client system.
Some options like "no friendly fire" in coop (or damage 1/2 or 1/4), revive mode (new gameplay features) and other fun things for MP who has everything from the original mp of Blood, Enjoy!

BloodGDX v0.793 (12.07.2018)
1. Сlassic multiplayer
2. File path fix should working on Linux now
3. Some cases dynamic fire fix
4. AI flee damage sectors
5. Check for updates checkbox
6. NoEnemies console command
7. Palette and sound reverb fix after load game with enabled reflectiveShots or divingSuit
8. New drunk effect
9. Keyboard setup delete buttonfunc crash fix when nothing choosed
10. Broken smk file crash fix (will not load)
11. (Sound) FindChannel() can't find free channel fix
12. BloodGDX should work on JRE9 and JRE10 now

For unknown reasons BloodGDX has been removed from Makarovs website. :(

EDIT: The links have been restored. All is good again.

Direct link:

http://m210.duke4.net/index.php/downloads/download/8-java/50-bloodgdx

Okay I don't know what the seven hells is going on, but Java is not playing nice with my system for this one. It worked fine when I was running on Windows 7, but now that I've upgraded to Windows 10 I can't get BloodGDX.jar to launch.

I get a quick half-second pop-up of a command line and then nothing. Using the drag-and-drop trick with cmd I found out what the problem was:

"Error: Could not find or load main class."

I don't speak anything to do with Java. Does anyone know how I could get this thing to figure itself out?

BloodGDX is now included in Makarovs new BuildGDX launcher.

BloodGDX source code has gone open source and can be found on M210's GetLab

• https://gitlab.com/m210/BloodGDX