FYI: you've forget about Quest's Priorities: https://www.creationkit.com/index.php?title=Quest_Data_Tab Your assumption about the race condition between quests tells that priorities do not working at all. Meanwhile I have seen lots of bugs in Fo4, I doubt to believe in that. This is core part of the engine.
I made some research and my conclusion is the reference Emogene of DN019 quest does not have the "Allow Disabled" flag, which means that the quest starts with empty value of Reference Alias (but this is OK). My hypotheze here is: the bug may appear only in the dialogue during setting the stage 600 of the MS09 quest. If the phase 4 of scene MS09CabotHouseMission2MainEnd (MS09) would not ran properly, then this would lead to the bug with disapperance of Emogene. But, I can be wrong.
Note that your fix does not taking into account the possible dialogue bug above. If it occurs then my assumption is correct. I would try your fix and say how it is working.
As I tried to do minimal set of changes (only editing DN019): I didn't forgot about the Priority Setting, DN019 got 30 and MS09 got 45 :) ...and Emogene will be missing if her aliases are not filled right at the beginning of the game (not during the dialogue with Edward). In DN019 her aliases were also set as External, linked to MS09's Emogene(wich on the other hand is Forced by EmogeneOld) and should never be empty if everything runs OK.
An easy way to check Emogene's Aliases even in the Intro video is via the console: ShowQuestAliases MS09 ShowQuestAliases DN019 ,where all the Emogene/Old aliases should be filled. If not - so long Emogene.
<Here was a big reply, I cut it off to point only on important details> The bug occurs while using external refs to another quest's alias AND both quests are flagged with "Start Game Enabled". Usage of external refs in Quest Aliases is incredibly buggy. I have tested all possible combinations of flags and got all possible results while testing. Just trust me and Indig0, don't waste your time on this. Yes, Indig0 was right about the quest alias race condition. Also, it is obviosly that there is no such thing as "locking" (semaphores/mutexes) to wait while an alias from external quest get filled in. My interest here was in how to use external refs in quest aliases to such cases in a future. The answer is to avoid them if possible.
May i copy this from the last comment: "Yes, Indig0 was right about the quest alias race condition." Did like 200/200 checks on this quest before posting it :)
so what if she does shows up despite having the UF4P without your mod installed? was i just lucky that she showed up or will this cause issues regardless? I remember my game crashing toward the end of the quest where you fight off raiders in the asylum, couldve been unrelated but my game hasnt crashed at all up until then
Ok, there's something I don't understand. In description, it says to not to use this mod for pc, and use FPS High Physics Fix instead, I installed said mod and didn't fix anything. Emogene wasn't where she was supposed to be. I guess I'll try Emogene takes a lover Fix and see what happens...
Be sure to start a New Game as Emogene's aliases are set at the beginning. As example - using a save game at vault 111 exit won't fix Emogene as she can be bugged long before that. You can check her aliases via console right after the char. creation (more info at the end of the description).
Thank you!!! Had like 15 playthroughs without this problem and now every new game she's missing, don't understand why Beth doesn't fix their broken sh*t! Kudos to you for the fix!
Happy to hear it helps !!! ... and Kudos back to You ;)
P.S. : The Problem is caused in the initialization of the (start)new game as Beth were to lazy to put a simple Mutex in the code. Forcing 1 CPU core will prevent all the bugs ... ... more info in red in description page :)
You can always check the variables of Emogene (as soon as you started a new game) via the console as I pointed it in the description page ;) ShowQuestAliases MS09 ShowQuestAliases DN019
Went through my various characters using the console commands you put in the description and found about half of them had the bug you mentioned. Going to restart those characters with this mod active and see if it works.
What do you mean by restarting a char. as a new game is needed to get all that quests aliases initialized ? Save at V111 exit won't do the trick. All the aliases can be messed up before that.
A New Game with loading a preset is quite fine ;)
Writing this, because a lot of people think that a NEW GAME means V111 exit and that's quite wrong ;)
By restarting a character I mean starting a brand new game, though I reload the preset I saved for that character and use the same name and SPECIAL stats. I checked the console commands while the "War... War never changes" cinematic played.
I never experienced this bug while I was playing on Xbox One, but since switching to PC Emogene has been missing twice in two playthroughs. That's like... a 100% failure rate!
I've noticed this mod too late for my current playthrough, but I've installed it ready for my next one. Hopefully there'll be no more missing Emogene from now on. Thanks!
Also, there seems to be another, very well documented bug that has plagued this game for years ... the 0% Defend the Castle bug.
What is odd is, that before I started to keep my game up to date (around 6 months ago), this never happened to me. It happened to my nephew though, who funny enough, played on PS4. Once I updated (which seemed to fix all other issues I had), I started to get this bug. And I still do, to this day. Every single time I do the quest.
Is this something you can fix and look into?
Another less documented bug is during Far Harbor:
It's when The Mariner asks you to kill the Red Death. Once you come back, the event doesn't proceed and they just stand around. I had to use console commands to pass this event.
As for Defend the Castle glitch, Personally I never had any issues but will do my best to reproduce it. Meanwhile You might wonna try: https://www.nexusmods.com/fallout4/mods/12259 and check if it helps ;)
I've had this bug that many times in different playthroughs that it got so annoying. Made me wonder in each playthrough if she would actually spawn or not. Thankyou for fixing this bug.
66 comments
Your assumption about the race condition between quests tells that priorities do not working at all. Meanwhile I have seen lots of bugs in Fo4, I doubt to believe in that. This is core part of the engine.
I made some research and my conclusion is the reference Emogene of DN019 quest does not have the "Allow Disabled" flag, which means that the quest starts with empty value of Reference Alias (but this is OK). My hypotheze here is: the bug may appear only in the dialogue during setting the stage 600 of the MS09 quest. If the phase 4 of scene MS09CabotHouseMission2MainEnd (MS09) would not ran properly, then this would lead to the bug with disapperance of Emogene. But, I can be wrong.
Note that your fix does not taking into account the possible dialogue bug above. If it occurs then my assumption is correct. I would try your fix and say how it is working.
I didn't forgot about the Priority Setting, DN019 got 30 and MS09 got 45 :)
...and Emogene will be missing if her aliases are not filled right at the beginning of the game (not during the dialogue with Edward).
In DN019 her aliases were also set as External, linked to MS09's Emogene(wich on the other hand is Forced by EmogeneOld) and should never be empty if everything runs OK.
An easy way to check Emogene's Aliases even in the Intro video is via the console:
ShowQuestAliases MS09
ShowQuestAliases DN019
,where all the Emogene/Old aliases should be filled. If not - so long Emogene.
The bug occurs while using external refs to another quest's alias AND both quests are flagged with "Start Game Enabled". Usage of external refs in Quest Aliases is incredibly buggy. I have tested all possible combinations of flags and got all possible results while testing. Just trust me and Indig0, don't waste your time on this. Yes, Indig0 was right about the quest alias race condition.
Also, it is obviosly that there is no such thing as "locking" (semaphores/mutexes) to wait while an alias from external quest get filled in. My interest here was in how to use external refs in quest aliases to such cases in a future. The answer is to avoid them if possible.
Did like 200/200 checks on this quest before posting it :)
P.S.: I don't use UFO4P at all.
Hope this helps a bit :)
... and Kudos back to You ;)
P.S. : The Problem is caused in the initialization of the (start)new game as Beth were to lazy to put a simple Mutex in the code. Forcing 1 CPU core will prevent all the bugs ...
... more info in red in description page :)
ShowQuestAliases MS09
ShowQuestAliases DN019
Edit: It works. Endorsing!
Save at V111 exit won't do the trick. All the aliases can be messed up before that.
A New Game with loading a preset is quite fine ;)
Writing this, because a lot of people think that a NEW GAME means V111 exit and that's quite wrong ;)
I've noticed this mod too late for my current playthrough, but I've installed it ready for my next one. Hopefully there'll be no more missing Emogene from now on. Thanks!
Thank you for this mod.
Also, there seems to be another, very well documented bug that has plagued this game for years ... the 0% Defend the Castle bug.
What is odd is, that before I started to keep my game up to date (around 6 months ago), this never happened to me. It happened to my nephew though, who funny enough, played on PS4. Once I updated (which seemed to fix all other issues I had), I started to get this bug. And I still do, to this day. Every single time I do the quest.
Is this something you can fix and look into?
Another less documented bug is during Far Harbor:
It's when The Mariner asks you to kill the Red Death. Once you come back, the event doesn't proceed and they just stand around. I had to use console commands to pass this event.
As for Defend the Castle glitch, Personally I never had any issues but will do my best to reproduce it. Meanwhile You might wonna try:
https://www.nexusmods.com/fallout4/mods/12259
and check if it helps ;)
Thankyou for fixing this bug.