[Dominic Vaughan]

There is sometimes an extra step necessary for Vista and Win7 users to get Bash to run: http://tesivpositive.animolious.com/index.php?page=wrye_bash#Config <-- see step #5

Ok I see it, thanks a lot.

[Sun of Sammy]

I had the latest Wrye Bash and the previous Wrye Python, and everything worked fine. Now I installed the latest Wrye Python, and when I click Wrye Bash, nothing happens.

[zoe]

I had the latest Wrye Bash and the previous Wrye Python, and everything worked fine. Now I installed the latest Wrye Python, and when I click Wrye Bash, nothing happens.

What operating system are you running? What steps did you take to upgrade the install? Try creating a new shortcut to the PYW file.

[Rob Smith]

krabman7, try reinstalling Bash again. If that doesn't work, I'll need a bug dump to see what's going on (see Wrye Bash.html for instructions).

Arkngt, I'm not too sure how easy/hard that will be to do. Will keep it in mind.

Ninlil, there are already larger icons available by editing the ini file. Copy bash_default.ini, and rename the copy to bash.ini. Open it, and look for iIconSize=16. Change it to iIconSize=32 for larger icons. The ini file isn't well documented in Wrye Bash.html, but the file itself is very self explanatory.

Arthmoor, yes to the first question, and no to the last. Also, if you're using CBash or the latest SVN, the bug won't be triggered.

Spotty42, I'm honestly not sure. I don't use the exhaustion feature myself, so I don't know exactly how it works. You may try asking in the Cobl thread since it is the mod that actually implements the Exhaustion feature...Bash basically just makes Cobl aware of the spells.

[Logan Greenwood]

I had the latest Wrye Bash and the previous Wrye Python, and everything worked fine. Now I installed the latest Wrye Python, and when I click Wrye Bash, nothing happens.

Try reinstalling by the instructions I linked earlier. You will not lose any data by reinstalling Bash.

[oliver klosoff]

Arthmoor, yes to the first question, and no to the last. Also, if you're using CBash or the latest SVN, the bug won't be triggered.

Well that's what I'm getting at. I have several mods using the graphics patcher and I'm using 285 and don't see this issue with Aspen Wood, and at least one other person said the same. I guess it doesn't matter now that it's been fixed but I don't like having unsolved mysteries where code is concerned

[Adam Baumgartner]

I suppose I simplified my explanations a little too much. It isn't really a mystery, it's just complicated to explain and highly dependent on a lot of factors including python version, load order, patch order, etc. I spent about 40 minutes trying to replicate it on my end and nearly gave up before I found the right combination of circumstances that triggered it.

I could go into more detail, but it's fixed and I'd rather spend my time getting 286 out the door.

[El Khatiri]

What operating system are you running? What steps did you take to upgrade the install? Try creating a new shortcut to the PYW file.

I'm on Windows 7, and to upgrade I just downloaded the python from here: http://www.tesnexus.com/downloads/file.php?id=22368

A friend of mine just installed Bash and Python for the first time, and he has the same problem. He runs on Windows Vista.

I tried generating the bug dump, following all the instruction steps, but all it does is actually LAUNCH wrye bash. I can launch it that way but I still have no idea why it doesn't work normally.

[QuinDINGDONGcey]

Also a request: it would be nice to have a Cancel button for the Installers tab. I tend to "automatically" click on it sometimes and as it takes several minutes to open, it would be nice to be able to cancel the process if clicked inadvertently.

You sort of can, I think, by closing Bash via right-clicking close on bottom tool bar. Then just open Bash again. It's what I do (sometimes I've done it whilst its rebuilding the patch and I realise I forgot something and don't want to wait 10 mins for build to finish then redo it after again...) Doesn't seem to do any harm

[Sherry Speakman]

Vista and Win7 64-bit have the same issues. Try reinstalling it following these instructions - http://www.gamesas.com/index.php?/topic/1102179-relz-wrye-bash-thread-46/page__view__findpost__p__16175712 <-- It should be fine if you just install it on top.


Did you delete your old Bash shortcut?

[Jose ordaz]

I just deleted the old shortcut.

