Stuffyy

Are you all playing on unmodded games? I sporadically have this issue aswell, and always thought my mods are to blame.

I think thats a new "feature" from bethesda to prevent you from cheating with the archivements. I'm pretty sure its not easy to "untag" a savegame to not-modded. You may have to check some savegame-editing tools.

It's probabably one of your mods causing a conflict. Since you dont have that many mods loaded, I would suggest trying to disable a few of them, check if it works. If it doesnt, continue to disable mods till it works. Start with the smaller mods that dont have many downloads or endorsments, since those are most likely to have bugs that are not reported.

I would recommend a clean driver installation in general before you try anything else. Uninstall the driver completely, download the version speedynl mentioned and test again. Most of the time this fixes it.

Do you get it everytime you start/play it? Or only sometimes? At what exact moment does it happen? Did it work fine with older drivers ( if you played fo4 with older drivers) ?

No problem. Hope you get it resolved somehow.

Thats weird, I always thought setstage forced the game to start a quest no matter what. Have you tried to "usual" reset commands on dogmeat like "kill" and then "resurrect 1" ? Other than that, I'm not really sure on what to do. If you already played the game, you could try skipping the "Reunion" quest with console commands.

Did you try to use the "setstage" command already? ( if I understood you correctly and you still have the "Getting a Clue" quest )? If you did not try that, try this command ( MAKE BACKUP SAVES ): setstage MQ105 1000if that doesnt help, try: completeallobjectives MQ105 or if that doesnt work completequest MQ105 If the quest "Getting a Clue" has already ended and you somehow havent gotten the "Reunions" quest, try setstage MQ106 10

Is your quest called "Getting a Clue" or "Reunions" ?