The problem is that on Windows, you can't enable the addon in any buildbot build (as described in the OP).jensverwiebe wrote: ↑Mon Jan 22, 2018 6:51 pm Why waiting ? Grab an actual testbuild, else we don't get rid of hidden bugs.
Windows: Can't enable addon in latest Blender
Forum rules
Please upload a testscene that allows developers to reproduce the problem, and attach some images.
Please upload a testscene that allows developers to reproduce the problem, and attach some images.
Re: Windows: Can't enable addon in latest Blender
Re: Windows: Can't enable addon in latest Blender
Im also getting that error message with Windows 64bit (with OpenCL support).
I tried to installing the newest addons luxcorerender release v2.0 alpha2 and v2.0 alpha1 but none are installing.
I have tried on blender 2.79 and also the the newest from blender build.
I tried to installing the newest addons luxcorerender release v2.0 alpha2 and v2.0 alpha1 but none are installing.
I have tried on blender 2.79 and also the the newest from blender build.
-
- Supporting Users
- Posts: 141
- Joined: Tue Jan 09, 2018 6:48 pm
Re: Windows: Can't enable addon in latest Blender
Thanks !jensverwiebe wrote: ↑Tue Jan 23, 2018 2:55 pm Testbuilds 'a' are up:
https://download.blender.org/release/Blender2.79/
Python used: 3.5.3
Jens
Tested and shader work.shader are saved after save/re-open.
Re: Windows: Can't enable addon in latest Blender
I updated our download page. Thanks for the info.
Re: Windows: Can't enable addon in latest Blender
Thank you, add-on is now installed and working.
Re: Windows: Can't enable addon in latest Blender
I dug a bit into this topic, since the problem will sooner or later come up again.jensverwiebe wrote: ↑Sat Jan 20, 2018 8:15 pm Normally that should not be an issue as long as no newer py exclusive functions are used ( which are not afaik ).
On Linux and macOS i made it so the module pulls the python from Blender itself.
Dunno if thats possible with Windows, someone should take a look.
The trick is to use dynamic_lookup on macOS or same default link behaviour on Linux and not even link pythonlib.
Maybe Win need a flag set for such like macOS does. ( equivalent to: -undefined dynamic_lookup )
More to readup here: https://msdn.microsoft.com/en-us/librar ... s.85).aspx
Jens
It seems that in Windows there is little that can be done against this behaviour, because link with Python happens including explicitly the minor version:
https://stackoverflow.com/a/33674759
The only thing that could help is the stable Python ABI, which could be used defining symbol "Py_LIMITED_API" when building Boost.Python and pyluxcore:
https://docs.python.org/3.5/c-api/stable.html
https://www.python.org/dev/peps/pep-0384/
I don't know if that could be used for pyluxcore, at least in principle, but for sure it is not supported by Boost.Python (not our version, which i have just tested, but most likely not even the latest).
So, at the moment it seems that for Windows the exact same minor version of Python will be needed. I could not find any traces of other workarounds mentioned anywhere...
Re: Windows: Can't enable addon in latest Blender
Thanks for your research.
Re: Windows: Can't enable addon in latest Blender
Thanks Acasta69 for having investigate the problem. It looks like 2.79a is going to be released with Python v3.5 so we will have all the time to update for Blender v2.8.
Re: Windows: Can't enable addon in latest Blender
Just downloaded the 2.79a RC for Win64, still unable to enable Luxcore. Any ideas on how to get it working.
Thanks, Wig42
Thanks, Wig42