Jenrai Posted February 25, 2010 Share Posted February 25, 2010 Generally I don't use Blender... I'm far from being the worlds greatest modeller/artist and have given it a wide berth. However, I thought I'd have a play. Then I find out that the newest version of Blender relies on Python 2.6. Problem. I use Python 2.5.2 as I use Wrye Bash. Not willing to lose that. Considering I play with FCOM its pretty much essential.BUT... install Python 2.6 on my comp and Wrye freaks out. Remove it, Wrye works. Blender don't like playing without Python 2.6 though. Figured that it might just be because I have 2 versions of Python installed, and after a little browse through the Wrye read-me, head off to source forge to d/l wx, python for windows and PIL for the new version of Python. Theres a couple of other things (psycho and something else) which aren't needed, and there isn't a Python 2.6 compatible version of the wx ansi thats also psycho enabled... so I can live without the extra speed. Lets not bother. Install the Python libraries, Python for windows, the wx ansi, & pil. Reinstall Wrye. It gets half way through starting up Wrye (the "initializing mod infos" window) and *ding* "Python has encountered an error and needs to close" ... Bash dump reveals the error is something to do with the imaging files not found. :wallbash: :wallbash: Bash's readme says one of the components is not installed right if this is the error. Ohm... yeah, it is. Checked. Double checked. Reinstalled it. Uninstalled the whole shebang and reinstalled it all again. No change. :wallbash: :wallbash: I guess in my roundabout way what I'm asking is wether or not anyone is running Wrye 275 with Python 2.6 support for Blender installed, and if so, how? Are they compatible and I've missed something or are they not compatible and I shoulda bloody known better? =DAnd yeah, I know this isn't the official home for questions about Wrye, but answers tend to come quicker and be right on the Nexus. :)Thanks in advance for the help, guys. Jenrai Link to comment Share on other sites More sharing options...
Jahmir0 Posted February 25, 2010 Share Posted February 25, 2010 Hi Jenrai. Not sure if this is going to be of much help since i really don´t know a thing about python other than it allows certain programs to run and use that language when installed :P Anyway, i have both python 2.5 and 2.6 installed and also blender 2.49b and wrye 278b(just installed today, i had 277 before i think). I didn´t have any problems with any of the installations and the only thing i can remember that might be helpfull is that i first installed 2.6 and only after that did i install 2.5 and wrye bash(i recently reinstalled oblivion). Like i said this probably won´t be of any help to you but i was very surprised at how smoothly i was able to install both python versions, and i remember thinking it might have had something to do with the order i installed them by. This is nothing but an uneducated guess of course, but i thought i´d mention it anyway. Cheers Link to comment Share on other sites More sharing options...
Jenrai Posted February 25, 2010 Author Share Posted February 25, 2010 Thanks Jamiro. :) I'm gonna have another play when I get home then if you have it working. Must be something I've overlooked. Thanks again matey. Jenrai Link to comment Share on other sites More sharing options...
Jahmir0 Posted February 25, 2010 Share Posted February 25, 2010 You´re welcome :) And good luck with sorting it out. Link to comment Share on other sites More sharing options...
Jenrai Posted February 26, 2010 Author Share Posted February 26, 2010 Rightyho... added to list of potential probs and how to fix them; no. 8,0001245... (I jest... but its prolly not far off. ;) ) If you wanna use Bash & Blender with full Python support, it seems to work best if you install Python 2.6 for Blender 2.49b first, then Blender itself (and fire it up to make sure its working) then install Python 2.5.2 (for bash), and the extentions (psycho, python for windows, PIL, et al), then Wyre Bash... it works.The problem seemed to occur because I install Python 2.6 AFTER 2.5 (without overwriting. It was in a different directory. I'm not that dumb. heh heh) and Bash didn't like that for whatever reason. Jenrai Link to comment Share on other sites More sharing options...
Recommended Posts