Jump to content

Infernio

Members
  • Content Count

    53
  • 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. @Arthmoor I'll have a look, seems like the RACE definition for Oblivion broke. @lmstearn Should already be fixed in nightly.
  2. Actually @PoptartJuniper, could you try again with the latest nightly (307.202005131856)? I think it might have been due to you having 'Has Extra Directories' enabled on that file, which wasn't working correctly with some FOMODs.
  3. I'm working on a Bachelor's degree in CS, but I learned Python as a random aside for hobbies.
  4. The message is telling you exactly what's wrong: CBash ran out of memory. The WIP build is 64bit, so that may help, but if that doesn't fix it you'll have to stick to PBash.
  5. @PoptartJuniper I can't replicate that. Using CBBE 1.5.6's FOMOD with default options plus selecting one of the eyebrow options, it installed them correctly into the Data folder: @Skinwalker I've forwarded the issue to Utumno, who refactored the code that's erroring there. However, the issue seems to be caused by a plugin file with an unknown header signature, which should not be possible - so you may have a corrupt file on disk. @YoJeff328 We disabled it because it hasn't worked for years now (always hard-crashes Wrye Bash when you try) and there doesn't seem to be a way to fix it in the GUI framework we're using. Some people claim it worked in an earlier version, but we haven't actually found one where it does.
  6. @NorthMammoth Could you repeat your test with the latest WIP version (link is in the second post of this thread)? Probably won't solve the problem, but will make the traceback more useful.
  7. @Cecell Thanks, fixed in the latest nightly.
  8. CBash already runs on 64bit . The C++ code only needed one line changed, while cint had a whole bunch of places where it was passing 32-bit integers as pointers - which obviously broke on 64bit. Ganda did all that, so you should be able to use Oblivion with CBash in the latest WIP builds.
  9. @Leeux Hey Addressing your points: 1. A search bar for each tab is on my (long) TODO list. Prerequisites are at least de-wx'ing, python 3 and BAIN refactoring. Opened an issue for it so it doesn't get forgotten though: https://github.com/wrye-bash/wrye-bash/issues/490 2. Rethinking the different game installations will be part of https://github.com/wrye-bash/wrye-bash/issues/250 3. The 'Groups' feature will most likely be merged with the 'Ratings' feature, at which point we can consider generalizing it and extending it to all tabs: https://github.com/wrye-bash/wrye-bash/issues/484 4. Collapsible markers are still on the TODO list, but 308+: https://github.com/wrye-bash/wrye-bash/issues/267 5. 'Date Installed' could be done as part of https://github.com/wrye-bash/wrye-bash/issues/30 6. Rethinking Nexus integration is on the TODO list, but 308+: https://github.com/wrye-bash/wrye-bash/issues/459 7. Currently, no one is maintaining CBash. The eventual plan is to slowly rewrite it in Rust once we're on python 3: https://github.com/GandaG/rbash/ I also pinged Utumno since I normally respond to most people who post here, so he might show up at some point
  10. @kaliban71 Wrye Bash is not misreporting the order of the mods in your save, Bethesda simply screwed up and is storing mods as two seperate lists, non-ESL mods first and ESL mods afterwards. That is exactly what WB is showing you on the Saves tab. If you want an accurate representation of the masters of your save, install SKSE64/F4SE - those will create cosaves that contain the correct, interleaved master list. When those cosaves are present, WB will show the correct order, but if they aren't, it's literally impossible to show the correct order, so we just show what the save gives us. Regarding the ESL flagging: it's not done automatically. You will have to right click each green mod you want ESL-flagged, and click 'Add ESL Flag'. That's because ESL-flagging should be a deliberate choice, not an automatic thing.
  11. @Fiery Grab the WIP build (link is in the second post of this thread), should be fixed in there.
  12. Here's a quick BCF for SSE's XP32 I made for myself. Only supports RaceMenu cause I couldn't be bothered to make subpackages for all the MCM/RaceMenu/ECE options: XP32 Maximum Skeleton Special Extended - BAIN Compatible-1988-4-71-1577467636-BCF.7z Use with v4.71. No wizard right now, and all subpackages (except 00 Core) are optional.
  13. @Gemma_Kat Try the latest WIP build (see second post in this thread for the link), that's a bug in the Nexus version that is fixed in the WIP build. Wrye Bash supports all three types of save compression (LZ4, zlib, uncompressed).
  14. @Verayth @Arthmoor pipenv through powershell seems to crash (at least for me), try using Git Bash to run the commands instead.
  15. Important info for everyone using the source download or a git clone of the nightly branch: Wrye Bash is now 64bit, so make sure to grab a 64bit version of Python 2 and all our dependencies. And speaking of dependencies: our method of installing them has changed. Please see the Readme.md for information on the new process. For everyone else: Wrye Bash no longer supports 32-bit operating systems. The newest WIP build will not run if you have such a system. This is unlikely to affect a significant number of people, and it's simply not something we can support any longer.

Support us on Patreon!

Patreon
×
×
  • Create New...