Jump to content


  • Content Count

  • Joined

  • Last visited

About Infernio

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @Vythical First, try launching the game through Steam and, if that doesn't help, verifying the game files through Steam. If it still happens even after that, please make a bashbugdump: https://github.com/wrye-bash/wrye-bash/wiki/[github]-Reporting-a-bug#the-bashbugdumplog and upload it here
  2. @dipsauce13 This is caused by OneDrive. Please follow the directions found in the following link under Change PC folder backup settings, removing your Documents folder from backup: https://support.microsoft.com/en-us/office/back-up-your-documents-pictures-and-desktop-folders-with-onedrive-d61a7930-a6fb-4b95-b28a-6552e77c3057
  3. Re: the dots, those are just there to visually 'organize' tags together. E.g. all tags that target NPCs use either Actors. or NPC. as their prefix: Actors.ACBS, Actors.AIPackages, NPC.Class, etc.
  4. Wrye Bash can patch a lot more than just leveled lists for later games. The only game where it is still limited to that is Fallout 4. Relevant issues: - Porting status of patchers for FO3/FNV: https://github.com/wrye-bash/wrye-bash/issues/468 - Porting status of patchers for Skyrim: https://github.com/wrye-bash/wrye-bash/issues/151 - Porting status of patchers for FO4: https://github.com/wrye-bash/wrye-bash/issues/482 xEdit's merged patch is deprecated and should not be used anymore. It was created around the time when FO3/FNV were released, and no Wrye Bash existed for them
  5. @Beermotor In case you see it here - could you give us explicit permission to redistribute your BAIN wizards from this thread for CI/testing the new parser? Best to do it in a post on this thread so that we can archive and link it.
  6. @Ruffled Try the WIP build (link is in the second post in this thread).
  7. Morrowind support for mainline WB is mainly about code quality. Supporting MW is yet another step to making the code more game-agnostic and more maintainable in the long run. If we end up supplanting Wrye Mash in the process, that's fine too. It took a long time for us to equal valda's version for FO3/FNV as well (and we're still not quite there yet, since we're lacking the race patcher). We'll get there.
  8. Try running the SSE launcher through Steam once. Wrye Bash needs up-to-date registry keys to detect your games, and Bethesda games only generate them when you run the regular launcher (i.e. not SKSE/OBSE/etc.) through Steam.
  9. @Zea.M By using the WIP build from the second post in this thread.
  10. The only things that are silently skipped with no way to change it are executables (DLLs and EXEs), except for xSE (SKSE, OBSE, etc.) plugins. This is by design, for security reasons. I've submitted an issue a while ago because I personally don't think this argument holds much water: https://github.com/wrye-bash/wrye-bash/issues/501 But people feel strongly on this, and without some sort of consensus from the rest of the team I can't just make a change like that.
  11. I wouldn't say we're interested in having two different GUI backends, just that it's possible GUI refactoring could eventually make such an API possible. Honestly? I'm not sure. You would have to reimplement all GUI components we use right now, which is no problem for e.g. dialogs, but I can imagine that UIList (the class we use to display the mods/saves/installers/etc. files on the left side of each tab) would be much harder to implement. I'm not sure how much I can quantify a subjective feeling, I just think Tkinter looks much uglier than wxPython
  12. We wouldn't accept a patch to remove it (because Tkinter looks way worse than wxPython), but we might work towards allowing multiple GUI backends. If we do that, then you could implement a Tkinter backend (and we'd probably accept the patch).
  13. I've gone ahead and increased the contrast on several checkbox images in 307.202006121256 that were failing WCAG AAA or even WCAG AA.
  14. @Synel00 That error is caused by an invalid BSA file you have somewhere. Try again with the latest WIP version (link is in the second post in this thread) and make another BashBugDump, which will tell you what BSA file is affected.
  15. Yeah, the online advanced readme doesn't get updated very often. I've gone ahead and synced it again, but the only guaranteed up-to-date docs are the ones that come with the Wrye Bash download. Regarding your error: are you on the nightly branch? That branch needs a 64 bit python, while the dev branch is still on 32 bit.
  • Create New...