Jump to content

Bethesda Modding Diary - 10 June 2022


gregaaz

668 views

Greetings, folks! Today the focus is going to be on finishing up the LOTD vs. TGSC deconfliction patch, and then (if time permits) doing the leveled lists. If I don't run into any big surprises, that might make for a deceptively small blog, since a lot of it is going to to just be repeating the steps I did in yesterday's entry. 

 

Revisiting the Cheongsam

Spoiler

So yesterday we had some issues with the COCO Cheongsam. It was rendering weird, the morphs weren't firing right, and it was generally a mess. Today I went back in to do more testing and verified that at least on the zero-slider body it looks OK.

 

image.png.e0fcf90a63884f9d03849965fad54cf2.png

 

Now, one thing I did do was go into OBody Standalone's configuration file and turn off the ORefit option. This feature is really designed with CBBE 3BA in mind, but I had been experimenting with using it on the BHUNP body. I hadn't previously noticed any major issues, but I suspect it might have something to do with the problems I encountered on this outfit and I turned it off from an abundance of caution. The Nipple and Genital customization are also aimed at CBBE 3BA, but I'm going to continue fiddling with them for the time being. It seems that, at worst, they do nothing and at best they may be partially functional on BHUNP - though I haven't thoroughly tested them yet.

 

image.png.80b4324a138b3190dcd57f710e8a1cfa.png

 

Some more good news - the high heels issues might have been a false alarm. I forgot that I was taking screen shots of actors who were playing idle animations, which sometimes override heel data. As you can see here, at least on the player character I was getting heel functions - though this too needs more observation and testing. Also, 3D pubic hair doesn't appear to protrude enough from the body to intrude through the dress. I suspect Futanari may still be an issue, but that's a pretty common problem with many outfits like this and I'm not all that bent out of shape. Worse come to worst, I can make sure that "known" Futa who use this out have the panties equipped to suppress Slot 52.

 

Finally, switching the body morph did no result in deformed or wrongly-fitted clothing, and I suspect that this is the fruits of turning off ORefit. If I had to guess, this outfit has some residual CBBE scaling data in it so it responded to calls made by ORefit in an unintended way.

 

As an aside, the test morph you see in the third image is the Jill Valentine Body from the Accurate Bodyslide Series. I've been pretty happy with the bodyslide presets in this series so I wanted to make sure I gave the mod some visibility!

 

image.png.7a439060107dea4e0fcc49fa05e5fef3.png

image.png.1b879913383e39e1c0117e593531c677.png

image.png.b1b85739ba4d5d9dc57c2e3146f8b2f3.png

 

So, the player's body looks OK now. Let's head over to the Blue Palace and see how the servant girls look.

 

image.png.51b092ff5655ce90d28f2c79207dc698.png

image.png.fa58a86130de16a73b6d4491797a4ea5.png

 

Still some minor issues - the high heels aren't working and there's some minor mesh intrusion on Hilde's bust. Still, these are much less noticeable issues than before. I'll need to loop back and give those high heels some extra attention, but I don't rank this in the same tier of problem as we were seeing yesterday. I think we can move that one to the back burner for now before we end up going down a huge rabbit hole in Outfit Studio and fail to get anything else done today!

 

Possible Trouble on the Horizon

Spoiler

During the recent testing in Solitude, I noticed pronounced FPS drops within the SolitudeWorld space. Worse yet, I got a CTD that cited TBBMalloc.dll, which suggests the game ran out of memory. Now, I was running with a billion chrome tabs open, music playing on Youtube, etc., so its possible that I'm just in a temporary degraded memory state at the moment, but I'll need to keep a close eye out for whether or not this persists, as it could point to a runaway script of some sort. If so, the Papyrus Log and ReSaver should reveal the culprit between the two of them. I do note that the Faction Economy script has a large number of instances, 

 

image.png.4be8662c62316f94f32fc3dcbbf947c2.png

 

Now, these issues we're seeing here might be early game artifacts associated with functional mods starting up for the first time that were compounded by me moving the player character to a densely populated are like Solitude that's also used as an initial spawn point for many traveling NPCs. The suspended stacks are essentially non-existent before I leave the Blue Palace interior cell, so more research and observation is necessary before concluding that there is a "real" problem here as opposed to a malfunction resulting from unintended gameplay, but I'm definitely now on alert for potential problems. 

 

image.png.74c71091dfa89fe0f40938452b5b6b7f.png

 

Hopefully we won't have to revisit this, but if we do it'll at least be a good opportunity to talk about finding problems by parsing the saved game and the Papyrus log.

 

Gemstone Patching

Spoiler

As expected, I didn't find any big surprises with the remaining gemstone patching, but it did eat up most of my hobby time today. However, the end result is a comprehensive patch that remaps all the TGSC content in LOTD back to its original source data within Mystic Legacy. Let's hop into the game and take a look at it.

 

