I am running W7 (64) with Python 2.6.4, wxPython 2.8.10.1 and Comtypes 0.6.2.
Wrye Bash 279 runs great, had it up to 253/370 mods no problem.
Currently on a new install, up to and including UOPs, so only got 6 items loading. The 279 setup is working fine. Can bash a patch, add/remove, sort etc. Running BOSS updates straight away, and all files got good time sigs to load in order.
Downloaded 281 and overwrote files as required. On first start I get the purple Oblivion.esm, and can rebuild a patch. However, if I add a new mod, I get the following wxPython error:
Traceback (most recent call last): File "F:\Oblivion\Mopy\basher.py", line 1355, in OnItemSelected self.details.SetFile(modName) File "F:\Oblivion\Mopy\basher.py", line 1467, in SetFile tagsStr = '\n'.join(sorted(modInfo.getBashTags())) File "F:\Oblivion\Mopy\bosh.py", line 7288, in getBashTags tags = self.getRow().get('bashTags')AttributeError: 'str' object has no attribute 'get'
If I run BOSS from inside Wyre it completes correctly but Wyre does not update to new order.
If I restart Wyre, I get the above wxPython error, but Wyre reads the new modlist ok and the order is now correct and time sigs are good. Now I am stuck... I can't add/remove, edit or rebuild without the error above popping up.
So, I reverted back to 279 by overwriting files. It runs great as it always has, I ran a rebuild and it was fine. Thinking maybe my 281 install was bad, I redownloaded it and then installed it over the 279 again.
On first start it appears fine, the added mod is there, everything is in order the time sigs are good. But as soon as I install a new mod or try to remove one I get the same wxPython error above.
So, now for the last try... I completely uninstall all Wyre, Python and clean down with CCCleaner to remove all traces from registry etc. And then reinstall from scratch, Python, wx, Com, Wyre 275, 281 and...
...same problem. It runs first time then errors as above.
I am solely a user, not a modder or programmer but it seems to me that on my system 281 is not updating correctly, that it works on an update done by 279 but can't run it's own update without compiling an error.
So, looks like I'm back with 279 - a great tool - it works for me.
Any enlightenment of what else I can try greatly appreciated.