Jump to content


  • Posts

  • Joined

  • Last visited

Posts posted by DayDreamer

  1. Thought I'd add my recent experimenting on baked-in scripts. Scripts that are fragments for packages never go away, and seem to begin executing on a None package with no conditions. Or something. It made no sense.


    I had 5 quests. I made 5 new quests. I made new quest-specific packages for the new quests, and removed the packages on the old quests (leaving the old quests in place to fulfill the existing pointers to them).


    Boom! The OnEnd fragments for the old packages! What are they ending??? They aren't running!!!


    Solution: Keep the old packages, and re-purposed them to the new quests with revised scripts with exactly the same names. Delete the 5 old quests entirely.


    This leaves dangling pointers to the old quests. Fooey....


    Solution: used TES5Edit to renumber the 5 old quests to the 5 new quests, with the packages still in place.


    That re-filled all the old pointers with new values, but the old pointers were baked into the savefile.


    Solution: used TES5Edit to renumber all objects that had dangling pointers. They went away with no objections! No script logs! :banana:


    There were still 5 vanilla objects that I'd filled with a single property script with single pointers to the old quests. Used OnPlayerLoadGame() in each new quest to replace those with Self.


    Caveat: I have no idea whether the dozens of old objects that were renumbered are still in the savefiles (probably not), or their old scripts with baked values are still there on a [None] object (possibly). As long as they don't run and don't complain, I'm OK with that!


    Nota Bene: This probably only worked because I'd designed everything from the get-go to be removable. And in the beginning, you could remove it and there were no complaints. Everything was a dynamically allocated object. That's no longer true -- all the static local carts folks asked me to add. It was those static carts that were renumbered.

  2. Check your log: before the first "VM is thawing" message (i.e. before you actually enter the game), there will be a "saving" message. That's when it happens.

    i'm not seeing that. I have only:


    VM is freezing...
    VM is frozen
    Reverting game...
    Loading game...
    VM is thawing...

    EDIT: But I have auto-saves turned off for every option. Auto-saves were my biggest source of crashes.

  3. More objects for touring carriages to flatten ...

    lol, I bet that's not even been considered since everyone just thinks it's normal for the wildlife to thin out so much :P

    The die off has been reported for a long time. Between that and the flora problem, Skyrim gets barren pretty fast.


    TC version 2 also widens the push area some more (another +25 to the radius). The old value was the width of the cart, the new one is about a sheep wider. Since I cut Scenic's push 9 to 5, I've not even been killing chickens!


    The real problem now is guards; they turn and walk toward you to talk, and get stuck in between the driver and the wheels. But there's no "farthest" actor function, there's only "closest" -- and the driver himself is obviously closer. Oh well, they almost never actually die.


    Speaking of chickens, it's amazing to hear the clucking as you drive by now! The smallest things....  Good work!

  4. Yeah, no, we're not going back to Bugzilla. If you guys think the UI for Tracdown is bad, Bugzilla is hideous.

    Actually, I had no problems as a Bugzilla user. For one thing, the search and categories worked pretty well. Dunno how it was to administer.


    Man-o-manischewitz, I've not found the search here useful. And not possible across categories at all.


    And I hate the status on the lower right. In Firefox, it's very hard to read or scroll.


    One nice thing about Bugzilla was everything was a message. Status changes, comments, all nice and simple text. None of this scrolley boxes within boxes UI.

  5. I had no problems hand sorting with NMM. The standard launcher then accepted that load order, no problems, and check my 4 steam mods. Then I launched SKSE+SkyUI, also with no problems.


    I don't yet run with enough mods to bother with BOSS, although I downloaded it today.


    There are still some log errors I expected to go away. But I see there was another UDGP.


    Is there anything special we need to do to load these in CK? I've not tried yet, but I always do any navmeshing with USKP loaded above it, to avoid any conflicts there.

  6. That alone is enough to foul things up on that save. Nothing you're doing to it at this point is going to correct it. You'll either have to live with what you have or start over with a new save. Papyrus does not forgive the removal and reapplication of a mod, no matter the conditions.

    Please explain. For Touring Carriages, I'd hoped that folks could remove it and re-add it later. Heck, it was a design goal from the get-go.


    I used all new form numbers for every object, essentially layering them on the existing base forms. That is, the horses are new forms, but they have an existing form (HorseForCarrriageTemplate) as a base. I'm having to change the underlying form to pick up your new UDGP 2.0 factions, that you put in HorseForCarriageNew -- so I have to use that too. Thus, this is of immediate concern to me....


    Anyway, everything disappears after removing the mod. Doesn't that include scripts attached to the objects that disappeared?

  7. To complete this, I also did upload a version 2.4e two days ago, which has the correct script in it as well. There's otherwise nothing new in that version; I just removed a few lines of code from both scripts that had become superfluous.


    i thin it was a bit confusing with the versions in the end. 2.5 is this in the 1.3.3 release now?


    2.4e is what should go into the patch now, and it will fix the issue?  i would give it a quick look, but i can not download it.

    good thing is: with the DDoS on the Nexus, bug reports and downloads have been relativelly low still. :-D

    He's not clear. I think the final version belongs in 1.3.3 -- that is, 2.5.

  8. So what happens when i do this, does it Delete the Actual Mod or something.

    It backs them up. You have such a long load order, it's going to take awhile. And you are going to have to do it again in a week starting with the new Update.

  9. Although this won't be complete, here's a quick hand comparison of explicitly mentoned matching fixes:

    • Gallus's Encoded Journal
    • No Stone Unturned
    • Ebony Blade
    • Proudspire Manor key
    • Nord Hero Bow (68C57)
    • Purity (Alchemy) perk
    • Japhet's Folly
    • Gharol (Burguk's Longhouse)
    • Matching Set
    • Ancient Knowledge
    • courier (Bug #179)
  10. I asked over on the BS forum, heard nothing, am asking here. What do you need us to look at/test for this beta?


    I understand we cannot yet look at Source, so it will just be the patches themselves. Please make a list of things to check, and I'm sure we can divide the work up.

  • Create New...