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
I agree with you in principle, but in this case I'm not sure it's an issue the devs can fix. It's an issue with Unreal Engine itself. A lot of the potential fixes came from videos and threads about other games.
That said, I'd like the devs to address the problem even if it's just to say "we can't help with this."
I noticed that too. I played about 10 hours of early access (whichever version was right before Huntress was introduced), and never had a single crash.
When I was researching this issue, I noticed that reports of these crashes on this forum went back more than a year. Makes me wonder what changed, and why the developers still haven't addressed it.
Now I count my blessings if it doesn't crash during cut scenes and the best thing? I can't even end the boss battle in this sad joke of a game.
Yup. In it's current state, the game is completely unplayable for some folks. The worst part is, there doesn't seem to be an easy way to diagnose why. I saw a thread last week of two people comparing specs. Nearly everything was the same. One had the recurring crash error, the other didn't. It's just bizarre.
Same story for me. Ran perfectly fine, no crashes pre-launch. Now it's a toss up if I get a fatal error during dialogue. I think this issue is more on the code than the player, especially since it's happening when the player isn't interacting with the game much.
Same. It's pretty weird that such an old and widely reported bug still exists after the 1.0 launch.