Issue Data
|
Issue #28956: Civil war commanders in two places at once
I'm running the latest version of SkyrimSE and USSEP, new game, nothing else enabled.
Civil war commanders are appearing in camps when they shouldn't, essentially causing them to be in two places at the same time. Its effecting all the military camps that are empty from the start. Also the wisp mother doesn't appear at the Stormcloak Winterhold camp, Kai Wet-Pommel will be there instead and nothing else. Screenshots: https://imgur.com/a/cwEHkwF |
Related Issues: 29207
I have the same issue in my game where the Winterhold Stormcloak Camp would be if the Imperials controlled the hold. The thing is, I'm almost positive this didn't used to be the case because I would have noticed when I fixed a number of enable parent settings years back.
Comment #1 Apr 17, 2020 7:56 am
Edited by BlackPete on Apr 17, 2020 8:25 am
@BlackPete, Its actually been an problem since last year, October/November I think was the last time I played and had the same issue. I couldn't figure out what was causing it. Luckily I encountered it early this time while setting up my mods.
Comment #2 Apr 17, 2020 8:17 am
Edited by Arenthia on Apr 17, 2020 8:17 am
In the case of Kai Wet-Pommel, the problem may be that the trigger box he's linked to is missing its enable parent setting (judging from how the commander is set up at the Pale Stormcloak Camp). Maybe that's the case with the other commanders, but I haven't checked yet. I have no idea what's wrong with the wisp mother that should be there instead. Again, I could have sworn these weren't issues years back in LE Skyrim, so either I'm remembering incorrectly, some fixes were lost during the USLEEP/USSEP transition, or Bethesda messed them up in an official patch.
Comment #3 Apr 17, 2020 8:49 am
Edited by BlackPete on Apr 18, 2020 8:52 pm
@BlackPete, You're right, I checked the trigger box for Kai Wet-Pommel and it has no enable parent.
Can you guys try this file and see what happens?
Unpack it to your Data\Scripts folder and then load a save somewhere other than one of the camps and then go see if the commander shows up when they shouldn't.
Attached Files:
CWMissionGeneratorTriggerScript.7z
Unpack it to your Data\Scripts folder and then load a save somewhere other than one of the camps and then go see if the commander shows up when they shouldn't.
Attached Files:
CWMissionGeneratorTriggerScript.7z
Comment #5 Apr 18, 2020 7:48 pm
Edited by Arthmoor on Apr 18, 2020 7:48 pm
Yeah, it works like it should now.
Comment #7 Apr 18, 2020 8:45 pm
Edited by BlackPete on Apr 19, 2020 3:28 am
Ok, then that was entirely due to an undocumented change in CWMissionGeneratorTriggerScript that somehow got in, and since none of the commits to the private GitHub repository show this happening, it had to have been done before USSEP was properly released. Which fits, because that script is NOT altered on the LE side in USLEEP.
Since you guys were using a copy I recompiled from vanilla that's why it works again
Since you guys were using a copy I recompiled from vanilla that's why it works again
Showing Comments 1 - 8 of 8