Creation Kit Cell Changes Not Taking Effect

[Synthesis]

I'm a fan of the Frostfall mod for adding exposure effects (cold, hot, etc.) to Skyrim, and I've been modding added exterior/interior areas in Skyrim to now have their water temperature reflected (for example, hot springs areas) instead of being uniformly freezing. I do this by adding certain effects--FXSteamBillow, for example--to the areas. 

 

Unfortunately, no changes I make in Creation Kit seem to show up when I load up the game--that includes after a clean save. Am I overlooking something obvious--forcing the game to rebuild an environmental cell or something? According to the creation kit, they should show up perfectly. Any help would be much appreciated, hopefully this is in the right area since I'm just trying to add already-existing effects in the game. 

[Rayblue]

The solution is to fast-travel to another distant marker, make a hard/new gamesave, and exit the game; disable the mod you're working on, run Skyrim again, make another hard gamesave and exit. Then enable the mod, run Skyrim and you should see the changes you want.

 

If you're editing an external cell, make a hard gamesave within an interior cell; vice-versa if it's an interior cell.

[Synthesis]

Thanks, Rayblue, I'll try that now.

 

EDIT:

 

Damn, didn't work. I fast traveled from Solitude (near where the mod is set) to Whiterun, saved inside the Inn, deactivated the mod, saved inside the inn again, activated the mod, then fast traveled back to Whiterun and ran to the location--no changes, just as before. The game just doesn't want to acknowledge any changes I make to the ESP. 

[b3lisario]

Can it be a load order issue? maybe there is another mod after the one you are editing that overwrites your changes. I'm thinking on light overhaul mods or something like that.

Use tes5edit to check if another mod is altering the same cell.

[Synthesis]

One of the first things I tried was moving it to the bottom of the load order, but I haven't tried TES5Edit at all, so thank you for the suggestion. How would I go about doing that, I haven't used TES5Edit since before the Creation kit came out. 

 

The fact that anything I put in with Creation Kit--say, a campfire instead of a steam effect--doesn't show up is telling, I think. 

 

EDIT: Okay, I loaded up my mod list in TES5Edit and the Worldspace entry under the mod heading IS highlighted red, indicating a conflict--but with what, I'm not sure. It just says "000003C Tamriel Bordeciel".

 

EDIT EDIT: So, I disabled all the conflict mods for the ESP that TES5Edit pointed out--obviously, I couldn't disable the ESP for the file itself, that defeats the whole point. I noticed it said "Bordeciel" instead of "Skyrim" like the other mods that originally effected that line (presumably mods that change the world geography). Are none of my changes working because they only work on "Bordeciel" and not the game world? 

[b3lisario]

The right panel shows the detailed info of what are being modified in the selected record. Also shows the mods that are affecting it.

 

But if your mod is at the bottom it should "win", so that's no the issue.

Anyway the TES5Edit tool is useful to locate and fix unwanted edits.

[b3lisario]

Bordeciel? I don't think so.

I'm guessing your game or CK is in French. Any edit you do will use the localized strings.

[Synthesis]

Yeah, the area I'm editing is from an existing mod--should have mentioned that (Nikitaa's Project Sekirei, I'm trying to add FX sources to the Onsen that will allow for temperature effects--that explains the French). So it's not that. 

 

Given that the problem isn't fixed when I load it last, there must be something about how the game caches that it refuses to update changes to that mod. It's even stranger how I can uninstall the ESP, play the game and have that area be empty (of course), but when I reactivate the modded ESP, none of my changes show up. 

 

EDIT: Well, I did a test in Creation Kit, and I was able to alter the environment with my own ESP--just nothing in the cell created by Nikita's ESP. It must have something to do with the ESP file itself.