LuxCoreRender Forums

and I think a separate branch of BlendLuxCore is needed to conform to changes - Yes, that's what I meant. Providing a python39-compatible pyluxcore.pyd is just the easy part. Indeed, I've just tried it with the latest 2.93 alpha from 25 February and it is not working, as kintuX said BlendLuxCore al...

Usually BlendLuxCore works fine in alpha versions, but the Python update has broken compatibility. I could set up automated Windows builds for both Python versions. We already did that in the past, when Blender switched from Python 3.5 to 3.7, but alpha versions were not supported, it was when Blen...

Weird, I've just tried builds with 3 and 8 CPUs on my PC (16 GB) and they all succeeded. Maybe I was not using so much memory overall, even if I have some other programs open. By the way, if you don't need all samples like luxcoreconsole, luxcoreimplserializationdemo, etc., you can use: cmake-build-...

2) LINK : fatal error C1002: compiler is out of heap space in pass 2 Are you using the "x64 Native Tools Command Prompt for VS 2019" command prompt to run the build process? You could also try to reduce to number of parallel processes used to build. RAM usage can be very high due to LTCG, normally ...

I should have fixed this, now it's working here and on Azure.
Apparently some OpenImageIO headers messed up something with boost/lexical_cast.hpp. I moved their include's after those of LuxCore headers.

This looks like the same problem described a few posts ago by user theoharkes.
We do not have a solution at the moment, the only suggestion I can give is to use Visual Studio 2017, which has always worked without problems.

acasta69 wrote: ↑

Sun Feb 07, 2021 8:11 pm

I am under the impression that this is caused by a recent upgrade in Visual Studio 2019.

I can confirm this: the same commit that was built without problem here and on Azure in October, when I first tried VS2019, shows now the same errors.

I've not been able to find a solution yet. I was thinking of some compatibility issues with Windows SDKs, but the problem persists with all those I have tried. Also googling has not helped yet: similar but different issues are found and the proposed solutions are not applicable here (and also my lit...

Just checked and it's happening also here, I'm going to look into that. By the way, did you use the "cmake-build-x64.bat" to build with VS2019? Could you please let me know if the script has correctly detected VS2019 or you had to use the "/vs2019" switch? It should be possible to see that from the ...

Also using the .bat file processes only the actual changes (unless you use the "/rebuild" switch), however the most time consuming task is linking all binaries with LTCG, and also the initial project generation by CMake is not super fast. You might want to check the following, which can give some pe...