Let's head over to the Hall of Natural Sciences and spawn the gem testing chest from LOTD.

 

image.png.2c026dcbc936a2a6d47cdf91598e4d0a.png

 

Inside, you can see the TGSC items seamlessly displacing their LOTD versions, like these Tourmalines below:

 

image.png.96b0b82fabf379462264dfccbf6eb9df.png

 

Now let's confirm that the displays work properly - we'll take the contents of this box and start filling shelves. As you can see, all the items properly move to their shelves. There's a little bit of jostling in a handful of areas where TGSC has different meshes, but in functionally everything is working correctly!

 

image.png.06c689c03507a6b0a50adecba1df9526.png

 

Well, that's some good progress for today! This weekend, we'll wrap up by fixing the leveled list issues, and then finally by completing normal conflict resolution on these mods. See you then!

 

 

Edited by gregaaz

5 Comments


Recommended Comments

3k stacked is pretty insane. You probably know but the key here is to see if they go away (resolve on their own) on a later save or not. If not your save is likely toast.

 

I should mention, the latest version of Toys&Love fixed two cases of script vulnerable to stacking in high load. One was the "explosion cleanup", and the other was nipple bell and chain sounds.

 

I never saw them stack and then not resolve. Nor did I see them stack dump. So I'm not saying its your problem, most likely its not, but it would contribute, and be best if you have latest version. Not sure if you do or not.

Edited by VirginMarie
Link to comment
On 6/10/2022 at 5:42 PM, VirginMarie said:

3k stacked is pretty insane. You probably know but the key here is to see if they go away (resolve on their own) on a later save or not. If not your save is likely toast.

 

I should mention, the latest version of Toys&Love fixed two cases of script vulnerable to stacking in high load. One was the "explosion cleanup", and the other was nipple bell and chain sounds.

 

I never saw them stack and then not resolve. Nor did I see them stack dump. So I'm not saying its your problem, most likely its not, but it would contribute, and be best if you have latest version. Not sure if you do or not.

 

After some further digging, its starting to look like Skyrim At War is wigging out again. At some point I'll drill into this and get it fixed - or just dump it. With all the drama from the author, at times I wonder if its worth the trouble to try and maintain support for his mod in this build. On the other hand, I'm overdue for a script-focused diary entry, and while the author published the scripts closed-source, it shouldn't be too hard to decompile and evaluate them.

 

image.png.e8b110676453d7817065089a0101efd2.png

Edited by gregaaz
Link to comment
1 hour ago, xtremer said:

Any chance you could release your TGSC/LOTD patch?

 

I took a look at TGSC's permissions and they do allow for modifications as long as no assets are rehosted off the Nexus. 

 

Spoiler

image.png.84612e6bb56feadfb60bdaea9a48c517.png

 

I double-checked the patch I made and it looks like it picked up some dependencies on other mods. Let's take a look and see if we can peel those out and make a standalone patch for you.

 

image.png.ee1a305974b1e76bdf05c7816ef87615.png

 

Fortunately most of these only impact a few records each, so it won't be too hard to forward these records to my conflict resolution patches and peel them out of the DBM-TGSC patch.

 

image.png.ee6a7729e0b695a024864e50f5608557.png

 

HOWEVER, on closer examination we see that these dependencies are actually relevant to the change, and I don't want to just dump them into a rollup patch lest they get accidentally removed in the future.

 

image.png.46fa61aa4c810f14d0d99c786ee765a2.png

 

What I'll do instead is make a duplicate of the patch and using that as a working file split it into a few sub-files that should allow you (or any future end user) to fine tune the patch to their configuration.

 

With that done, now we have standalone patches for each mod combo: one that addresses the direct LOTD vs. TGSC conflicts and 3 more for the conflicts with specific LOTD patches for other mods.

 

image.png.32a643e27d05676158abcd7cab3de4cb.png

 

You can download those files below. Have fun!

 

DBM_TGSC_Only_Patch.espDBM_OCW_TGSC_Patch.espDBM_3DNPC_TGSC_Patch.esp

 

EDIT: Sorry, I had to remove the Kaidan patch because Kaidan 2 has closed permissions for modifications. 

Edited by gregaaz
Link to comment
29 minutes ago, gregaaz said:

You can download those files below. Have fun!

 

DBM_TGSC_Only_Patch.esp 45.42 kB · 0 downloads DBM_OCW_TGSC_Patch.esp 540 B · 0 downloads DBM_3DNPC_TGSC_Patch.esp 443 B · 0 downloads

 

EDIT: Sorry, I had to remove the Kaidan patch because Kaidan 2 has closed permissions for modifications. 

Thanks, my skyrim currently isn't really in a usable state (i'm building a Mutagen-based successor to zMerge, which almost works (there's some wonkinesss with non-worldspace cell records), so my data folder is a mess), but these will be very useful when i finally sit down to make a working load order.

Link to comment

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. For more information, see our Privacy Policy & Terms of Use