Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
I feel as both a GOG user and Steam. (I own the game on both.) Their GOG communication is 0%. We are still using the original game's forums there and we don't get staff there from Nightdive at all. People like myself either have to re-post things there or GOG users have to ask here. The game is sold on both stores, why do you not support both stores?
Even on Steam their communication is not great on Blood. They released an update and posted how to access saved games in their patch notes. Why not sticky it? I've had to answer that question several times today because Nightdive decided to break them then add it as a footnote on something that not everyone will read.
But on Blood itself. Why spend the money getting this on a version that has alot of issues after their first patch (that seems to cause more than it fixed) and not really fixed or mentioned any of the massive deal breakers. We still have terrible saving times, the rebinding confusion still exists, we still have people having issues with graphics because Nightdive suddenly deciding its too old for Blood, the fact that you can get stuck on a certain level due to a spider slapping you in the face and causing you to go out of bounds, not to mention countless others that they failed to fix.
Also this patch added more such as their a pitchfork can't break windows and the whole saving thing.
Why would you worry about any of that when GDX or NBlood doesn't have half those issues and is free?
That's a flat out lie. GDX mouse is horrendous compared to fresh supply.
I just want to chime and say my experience matches yours. I mean it's completely bizarre to me how people have completely opposite experiences in regards to these various ports, but for me the experience, on every system I've ever used, has been this:
Any port built off EDuke stutters if you enable vsync. If you run without vsync, the tearing is unbearable, especially any time there is screen shaking from explosions or scripted events. World Tour was the first Duke port to fix this in my experience. In addition to this issue, Megaton and SW Redux had inaccurate colors. World Tour is a million times better than either of these ports. That's my experience.
Now as far as Blood goes, BloodGDX has the worst stutter of any Build port I've ever played. Completely unplayable. On top of that, it uses the same exact mouse aim from the DOS version, which was terrible because it had bias (if you were moving horizontally even a little, vertical aim is crippled). On top of this, it has inaccurate colors. NBlood is decent. It has good colors, and the mouse aim is fine as long as you turn mouse filtering off. Only problem is it has the standard EDuke stutter thing going on. With the state Fresh Supply is in right now, it's hard to say it's clearly the best way to play vs. NBlood, but even with all the problems it has right now I'd probably still give it the nod. Hopefully after some more patches it will be the definitive version.
Now I will say, the latest builds of EDuke32 I've tried lately have been much better in terms of the stutter problem as long as I lock to 120fps on a 144Hz g-sync monitor. I'm inclined to say it's finally been fixed (at that frame rate anyway), but I'd have to do more testing. Every now and then I download the latest version and play a few levels, but I'd have to play through at least an entire episode to say it's fixed with any confidence, but definitely check it out if you haven't in awhile. I've heard something about mainline EDuke32 getting NBlood support? If that happens and the stutter is really fixed, I think it would probably be the best way to play the game if this version never gets polished to the level it needs.
EDIT/ I take back what I said about BloodGDX's mouse aim. I tried it again and it's fine as long as vsync is off and no fps cap is set. I think it was just the horrible fps cap stutter making me think the aim was off. Also the latest NBlood isn't stuttering for me with vsync as long as I set the fps cap to 120 (on a 144hz g-sync monitor), just like recent versions of EDuke32.
That is really strange, but BloodGDX as I understand it has more of its own independent basis from eduke, so it might be a different reason that you have problems with it. It worked great for me.
I'll give the newer build of eduke a try.
Hmm that is strange. Maybe there is a particular frame rate it works best at. I couldn't be bothered to test it too much because of the bad mouse aim and colors. I tested it and NBlood at the same time and determined I much preferred NBlood.
EDIT/ Tried it again. It doesn't stutter as long as vsync is off and no fps cap is set, so basically it's just like Megaton or SW Redux in that regard. I guess it's fine if you don't mind the screen getting torn to shreds anytime there is screen shaking (not something I can tolerate well). Still prefer NBlood since I've now got that running without tearing OR stutter, and the colors are more accurate.