0 of 0
File information
Created by
The Blender AnimatorUploaded by
TheBlenderAnimatorVirus scan
Safe to use
videogame_asset My games
Install hundreds of mods with the click of a button.
Notifications
-
Give Feedback
74 comments
"There are 3034 stacks and 3558 frames, which probably indicates a problem.
PuddleWeatherScript occurs the most as a stack frame (3266 occurrences)"
I'm uninstalling this untill I find a solution. Please, if you can, let me know what is happening.
TB's Improved Puddles v2
Wet Whiterun v5
The Puddles Of Riften v2
Dynamic Puddles - Whiterun v2
So what's the difference between all those mods?
TB's Dynamic Puddles v1.9 was a single mod, now it's a frameworks?
And how should I array them with RWT?
I do love your works but these are such a chaos you know. :^(
I recommend choosing one of them however make sure you only choice one variant for each hold.
TB's Improved Puddles v2 - a texture replacement mod, you probablay want it to overwrite RW2 since he sseems to always want to improve that mod
Wet Whiterun - adds a bunch of static puddles,etc to whiterun in a way that is incompatible with the dynamic puddles
The Puddles Of Riften v2 - the same thing, but in Riften
Dynamic Puddles - Whiterun v2- using the framework that is the mod of this page, it adds some particular dynamic puddles to whiterun , also includes the second mod's improved textures, if you want it to
There are ways to improve performance here actually. I can assume that you're using an update function in order to make them shrink. The thing that I want to ask is are you using single update or regular update? it's always better to use the latter as regular update from what I've heard has issues. Additionally, I think it would be a good idea to give those updates a little variance on time to update. Looping in a single update is ill advised even if it gives the desired result, so, why not instead prioritize such behaviour for only when the player is within a certain proximity? If they are shrink it slowly.
Next, if the puddle isn't visible, have it not update. Take the time that it stops updating so frequently, and instead just waits to see if the player is even in distance and if they aren't then it stays in hibernation.
But if the player does enter that range, take the current weather pattern, and then get how much time passed between it hibernating and now and make it progress that far.
I believe an exellent function for this is the OnUnload event which fires each time the function unloads it's 3D model (also fires during saving but that's not as much an issue honestly).
Speaking of another thing you could do is not make the thing function all the time. I'm unsure of the specifics of this sort of thing but I'm sure that in some capacity just because an actor reference is no longer in the cell it doesn't mean that it's not in memory, and that doesn't mean that no scripts are running at all on it. If the thing can no longer be manipulated (ie cell detach and not unload) then this shouldn't be running and instead should to be reloaded to do any updating and such. Mainly this part is to prevent getting errors of trying to manipulate an unloaded object. But also if it is still running at full power it prevents it from taxing the scripting engine.
Optimization isn't able reducing the fidelity, it's about increasing the performance in a way the player can't see or feel to make the best of both worlds.
tldr, if this is going to be an earnest framework I'd urge you to look into optimization in like 4 sections Super Visable (player is looking at and admiring it), Visible (The player could notice it), Invisible (Not in range to be seen yet, but still loaded), and intangible (the player will not be seeing it nor will they be near it any time soon). Splitting it up between that will improve the performance of the mod greatly.
A great tool to top all this off would be, 1 use globals. They are very useful, especially in a framework, if you'd want like regional control it'd be a god send. Second read up on states, they are super cool, MCM uses them for it's state machine and it allows you to reuse and turn off event's depending on how you set it up. Last, use properties more, having things editable from the editor is a lot better than needing a recompile on every minor numeric edit, I've learned the hard way.
I've probably failed at not coming off a bit strong but I like this sort of mod and if I could offer what I can to help I'd be glad. Sorry for the wall of text but I'd greatly recommend at least looking into the stuff directly above.
People making excuses for poor optimization, especially people who don't code, has always bothered me.
I was blissfully unaware of it until my game recently crashed on loading saves. Maybe a couple of tweaks can set this straight. I'm no scripter so sadly, I can't help.