After opening a thread in the Mailing List, it turned out that the problem lies in the PySide prerequisite.
Takayoshi Matsumoto has provided us with an updated PyQT-addon and an updated PySide to address the issue with Windows 10. This only seems to work when using an “external” Python…
- Download and install Python 2.7 and Pywin32
- Download “PySide-1.2.4-cp27-cp27m-win_amd64.whl” from here and the updated addon from here.
- Open a command prompt in the folder where you've downloaded the alternative PySide and install it using
Code: Select all
pip install --upgrade PySide-1.2.4-cp27-cp27m-win_amd64.whl
- Right-click the Windows menu logo. Go to Control Panel → System and Security → System → Advanced system settings → Environment variables" and create an environment variable called “PYTHONHOME”
and point it to your Python 2.7 install (for example: E:\Python27). For some reason this is a requirement under Softimage 2015 in Windows 10 if you want to use an "external Python".
(If you want to use the "internal Python" again, you'll have to delete this environment variable first.) - Go to “Preferences > Scripting” and uncheck “Use Python Installed with Softimage”. Install the updated addon. Restart Softimage.
There is one gotcha to all this. When using the “external” Python you lose the “print” function in Python, so you’ll have to revert to good old-fashioned “Application.Logmessage”…