I got an email from CDPR Support last week saying they're aware of the problem. My guess is this might not have been a known issue until past the "due" date for 1.22Patch 1.22 today and it still not fixed. This may be a side mission but it is a major one, how can they keep missing it?
I report it, right after 1.2 release, but they certainly work on other problemsI got an email from CDPR Support last week saying they're aware of the problem. My guess is this might not have been a known issue until past the "due" date for 1.22
Old okSo it is claimed to be fixed in the 1.23 update but I am still having the same issue and have tried from both old and new saves.
Maybe he has a new save file where he has been avoiding the quest.Old ok
But new save ? "fresh" save in 1.23 ?
(sound weird to be as far with new start in 1.23)
I would try to delete all save files that are related to the quest, then validate game files via Steam/GOG and try again.So it is claimed to be fixed in the 1.23 update but I am still having the same issue and have tried from both old and new saves.
Yes, the "old" save file was a file I was avoiding the quest. Not an old 1.1 save or anything. Still having the issue and have pretty much given up on the game. I feel as though I would have to start an entire new game for these fixes to take effect which is more trouble than it's worth.Maybe he has a new save file where he has been avoiding the quest.
I would try to delete all save files that are related to the quest, then validate game files via Steam/GOG and try again.