Closed GoogleCodeExporter closed 9 years ago
Do you already have PyQt or Qt installed? Or is installing our code the first
you've
dealt with it?
Original comment by eric.hul...@gmail.com
on 20 Oct 2009 at 11:03
Thanks for the reply.
I don't install original PyQt.
I installed PyQt4-gpl-snapshot-20090412_win32-msvc2008.
But I installed Qt(qt-win-opensource-src-4.5.2) in C:\Qt\4.5.2.
How should I deal?
I use WindowsXP x64 SP2.
Best regards.
Original comment by vanilla....@gmail.com
on 20 Oct 2009 at 11:45
Ok, I think I know whats wrong then - you need to make sure that
'c:/blur/common' is
in your Environment -> PATH variable, and that its before any references to the
Qt
paths. We usually just put it first.
Since we've made our own build of the Qt DLL's, you need to make sure its our
DLL
that is being loaded first. I think that error is because you're getting our
version
of PyQt trying to load against a standard build of a Qt DLL
Original comment by eric.hul...@gmail.com
on 21 Oct 2009 at 12:26
[deleted comment]
I still have same error.
I deleted C:\Qt\4.5.2\bin line from PATH.
I set following PATH.
Environment -> PATH
* C:\blur\common <- set first
* C:\WINDOWS\system32\blur64
* C:\Python24
* ...
Environment -> PYTHONPATH
* C:\Python24\Lib\site-packages
Best regards.
Original comment by vanilla....@gmail.com
on 21 Oct 2009 at 1:57
[deleted comment]
Just as a note on that topic. I did run into issues as it seems the blurQT
installer
is wiping the path variable instead of setting it correctly (wich is
windows\system32\blur according to the installer and not the common dir (wich
isnt
existing here)).
This killed quite a bunch of other things here so it's kinda big gotcha.
After resetting the path variable manually everything seems fine.
Original comment by instinctvfx@gmail.com
on 22 Oct 2009 at 8:24
I tried the following.
Environment -> PATH
* C:\blur\common <- delete
* C:\WINDOWS\system32\blur64 <- delete
reboot
I add PATH variable manually.
Environment -> PATH
* C:\blur\common <- add set first
reboot
I still have same error.
I searched QtCore4.dll in my PC.
SugarSync(QtCore4.dll) <- delete
PerfectDisk(QtCore4.dll) <- delete
C:\WINDOWS\SysWOW64 <- delete
I still have same error.
Though the following might be unrelated, I found QtCore4.dll in my PC.
C:\max2010
C:\max2010_64
C:\Program Files (x86)\Adobe\Adobe After Effects CS4\Mocha\bin
C:\Program Files (x86)\Adobe\Adobe SING Glyphlet Manager CS4
C:\Program Files (x86)\Common Files\Autodesk Shared\AdLM\R1
C:\Program Files (x86)\MeshLab
C:\Program Files\Common Files\Autodesk Shared\AdLM\R1
C:\Qt\4.5.2\bin
C:\Qt\4.5.2\lib
Best regards.
Original comment by vanilla....@gmail.com
on 22 Oct 2009 at 2:20
Thanks for the feedback guys - we will look into it!
Original comment by eric.hul...@gmail.com
on 22 Oct 2009 at 7:02
[deleted comment]
I set up max10_64 and max2009_64, and there was no error.
max10 startup error and TreeGrunt error
max2009 startup error and TreeGrunt error
max10_64 no startup error and TreeGrunt error
max2009_64 no startup error and TreeGrunt error
C:\max10_64\ui\macroscripts\BlurGrunt_Macros_TreeGrunt.mcr ->Toolbars add
TreeGrunt get the following error.
Traceback (most recent call last):
File "<string>", line 2, in <module>
ImportError: No module named trax
Startup error additional information:
C:\WINDOWS\system32\blur64\QtCore4.dll
rename QtCore4.dll -> _QtCore4.dll
max10_64(same error max10)
Traceback (most recent call last):
File "C:\Max10\scripts\python/__startup__.py", line 12, in ?
import blur.wingui
File "C:\Python24\Lib\site-packages\blur\wingui\__init__.py", line 22, in ?
from PyQt4.QtCore import QCoreApplication
It is thought that max10_64 has linked with
QtCore4.dll(C:\WINDOWS\system32\blur64).
I think QtCore4.dll(C:\blur\common) don't link with max10.
In my PC Environment, C:\blur\common(EnvironmentPATH) doesn't function
correctly.
Sorry bad English.
Best regards.
Original comment by vanilla....@gmail.com
on 30 Oct 2009 at 12:57
running into the same issue in Softimage:
# ERROR : Traceback (most recent call last):
# File "<Script Block >", line 28, in XSILoadPlugin
# import PySoftimage
# File
"c:\blur\dev\offline\workgroups\xsi_all\data\site-packages\PySoftimage\__init__.
py",
line 29, in <module>
# from blur import wingui as gui
# File "C:\Python26\lib\site-packages\blur\wingui\__init__.py", line 22, in
<module>
# from PyQt4.QtCore import QCoreApplication
After installing the blur PyQt it has prepended 'C:\windows\system32\blur64' to
path,
but still gives the error.
As also mentioned above, I have nothing in blur/common [not even the folder
'common']. Presume this is a legacy thing?
The Qt install I have is '2009.05', can't seem to find any version numbers any
more
on the download site - wondering if this is part of the problem?
Any pointers much appreciated.
Jules
Original comment by droolz202@googlemail.com
on 5 Jan 2010 at 10:28
Seems that there was an issue with python recognizing any values from the 'PATH'
windows enviroment variable, I've changed packages.py to:
# Register Workgroup site-packages
path = os.path.abspath( os.path.split( in_reg.fileName )[0] +
'../../../data/site-packages' ).lower()
if ( not path in sys.path ):
sys.path.append( path )
#JS3D hack to add QT path stuff
if not 'C:\Windows\System32\blur64' in sys.path:
sys.path.append('C:\Windows\System32\blur64')
very hacky, but forces the Qt search path, this however now throws and error in
xsi:
# ERROR : Traceback (most recent call last):
# File "<Script Block >", line 32, in XSILoadPlugin
# import PySoftimage
# File
"c:\blur\dev\offline\workgroups\xsi_all\data\site-packages\PySoftimage\__init__.
py",
line 32, in <module>
# gui.connectPlugin( xsi.GetPluginInstance(), xsi.GetWindowHandle() )
# File "C:\Python26\lib\site-packages\win32com\client\dynamic.py", line 512,
in
__getattr__
# raise AttributeError("%s.%s" % (self._username_, attr))
# AttributeError: <unknown>.GetPluginInstance
Xsi apparently can;t find the 'GetPluginInstance' method, which I'm presuming
is a
blur made method, but can;t find where it is supposed to be defined. Still
investigating :).
Original comment by droolz202@googlemail.com
on 6 Jan 2010 at 9:49
The GetPluginInstance is a blur plugin - check your workgroups to make sure that
there is a BlurApplication.dll in your
c:/blur/dev/offline/workgroups/xsi_all/application/plugins/ folder.
Make sure that is loading properly in your Plugin Manager. Thats where that
method
is being registered...
Original comment by eric.hul...@gmail.com
on 6 Jan 2010 at 9:02
Thanks Eric, got the dll, but presume this was put there by the PySoftimage
installer. In which case this is probably down to it being 32 bit? There
dosen't seem
to be a 64bit version.
Original comment by droolz202@googlemail.com
on 6 Jan 2010 at 9:30
Yeah, that would definitely be it - we haven't had the chance to make the
builds for
XSI x64 since we don't use that in the studio yet - will probably have those
coming
up pretty soon though.
Original comment by eric.hul...@gmail.com
on 6 Jan 2010 at 9:32
No dll error in plugin manager as far as I can tell. Please see attached image
Original comment by droolz202@googlemail.com
on 6 Jan 2010 at 9:36
Attachments:
Sorry, got a crossed post there. If you need me to compile I'm happy to give it
a whirl.
Original comment by droolz202@googlemail.com
on 6 Jan 2010 at 9:38
It has already been said on this thread, but as it is not fixed I say it as a
reminder :)
The installation still cleans up the environment variable Path, which leads to
max not loading blurPython among other non-related problems.
Original comment by titeblo...@gmail.com
on 30 May 2011 at 2:09
What do you mean by cleans up the environment variable Path?
I have not been able to recreate that bug at all. Its just getting completely
reset when you run the installer?
What version of Windows are you on, with which version of the BlurOffline did
you run?
Thanks!
Original comment by eric.hul...@gmail.com
on 31 May 2011 at 12:31
I've also had my PATH variable set to empty when I tried Py3dsMax. As it didn't
work out of the box, I uninstalled everything quite quickly, so I can't say if
it was the installer or uninstaller that wiped the PATH, but with an empty PATH
Windows does not work fine.
I tried on may 15, on a Win7 x64 system. Can't be more specific but if I find
some time I may make another run to try to reproduce the problem.
Original comment by nicolas....@gmail.com
on 31 May 2011 at 6:45
I already faced that with the old installers and i can confirm that it has
happened to me with the new installers as well. As i did quite some install
madness to different max versions i cannot really say if it was installing or
uninstalling either tho.
Original comment by instinctvfx@gmail.com
on 31 May 2011 at 9:15
Original comment by hen...@gmail.com
on 3 Dec 2013 at 8:16
Original issue reported on code.google.com by
eric.hul...@gmail.com
on 20 Oct 2009 at 11:01