|
|
journeyman
|
OP
journeyman
Joined: Aug 2022
|
So, I've gotten this message a fair number of times, usually before finishing the tiefling/druid issue and the party starting. It's useful when there actually is someone with a marker above their head, but mostly there is not a single character (nor Scratch, Withers, etc) with any new dialogue.
What's mostly annoying about this, is that I fear there actually *is* some dialogue that is special... but it just won't trigger in any visible way due to some glitch.
"Tribe?"
|
|
|
|
veteran
|
veteran
Joined: Jun 2022
|
I got the same after getting Volo to camp. Nobody actually has a conversation pending, yet the message pops up saying someone wants to talk.
At least I think it is caused by him. I try to talk to him and the dialogue above his head pops up saying; "Not now"/"Later", so he is stuck and cannot be talked to.
|
|
|
|
Volunteer Moderator
|
Volunteer Moderator
Joined: Feb 2022
|
I got this issue too, but not until after the party so I blamed Halsin, particularly as talking to him after his initial chat the party was a bit buggy (I’ve not had a problem with Volo, though).
As far as I can tell it doesn’t mess up genuine dialogue scenes as I still got a yellow exclamation mark when someone did want to talk.
I reported my bug to Larian, so if yours is the same problem then hopefully they’re already aware and it’s on the list to fix.
"You may call it 'nonsense' if you like, but I've heard nonsense, compared with which that would be as sensible as a dictionary!"
|
|
|
|
veteran
|
veteran
Joined: Jul 2022
|
The problem with "not now, later" from Volo and the problem OP mentioned are 2 different things. For those encountering a "later" from Volo I can recommend a workaround - go into sneak in his sight and immediately try to pickpocket him. He will run away and you would lose 5 attitude points but it will bring back a dialogue possibility.
|
|
|
|
addict
|
addict
Joined: Aug 2022
|
I've had this issue.
Here what was happening in my case.
I had fed the owlbear cub during a previous long rest. After that, the cub never appeared but I would get the "Someone is trying to talk with you..." message (even though I had talked to everyone). It seemed to me that the owlbear was there but not really.
To "fix" that, I had to do the following : - Go back to a previous save and feed the owlbear again. - Long rest again back to back without moving an inch or TP during the day (very important to not move) so the owlbear could properly appear at night. - Repeat last step until there aren't anymore owlbear related event at the camp.
With "luck", this is the same issue in your case? But it's definitely not normal I'd say x)
Last edited by MelivySilverRoot; 24/08/22 12:13 AM.
|
|
|
|
Volunteer Moderator
|
Volunteer Moderator
Joined: Feb 2022
|
I've had this issue.
Here what was happening in my case.
I had fed the owlbear cub during a previous long rest. After that, the cub never appeared but I would get the "Someone is trying to talk with you..." message (even though I had talked to everyone). It seemed to me that the owlbear was there but not really.
To "fix" that, I had to do the following : - Go back to a previous save and feed the owlbear again. - Long rest again back to back without moving an inch or TP during the day (very important to not move) so the owlbear could properly appear at night. - Repeat last step until there aren't anymore owlbear related event at the camp.
With "luck", this is the same issue in your case? But it's definitely not normal I'd say x) Oh, now you say that, it could well have been owlbear cub related in my case, too! It’s happened in two playthroughs of patch 8 and I think in the first case I saw the same owlbear issue as you, and in the second I happened to go back to the goblin camp and though I’d fed the owlbear in my camp it reappeared running around the deserted camp and I interacted with it there. In neither case did it properly reappear, so I just reported the bug and carried on. Larian support did confirm that the owlbear bug was known, and fingers crossed if they fix that it’ll fix this one too.
"You may call it 'nonsense' if you like, but I've heard nonsense, compared with which that would be as sensible as a dictionary!"
|
|
|
|
stranger
|
stranger
Joined: Aug 2022
|
I got the same after getting Volo to camp. Nobody actually has a conversation pending, yet the message pops up saying someone wants to talk.
At least I think it is caused by him. I try to talk to him and the dialogue above his head pops up saying; "Not now"/"Later", so he is stuck and cannot be talked to. I had the same issue with Volo and then again with the Tiefling Bard at the party. I assumed it had to do with me playing a bard as well.
Last edited by Sojuma; 28/08/22 08:49 PM.
|
|
|
|
veteran
|
veteran
Joined: Jun 2022
|
I've had this issue.
Here what was happening in my case.
I had fed the owlbear cub during a previous long rest. After that, the cub never appeared but I would get the "Someone is trying to talk with you..." message (even though I had talked to everyone). It seemed to me that the owlbear was there but not really.
To "fix" that, I had to do the following : - Go back to a previous save and feed the owlbear again. - Long rest again back to back without moving an inch or TP during the day (very important to not move) so the owlbear could properly appear at night. - Repeat last step until there aren't anymore owlbear related event at the camp.
With "luck", this is the same issue in your case? But it's definitely not normal I'd say x) After further testing I can confirm that this bug is indeed caused by the Owlbear.
The issue is that sending it to the camp breaks either its AI or event script, so it doesn't despawn from our camp after the first scene and eventually ends up spawning back in the Goblin camp. Which then causes this permanent prompt bug because you no longer can advance the Owlbear camp scenes.
However just like MelivySilverRoot mentioned, if the player immediately after sending the Owlbear to camp keeps resting back to back in order to exhaust all the scenes with the Owlbear, the dialogue prompt for the Owlbear will properly appear.
Unfortunately the Owlbear does permanently remain bugged since its AI script doesn't work, so because of this it doesn't sleep with Scratch nor chase him around the camp.
Whether it remains at the camp afterwards for good I cannot say as I have only done enough testing to confirm it is indeed the Owlbear, so I've submitted an official bug report and it is being investigated.
|
|
|
|
stranger
|
stranger
Joined: Sep 2023
|
Is there a place where one can read status and updates regarding this bug?
My Status -------- Multiplayer LAN Ending Act 2 - Road To Baldurs Gate Ends up in camp End Arabelles parents plot line Astarion got an exclamation mark; But does not want to talk; or has nothing new to say
Can't rest Message: Someone in camp still wishes to speak to you ---
TRIED ------- Quit client on all computers Reloading saves up to 1 hour back Still same issue
if in doubt, use C4
|
|
|
|
old hand
|
old hand
Joined: Jul 2023
|
Is there a place where one can read status and updates regarding this bug?
My Status -------- Multiplayer LAN Ending Act 2 - Road To Baldurs Gate Ends up in camp End Arabelles parents plot line Astarion got an exclamation mark; But does not want to talk; or has nothing new to say
Can't rest Message: Someone in camp still wishes to speak to you ---
TRIED ------- Quit client on all computers Reloading saves up to 1 hour back Still same issue I'm not on multiplay but I get that message every time. It gives me the option of resting or not. It doesn't stop me resting.
|
|
|
|
stranger
|
stranger
Joined: Oct 2023
|
I had this same problem at the end of act 2 transitioning to act 3. Astarion was the culprit after having 2 main dialogues happen consecutively. After spending 10 minutes talking to everyone and losing my mind, I went and smacked the shit out of the vampire, and that fixed it. If the person has bugged progression dialogue, the fix for me was to hit the person.
|
|
|
|
|
|