Jump to content

Infernio

Members
  • Content Count

    70
  • Joined

  • Last visited

About Infernio

  • Rank
    Hearthfriend

Recent Profile Visitors

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

  1. @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.
  2. @Ruffled Try the WIP build (link is in the second post in this thread).
  3. 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.
  4. 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.
  5. @Zea.M By using the WIP build from the second post in this thread.
  6. 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.
  7. 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
  8. 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).
  9. I've gone ahead and increased the contrast on several checkbox images in 307.202006121256 that were failing WCAG AAA or even WCAG AA.
  10. @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.
  11. 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.
  12. They're not all used for the same thing, e.g. masters use purple, blue, green, orange and red, while mods only use green, yellow, orange and red (with increasing severity of the problem in that order). Also, the status bar at the bottom will tell you what any of the 'problematic' colors (i.e. yellow, orange and red) mean (except on the Installers tab, where we don't have that yet).
  13. imp = imported into the Bashed Patch (i.e. a plugin is deactivated, but some of its data has been imported) inc = merged (stands for 'included' I guess?) into the Bashed Patch off = inactive plugin, uninstalled package, etc. on = active plugin, installed package, etc. The _wiz variations are for packages with BAIN wizards. Also, if you do change these, make sure to keep copies of the altered images in a safe place. The WB download includes the original versions, so if you use the installer or just unzip and overwrite, that would overwrite your changed files again.
  14. @sombrero Yeah, the colors might not be great for visually impaired people - right now they're just images we display, so you *could* open them with an image editor (they're in Mopy/bash/images, look for checkbox_*.png) and change the colors yourself. Hopefully we'll be able to draw them via code in the future, which would mean you could just configure their colors via the Colors dialog. Edit: opened an issue so it doesn't get forgotten: https://github.com/wrye-bash/wrye-bash/issues/511 @gurglegurgle You're using wxPython 3, but we're already on wxPython 4. You can also just run pip install -r requirements.txt while in the WB folder that has the requirements.txt file. That should install the right versions of everything you need.
  15. 1: I mean the 'File' menu at the top. Only available in the latest nightly build (second post here), in older builds you have to right click the columns. 2: BAIN already does this. It checks if all files are installed and match the package, that's what the colored checkboxes to the left of each package mean. Green=OK, Yellow=Conflict loser for non-plugin files, Orange=Conflict Loser with one or more plugin files (.esp, .esm, etc.), Red=one or more missing files. If you suspect that BAIN somehow missed a refresh, you can right click the package and choose 'Quick Refresh' to force a recheck of all files in that package (or right click the columns and choose 'Full Refresh' to do it for all your BAIN packages). Edit: And zip integrity should be checked automatically by 7zip, BAIN directly calls 7zip.exe for all its extraction/listing/compressing needs.

Support us on Patreon!

Patreon
×
×
  • Create New...