Jump to content

All Activity

This stream auto-updates     

  1. Past hour
  2. Today
  3. Same problem when I try and run it from the Python Source package. Standalone and the installer package work fine.
  4. Yesterday
  5. I can't get the new 64-bit instructions using pipenv to work. pipenv doesn't seem to want to install any of the packages from the Pipfile:
  6. No, USSEP doesn't do anything with it. The icon not being used isn't a bug, just something they created but never assigned.
  7. That sounds logic to me. I assume USSEP already touches this, but if not I wonder if I need to update my mod. Thanks for the update, mate.
  8. null54 has updated the dds filetype plugin https://forums.getpaint.net/topic/111731-dds-filetype-plus-01-24-2020/?do=findComment&comment=567501 "Added support for saving the uncompressed X8B8G8R8 and R8G8B8 formats. Fixed a visual glitch when previewing cube maps in some formats." No doubt the next version of Paint.NET will include this update, until then you can update the plugin manually as mentioned previously in this post Edit : Can someone please pop into Nexus forums and reply to ZAZAZ000000000000000000000 post, I think this update to the plugin will solve his / her problems (unless its a simple case of PEBCAK not using "Save as" and saving the resulting files in the correct dds format <shrugs>) .. https://forums.nexusmods.com/index.php?/topic/8057638-paintnet-now-supports-all-dds-formats-including-bc7-linear-etc/ I no longer have an account on Nexus.
  9. Last week
  10. Version 3.1.7 The Spirit of the Ancient Traveler at Wayward Pass will now only appear when the player takes his skull. Castle Karstaag on Solstheim has been given its unique map marker icon that was never assigned.
  11. Version 4.2.2 of the USSEP has been released. First post has the details. Enjoy!
  12. 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.
  13. pendraggon, type "@" and a box will popup. Start typing the forum name and select the correct one with the up/down arrow keys, then press "enter" when you have the name you are trying to refer to. It helps to type 2, 3, or 4 letters of the name to narrow it down.
  14. Oooo, Ooo... I have just one question in re Post Formatting, then I’ll leave y’all alone until I get Win 10 installed. How do I go about getting the name of the person I'm responding to to appear with the '@' symbol inside a little gray box? In my past responses I've been trying to do to it in various ways to see if I could get it appear that way. I'm assuming the forum uses those little boxes to notify people there's a response or a post addressed to them.
  15. @Arthmoor @Sharlikran @Malonn @Imstearn @Malonn et al Thanks to all for defining BAIN and Wrye Bash, i.e., I went back and read the definitions in the General Readme and I saw that I was holding, in my mind, a not "totally accurate definition" of the parts of Wrye Bash. I started to realize there was an issue with my system recently as well, i.e. desktop just stated an ugly blue instead of using the picture I told it to... well various things. So I am in the process of acquiring Windows 10. It may take a week or two, but after I get installed I will again attempt to get Wrye Bash to working. And after that I am Sure I'll be back. Thanks to all for the multiple responses attempting to help me with my issues with Wrye Bash and the game.
  16. @Leeux Glad you got it sorted. That was going to be my guess as well, that pywin32 isn't working on your system for some reason, which would cause WB to think you're on Linux. Re: py3 - no, we're still on py2. Hopefully not for much longer though @bossaruu The cause is "Lexy's LOTD Consistency Patches Merged.esp". Lexy is already aware of the problem and should have a fix up at some point. If you want to manually fix it, open that mod in xEdit, find the record with FormID 3200150C (should be under Armor Addon) and delete it. @Crownless Sword King New WIP build is up. Note that the error you experienced actually happened while Wrye Bash was trying to display another error. So after downloading the new build, please make a bashbugdump: https://github.com/wrye-bash/wrye-bash/wiki/[github]-Reporting-a-bug#the-bashbugdumplog and upload it here, because you may get a different error now.
  17. Windows 10 Wrye Bash 307.202001202144 - Standalone Executable I'm trying to build a bashed patch for my game. I expected the bashed patch to work as usual. The when I click Build Patch, the elapsed time goes to 24 seconds, freezes then goes to 38 seconds freezes again then after that the elapsed time says 45 seconds and it appears to be working, but the bar goes green to about 1% then closes immediately leaving the bashed patch, 0.esp empty. I get no error message I dont see a Bashed Patch config. Active Mod Files: === Current Bash Tags:
  18. Hello all, EDIT3: Nevermind, sorry... I jumped the gun with the report. It seems that the pip --upgrade process broke my pywin32 installation. It was failing to import win32api. I had to redo the pip install -U pywin32 and that made Bash work again. I would strike through the text in my post only if this editor would let me, it seems it doesn't want to let me. Also I can't for the life of me sorround the code with a spoiler tag that wouldnt eat all the text until the end of the post... not sure what I'm doing wrong, but.... oh well, sorry for the clutter! /EDIT3 -------- I'm using the Python version in SkyrimSE, and I just updated to head of the 'dev' branch using GIT, and after a bit of messing around I managed to make Bash run after updating my dependencies according to the requirements.txt. After the update was done and working, the only issue I had that I lost my Apps status bar icons... I have dozens of tools for which I made shortcuts under Mopy/Apps folder that before updating Bash used to pick them up and show them in the status bar, but now they aren't there anymore. In my attempts to see what's was going on, I toggled the Show App Version option to True, and that seems to have been a mistake... because that's when the crashes started. This is what dumps: Traceback (most recent call last): File "bash\bash.py", line 205, in main _main(opts, wx_locale) File "bash\bash.py", line 368, in _main app.Init() # Link.Frame is set here ! File "bash\basher\__init__.py", line 4073, in Init frame = BashFrame() # Link.Frame global set here File "bash\basher\__init__.py", line 3726, in __init__ self.SetStatusBar(BashStatusBar(self)) File "bash\balt.py", line 2864, in __init__ self.UpdateIconSizes() File "bash\basher\__init__.py", line 3611, in UpdateIconSizes self._addButton(link) File "bash\balt.py", line 2879, in _addButton gButton = link.GetBitmapButton(self) File "bash\basher\app_buttons.py", line 567, in GetBitmapButton onRClick) File "bash\basher\app_buttons.py", line 88, in GetBitmapButton tooltip=self.sb_button_tip) File "bash\basher\app_buttons.py", line 591, in sb_button_tip self.button_state]) % (bush.game.se.se_abbrev, self.obseVersion) File "bash\basher\app_buttons.py", line 112, in obseVersion in ver_path.strippedVersion]) File "bash\bolt.py", line 607, in strippedVersion version = list(self.version) File "bash\bolt.py", line 602, in version return get_file_version(self._s) File "bash\env.py", line 353, in get_file_version return _linux_get_file_version_info(filename) File "bash\env.py", line 486, in _linux_get_file_version_info offset=section_resources_pos + 12) File "bash\env.py", line 435, in _read file_obj.seek(offset, not absolute) IOError: [Errno 22] Invalid argument I also tried switching to the nightly branch to see if that would solve the problem, but it persisted. Of course, after upgrading and switching I always delete all PYC files from bash directory, just in case. My bash.ini is kept up to date with the download (I use WinMerge to compare it with the bash_default.ini to see if there was an important change, and I didn't noticed any.) Now I don't know what to do, I don't want to lose my config as the option I toggled seem to be embedded in the config and it'd seem that the only option would be to reset it to be able to launch bash again. EDIT2: I was trying to add to my post that I'm not entirely sure why is using "_linux_get_file_version_info" as this is running on Windows 7 64 bits, under Python 2.7 x86. Should I have updated Python too? I didn't saw any mention of Python 3.x support, but I could be blind. I have to go to bed now, but I'll try to fiddle a bit more tomorrow after work. Best regards, Leandro. EDIT: I couldn't edit the spoiler block at all, didn't find any way to use a "normal" non-wysywyg editor, so I had to redo my post again
  19. @bossaruu Thanks, it happened because your file was encoded in UTF-16 but the Python paser we used for the INI was expecting ASCII. I'll see about adding proper encoding detection to avoid that in the future. @Crownless Sword King Thanks, I found the mistake. Will push a WIP build that fixes it tomorrow.
  20. @Infernio I installed the WIP build and got what looks like the same error again. Traceback (most recent call last): File "bash\bash.pyo", line 206, in main File "bash\bash.pyo", line 369, in _main File "bash\basher\__init__.pyo", line 4068, in Init File "bash\basher\__init__.pyo", line 4106, in InitData File "bash\bosh\__init__.pyo", line 1957, in refresh File "bash\bosh\__init__.pyo", line 1363, in refresh File "bash\bosh\__init__.pyo", line 2162, in new_info File "bash\bosh\__init__.pyo", line 1339, in new_info File "bash\bosh\__init__.pyo", line 1258, in new_info File "bash\bosh\__init__.pyo", line 412, in __init__ File "bash\bosh\__init__.pyo", line 221, in __init__ File "bash\bosh\__init__.pyo", line 118, in __init__ File "bash\bosh\__init__.pyo", line 415, in _reset_cache File "bash\bosh\__init__.pyo", line 233, in _reset_cache File "bash\bosh\__init__.pyo", line 610, in readHeader File "bash\brec.pyo", line 2557, in __init__ File "bash\brec.pyo", line 1813, in initRecord File "bash\brec.pyo", line 2348, in __init__ File "bash\brec.pyo", line 2412, in load File "bash\brec.pyo", line 2566, in loadData File "bash\brec.pyo", line 1839, in loadData File "bash\brec.pyo", line 1847, in _handle_load_error TypeError: not enough arguments for format string
  21. @Infernio what the fuck. since you said that it could be my ini file, i just tried to remake the skyrim.ini in my skyrim directory and it seems to be working now. i'll add a copy of the file here anyways incase you need it for development purposes. Skyrim.ini
  22. @bossaruu That looks perfectly fine, so it must be the encoding of your INI that's causing hiccups. Could you upload the file itself to some hosting service? Mega or Mediafire or whatever. @Crownless Sword King Are you using the latest WIP build? If not, try again with that one (see second post in this thread for the link) and if it still fails, post the new traceback.
  23. I got a error for on Skyrim SE Wrye Bash and I wanted to know if someone could help. This is the error I get on startup: Traceback (most recent call last): File "bash\bash.pyo", line 206, in main File "bash\bash.pyo", line 369, in _main File "bash\basher\__init__.pyo", line 4075, in Init File "bash\basher\__init__.pyo", line 4113, in InitData File "bash\bosh\__init__.pyo", line 1927, in refresh File "bash\bosh\__init__.pyo", line 1337, in refresh File "bash\bosh\__init__.pyo", line 2129, in new_info File "bash\bosh\__init__.pyo", line 1313, in new_info File "bash\bosh\__init__.pyo", line 1232, in new_info File "bash\bosh\__init__.pyo", line 410, in __init__ File "bash\bosh\__init__.pyo", line 219, in __init__ File "bash\bosh\__init__.pyo", line 116, in __init__ File "bash\bosh\__init__.pyo", line 413, in _reset_cache File "bash\bosh\__init__.pyo", line 231, in _reset_cache File "bash\bosh\__init__.pyo", line 608, in readHeader File "bash\brec.pyo", line 2551, in __init__ File "bash\brec.pyo", line 1807, in initRecord File "bash\brec.pyo", line 2342, in __init__ File "bash\brec.pyo", line 2406, in load File "bash\brec.pyo", line 2560, in loadData File "bash\brec.pyo", line 1833, in loadData File "bash\brec.pyo", line 1841, in _handle_load_error TypeError: not enough arguments for format string
  24. https://pastebin.com/cDpyJzjX @Infernio here it is
  25. @bossaruu Please upload the contents of your file to something like pastebin or gist and link it here.
  26. apparently I wasn't on the newest version, since I got the files off the SSE nexus and it's working now! thank you!!
  1. Load more activity

Support us on Patreon!

Patreon
×
×
  • Create New...