I am using Python 3.0 which seems to have wxPython 2,8. The wxpython download link only has up to 2.7, and when I try to install it it says "No installation of Python 2.7 found in registry"

[carrie roche]

Wrye Bash doesn't support Python 3.0 because it isn't fully backwards compatible with existing python code. As well, psyco doesn't support python 3.0. For Bash to work, you have to use Python 2.5 or Python 2.6.

[Victoria Bartel]

Wrye Bash doesn't support Python 3.0 because it isn't fully backwards compatible with existing python code. As well, psyco doesn't support python 3.0. For Bash to work, you have to use Python 2.5 or Python 2.6.

Where can I find these?

[Sarah Knight]

Where can I find these?

Python 2.6 is installed with the Wyre Python 03 package.


Edit: Just follow the instructions, exactly. There is a wxPython download for Python 2.6 32-bit ansi. Follow the second link in the top-middle box, the box with the Python 2.6 header.

[Benito Martinez]

Where can I find these?

Here is http://www.tesnexus.com/downloads/download.php?id=63124.

Before you install the Wrye Python 3 package you must uninstalled any other version of Python and Wrye Bash.

[Angus Poole]

Here is http://www.tesnexus.com/downloads/download.php?id=63124.

Before you install the Wrye Python 3 package you must uninstalled any other version of Python and Wrye Bash.

You just have to upgrade Bash. I have Python 2.5 and 2.6 installed, last I checked, anyway. There is no reason for most users to have both installed though. Regardless, there is no need to uninstall Bash before upgrading.

[BlackaneseB]

I know I don't need to, but how can I make a CLEAN reinstall of wrye bash and python?

I mean, delete everything related to it and then install again?

[Gen Daley]

I know I don't need to, but how can I make a CLEAN reinstall of wrye bash and python?

I mean, delete everything related to it and then install again?

You don't need to make a clean reinstall. However, I would remove Python 3.0 through Add/Remove Programs if you are not using it.


Edit: Just follow the instructions I linked, installing the updated config on top of whatever you have (minus Python 3.0.)

[Danny Warner]

Wrye Bash doesn't support Python 3.0 because it isn't fully backwards compatible with existing python code. As well, psyco doesn't support python 3.0. For Bash to work, you have to use Python 2.5 or Python 2.6.

I instaled python 2.7 manually and it seems that Wrte Bash 285 works with it.
but i was forced to install 32 bit version (64bit is somewhat buggy with wxpython - it don't work with 32bit wxpython and 64bit one haven't ansi version)
i needed to install wxPython manually, and yes i needed damn comtypes

but if you install properly Wrye Bash work with Python2.7

(Python2.7 has some updates that 3.0 have but is backward compatible)

[Phillip Brunyee]

Bash only supports Python 2.5 or 2.6. We don't recommend the use of other python versions.

Bash may work with Python 2.7, but it hasn't been tested. This is mostly because Psyco doesn't support 2.7 and we don't want to lose the nice speed boost that it gives to those that install it (though this isn't as much of an issue any more with CBash being integrated). The risk with using 2.7 is that some functions may silently fail even though the vast majority of Bash works, leading to inexplicable bugs.

[TIhIsmc L Griot]

I found a bug in the structure of MreInfo DATA subrecord.
patch: http://github.com/valda/wryebash/commit/1ce3737eb4f65034e0776de02001cb371d36139e
Thanks.

[Mizz.Jayy]

I'm 99% sure that isn't a bug. TES4Edit, Bash, and CBash all use the same definition.

Without your patch, the dialog type field uses the first byte, the flag field uses the second byte, and the third field is unused.
With your patch, the dialog type field would take two bytes, and the flag field would use the third byte.

If your patch was correct, TES4Edit would always be wrong when displaying the flags field, and would occasionally be wrong when displaying the dialog type. It isn't though.

There is the possibility that the dialog type field uses the first byte, and the flag field uses both the second and third byte. However, this seems unlikely because the second byte contains all known info flags, and the third byte never appears to contain relevant data.

New thread shortly.

Please use the http://www.gamesas.com/index.php?/topic/1105224-relz-wrye-bash-thread-47/.