LuxCoreRender Forums

Sorry that I'm late with this, I see you've already solved, but anyways: with n = number of cores you want to use.

Would be interesting to know how this can work for @Acasta69 except everything is compiled without _DEBUG and against release runtime. I've just built with cmake-build-x64.bat /dll /debug create-sdk.bat Apart from having to manually gather the built executables from Debug folders, everything seems ...

Sorry, am new with all of this, i did follow the procedure described on the above Windows Compile page, but i too got No OpenCL support... How did you get it building with OCL? A further requirement is to install an OpenCL SDK. A very lightweight one, that I am using at the moment, is the GPUOpen O...

I have fixed the problem.
But as I said, if you want to use pyluxcoretools you need also Python with PySide2.

However, if you don't need pyluxcoretools, even with that error you have all the required luxcore binaries. Apparently I was wrong and this error prevents binaries from being generated. So at the moment you really need python + PySide2 to build everything. I'll see if this can be modified so that o...

To correctly generate pyluxcoretools files you also need to have Python 3.5 with package PySide2 installed (see same procedure, a few rows below: In order to create an official release... ). I will update the README in order to make this more clear. However, if you don't need pyluxcoretools, even wi...

why do you need to compile LuxCore DLL in debug mode ? Can't you link your app compiled in debug mode with a DLL compiled in release mode ? I was also wondering about that... Actually I never had the need to build LuxCore in debug mode. There could be something to be modified in the cmake config, I...

I'm glad it's working now. :) But if the error can be corrected, let me know so that I can correct that too. Do you have a working Python3 with PySide2 also installed? If not, that's the most likely cause: the pyluxcoretools cmake script deletes some files in order to regenerate them with the availa...

Fix the real problem, don't do additional work to just work around. There must be a reason why for you (and only for you) cmake does't detect VisualC++: https://stackoverflow.com/questions/51668676/cmake-visual-studio-15-2017-could-not-find-any-instance-of-visual-studio I agree, and the most likely...

Hi, it seems that for some reason cmake cannot find a C/C++ compiler.
Could it be that you have installed Visual Studio, but without selecting C/C++ development components?
You could try to run the installer again and verify that something like "Desktop development with C++" is selected.