Chastity Quest - Some Issues

Ugh. So, this isn't a happy fluffy bunnies and rainbows post. Rather, it's a letting you know there's been a rather serious problem, post. Specifically, the heavily modded Skyrim installation that I've been using for Chastity Quest...may have bit the dust. (Don't panic yet!) Earlier this month, in an attempt to resolve issues with both DAZ3d and Skyrim, I reinstalled Windows 10 on my system. I was very careful to backup any and all asset/mod/whathaveyou files for both Haven's Port and Chastity Quest. And...the reinstallation proved to be a needed thing, as Daz3d was working much better for Build 3 renders than Build 2. Likewise, the lag issues with Skyrim vanished and I had thought, at first, that I'd gotten through with everything functional. Unfortunately, when I went to start capturing all the scenes I needed for this month's update...I discovered that the build of Skyrim, despite being a very carefully made direct copy, has become wildly unstable. To the point that I've spent the last 48 hours in a painstaking effort to restore its functionality. 

Ultimately, I think I've failed outright. But you still shouldn't panic. 

I've known from the beginning how unstable Skyrim can be. As such, I've taken very solid measures over the last year, to ensure that, even should the worst happen, I would be able to reconstruct Kiralia and most of the main characters in a new, clean installation of Skyrim. My ability to restore all major characters is not really in question.  Likewise, most or all locations should be restorable. This isn't a critical game-ending issue...just a time consuming one.

Effectively, that means I simply can't make the full Build I was intending to do this month. That doesn't mean there won't be a release. To be CLEAR, there will STILL be a content release. It's just not going to be the content I had originally planned. Essentially, the instability that has developed in the Skyrim installation is that I cannot, for some reason that I can't sort out, move between locations. Also, saves in a few places, like whiterun's entire area, simply crash when loaded. However, SOME areas load and run 100% cleanly. Which means I can still use the existing framework in a sort of hodgepodge way, in order to add more scenes. This means that there will be something of a scattershot of new scenes, rather than the usual planned-out and themed content package. Ultimately, however, there will still be a release with, hopefully, a decent number of scenes. A lot is going to depend on how many areas I can make functional enough to get assets from.

I have, in fact, already recorded 2 scenes to add to Iris's potion game. Rodger with be getting at least a pair of his own scenes as well. Likewise, some scenes I had intended to add to Rosyln may get added early. They were supposed to happen after the Thieves Guild Quest 2, which was the originally planned major content for this month. But there's no real reason I can't add them earlier with a few adjustments. That makes for at least 7 scenes right there. And those are only examples. I need to check on the scenes I had planned for the Guard Captain and the Pony Express to see if some of them may be viable to add this time as well. And if I can get the exterior New Landing area to load, there are some other options as well. Suffice it to say, that I think I can still produce a decent number of scenes.

This is also going to mean that next month, I'm going to have to somehow find the time (I have no fucking clue how, but I'll work it out, somehow, I usually do) to rebuild a stable iteration of the game. So I'm super super frustrated, and not a little depressed at the moment. But you needn't worry about the ability of the project to go forward. This is a delay beyond my ability to predict or control, but it is only a delay. It was something I knew from experience with Skyrim in the past could happen, and had long since taken measures against. That just...doesn't keep it from still being frustrating and deny-inducing.