Jump to content

Beermotor

Members
  • Content count

    273
  • Joined

  • Last visited

About Beermotor

  • Rank
    Initiate

Recent Profile Visitors

309 profile views
  1. Wrye Bash - All Games

    It would appear some of this kind of parsing (or at least detection) is already happening. If you have an unconverted form v43 mod loaded you get this exception when building your Bashed Patch: The mod used for testing was Creatures House.
  2. Wrye Bash - All Games

    Does proper version parsing occur for Skyrim LE and Fallout 4 currently in the 307 builds?
  3. Wrye Bash Issue

    That's great news. If this happens again please give a shout though. That's certainly unusual.
  4. Wrye Bash - All Games

    That's referring to the Form Version in the TES4 header of the plugin. Skyrim LE was 43, Skyrim SE is 44. Currently the Bashed Patch shows form version 0 for SSE, LE, and FO4 that I know of. Skyrim 2011: Skyrim SE: Fallout 4: Oblivion: So I got a wild hair and grabbed a copy of WB 305 from GitHub, deleted my existing Skyrim LE Bashed Patch and allowed it to make a new one: So it has been 0 since at least 2014. I believe the form version was discovered when users started running this script in xEdit named "Check for old form versions.pas": So notice that const there that checks for form version 44, well basically it checks for 44 and if anything is lower it simply prints "Old version plugin: 'GetFileName(plugin)' " To test the logic of the script, I changed this to: const CheckFormVersion = 45; Then ran it against my SSE mods: So as for why there is concern over form 43: As Arthmoor mentions, based on evidence that has borne out since SSE's release, there are issues that older v43 plugins can cause with SSE. This isn't always apparent immediately but can manifest later in stability or save game consistency issues. The fix is easy (resave the plugin in the CK) but there have been lots of mods on the Nexus that have not been properly converted and lead to all kinds of wailing and gnashing of teeth. I'm sure @zilav or @Arthmoor can give a much better technical explanation of the potential issues so if this data is wrong in any way I'm sure they will correct me.
  5. Wrye Bash - All Games

    Is it actually v43 or is it v0 or NULL? Mine is showing as 0/NULL in xEdit.
  6. Wrye Bash Issue

    Welcome Cain. I'm sorry to hear you're having problems getting Wrye Bash to start. Just out of curiosity are you running the Python version or the Stand Alone version? It looks like the Python version in the bug dump but I want to make sure. Could you share any other info on your rig and setup? Also if you want you might try one of the newer builds from the second post in the main WB thread. Follow the "307 WIP Standalone" link if you want to get a copy of the standalone executable or an installer version.
  7. Wrye Bash - All Games

    I'm on the Python version. Now that I read this I'm wondering if I missed deleting something somewhere. I'll give it a test with regular Skyrim since it sounds like I got an unexpected result. EDIT: I'm tired from being up since 3:00AM and misread that. Derp. Disregard, mine is working fine.
  8. Wrye Bash - All Games

    This also in reply to the post above. In my case when I did a restore on Oblivion last night, after the restore my packages were back in their installed state as they were prior to the test. Most of these were simple BAIN packages save for Open Cities Reborn and maybe a couple of others. Regarding the CTD and losing your work, while crashes are becoming exceedingly rare in my experience, it seems as if WB is only saving changes when the app exits normally. Is there supposed to be a periodic/triggered/timed background config save that happens during operation?
  9. Wrye Bash - All Games

    10-4. I'll play some Oblivion tonight to churn up some data for snapshots then leave it all in-situ until the next build/iteration.
  10. Wrye Bash - All Games

    First test I performed was settings restoration. Test steps: Launched WB 307.201609160706 Gear icon -> Backup Saved as custom name. File saved to '\Oblivion Mods\Bash Mod Data\' Closed WB Went to my 'user profile\my games\oblivion\' and removed all of the WB dat files. Removed the dat files from all over 'oblivion mods'. Launched WB. Window position was forgotten. Window size as well. Gear icon -> Restored from backup Relaunched WB Other than receiving the Installer Tab confirmation again, everything was in place. OBSE stats: Right clicked a new save and selected ".obse Statistics". Window popped up with the following information: Note that this ^ is a brand new game with no quests completed or anything. I used Arthmoor's Alt Start patch and walked outside my house in Skingrad and down to the bridge. If I need to gather more data I can.
  11. In addition to what Arthmoor said, what I do is this when I export facegen. I'm presuming you use Wrye Bash. With WB running, go to the Installers tab and right click at the top of any header and enable "Monitor External Installation". Then go to the CK, do what you need to do, then export your FaceGen. When you are done with the CK, go back to Wrye Bash and click OK to end the monitoring. You will be presented with a list of all of the files that were exported by the CK during that session. Then you can go through to verify all of the facegen data.
  12. Wrye Bash - All Games

    So this is a thing: Highlights: EDIT was pointing users to the Bleeding Edge branch - it has been updated to point to this thread.
  13. Wrye Bash - All Games

    In my post earlier I was referring to Skyrim SE because I misunderstood the problem and though it may have been an issue with SSE as well. Regarding Oblivion, if you can back things up, try it with a clean slate and see what happens. If it goes to hell in a hand basket you have your backed up metadata to fall back on.
  14. Wrye Bash - All Games

    I was on call this weekend with work so I wasn't able to do much objective testing, but I did get to test the plugins.txt thing. Backstory: I hoped to avoid it, but I was working on an installer for a terribly constructed mod and needed to take a look at the FOMOD installer. I begrudgingly installed NMM (isolated as much as possible) and ran through the installer. Well as soon as I was finished I closed NMM and went back to WB. Of course NMM completely dicked up my plugins.txt. So I kept trying to get things to sort, fought with it for a good 5 min before I looked down at the task bar and saw a lone NMM error message window protesting about something completely insignificant. This one little error window was keeping NMM open with a lock on plugins.txt. NMM didn't show up in Task Manager but it kept showing up, like a bread turd that won't flush. Once NMM was completely killed off everything returned to normal and sorting proceeded as expected.
  15. Wrye Bash - All Games

    I'm running the Python WIP (not from Dropbox) from 6:45ishPM on 16 Sept and it is showing the version as 307.201709160706. I nuked all of my saves because I'd polluted them with foolishness, so I'm about to reroll a new character to test several things.

Support us on Patreon!

×