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
The author of this topic has marked a post as the answer to their question.
Discussions Rules and Guidelines
Report this post
Yeah, I thought the quest would fix itself with 1.4.2, however, this quest was qued already as a task in 1.4.1 (not started yet, just in my log), so it didn't load fresh from v1.4.2, meaning the bug was in the save from 1.4.1.
Most bugs in quests are fixed in the files, but if a player already has the quest in their log then there's a good chance the quest will still be bugged with a possible mis-match of logic, breaking the quest (IMO).
You can try leaving the area for a day or two. Example, travel far away during the day to Rattay, then travel back to Ushitz. Also, if you are running any mods, maybe mods are interfering with the interaction of the sitting command.
Most of time, leaving the area, saving the game, then returning to the area seems to fix most problems. Also, save the game, then exit game, then reload the save. You can also trying the "SAVE & QUIT" option to quickly save the game and exit the game with one click, then restart the game and see if you can continue with the quest (allowing you to use E to sit).
I spent a few days hunting and exploring during which time 1.4.2 was applied, then went back to Theresa and it worked perfectly.
Are people still getting it with 1.4.2 in playlines started with 1.4.1?
Yes, in my case I started a fresh new game back when 1.4.1 came out (my third play through, 2nd play through cut short by update to make sure).
I encountered the bug last week and reloaded a save game before starting the quest then continued playing for several game days. My only fix was to use ESC before the loop started back at the mill, at the end. I used SAVE & EXIT and noted the quest ending, then started the game and loaded the temporary save, which loaded fine and everything was ok.
Yes, this solution works!
Is this game in Early Acces ????????
WTF Devs !
I think it has ruined my entire save. What in the world. Now every time I start off from the last save It starts up the conversation even if I am not with her and loads me into the loading screen when I fast travel and wont load into the game again.
Yup, my most recent save is gone because of that bug dangit.
This is the only game we have downloaded on our computer.
Our computer has been looked over by a family member who owns and operates a computer store. He built our computer for gaming. He also knows KCD and what will run the game properly. We have TONS of space on our drives with a KILLER GPU that can and will play any game out there. As I stated before, we have no other game downloaded onto the computer. I have only one saved KCD game. So it's obviously a bug within the game. People are complaining of similar bugs within the game. You may know the game well, but you are not a Dev that built the game.
Anyway, there is a workaround - after the running "contest" with Theresa, she will invite you to sit with her on the grass. Make sure you sit as close to the mill as possible. If you do, the bug won't trigger, because after "walking" back, Henry will be sufficiently close, and Theresa will just say goodbye. If you sit too far, the dialogue will repeat again, and you will get stuck in an infinite loading screen.