Jump to content

Infernio

Members
  • Posts

    153
  • Joined

  • Last visited

Recent Profile Visitors

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

Infernio's Achievements

Brother

Brother (3/10)

26

Reputation

  1. Well, Wrye Bash dates back to 2006, when it was created as a fork of Wrye Mash. Wrye Mash itself dates back to at least January of 2005 (Wrye didn't keep docs until version 0.24, which was released on the 15th of January 2005). The GUI situation in Python probably looked quite different back then - Qt was on version 3.3 and Python on version 2.4 and I have no idea what the integration between those two was like back then.
  2. Switching to Qt wouldn't gain us much - skins, maybe. wxWidgets actually has an experimental Qt backend (https://wiki.wxwidgets.org/WxQt), so one day we could maybe even take advantage of that.
  3. @Arthmoor Should be fixed in 311.202209221513.
  4. @zomghax92 Is that from a run where you reproduced the issue, i.e. the Installers tab went from working to non-working? If not, please reproduce that and then upload a BashBugDump of that run.
  5. @ansomesa @Pseron Wyrd I've added a Skyrim equivalent of that tweak to the newest WIP build (311.202208231119, second post in this thread). Please try that build and let me know if it works (the custom choice for that tweak is a bit arcane, see the Advanced Readme if you need help).
  6. @zomghax92 Please try the WIP build (second post in this thread) and upload your BashBugDump.log if it still happens.
  7. @ssuamier That is the only remaining limitation of FOMOD support in WB: BAIN must need to recognize at least *something* in the package for it to be installable - but it will take a lot of refactoring work to get BAIN to that point wrt. FOMODs. Until that happens, there is a workaround: you can "trick" BAIN into thinking there's something installable in there. To do that: 1. Unpack the package (Archive.. > Unpack to Project) 2. Create a dummy ESP (on the Mods tab, Files.. > New Plugin..., call it e.g. "dummy.esp") 3. Create a dummy subpackage in the unpacked archive (on the same level as the "fomod" folder, again call it e.g. "dummy") 4. Put the dummy ESP into the new dummy subpackage 5. BAIN should now recognize the project. Repack it into an archive (Project.. > Pack to Archive). Done The final layout should look like this (contents of the other folders elided due to length): Fixed Mesh Lighting |- dummy | |- dummy.esp |- FML - Core | |- ... |- FML - Creatures - Mods | |- ... |- ... BAIN can now recognize it. And since the FOMOD installer doesn't mention the dummy subpackage, it will get skipped entirely once you run the FOMOD installer.
  8. @Odin70 Make sure you're using the latest version (310.beta1 or the nightly builds) and create a bashbugdump: https://github.com/wrye-bash/wrye-bash/wiki/[github]-Reporting-a-bug#the-bashbugdumplog @Malonn Right now there are two active maintainers, Utumno and I: https://wrye-bash.github.io/docs/Wrye Bash General Readme.html#credits
  9. For future reference (e.g. visitors from Google), Irwine's problem is solved since 310.202205261528 by adding the Text tag.
  10. @XJDHDR Doesn't exist yet, I can discuss it with Utumno.
  11. @Irwine First off, try removing the Filter tag. That tag is only needed if you want to create a plugin for distribution to other players that can target several different masters and be imported into a BP even if some of those masters are missing. If what you're looking for is a tag that deactivates the plugin when the BP is built but still imports data, use the Deactivate tag. If that still doesn't fix it, then please upload the plugin in question so we can take a look at it.
  12. If you mean this blue color: Then we can't change that programmatically since it's provided by the native win32 control (okay, one technically could change it by diving into the native Windows APIs, but that makes the code Windows-only and is insanely complicated).
  13. Which is why Utumno said nightly code Pushed a new version (310.202202261802) to dropbox that contains the fix.
  14. @4nk8r Did you enable the columns? Right click the column header, then enable them under 'Columns..'. Should look something like this:
  15. Please try this build and report back if the new column works as expected (I'm on Linux right now so had to implement this more or less blindly): https://github.com/wrye-bash/wrye-bash/suites/5371821797/artifacts/168558595
×
×
  • Create New...