Search found 100 matches

by acasta69
Thu Apr 11, 2019 3:27 pm
Forum: Development
Topic: Adding LuxCore to own application
Replies: 6
Views: 280

Re: Adding LuxCore to own application

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 ...
by acasta69
Wed Apr 10, 2019 1:06 pm
Forum: User Support
Topic: Could not locate required Boost files
Replies: 9
Views: 241

Re: Could not locate required Boost files

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...
by acasta69
Fri Apr 05, 2019 5:22 pm
Forum: User Support
Topic: Could not locate required Boost files
Replies: 9
Views: 241

Re: Could not locate required Boost files

I have fixed the problem.
But as I said, if you want to use pyluxcoretools you need also Python with PySide2.
by acasta69
Fri Apr 05, 2019 8:06 am
Forum: User Support
Topic: Could not locate required Boost files
Replies: 9
Views: 241

Re: Could not locate required Boost files

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...
by acasta69
Fri Apr 05, 2019 6:03 am
Forum: User Support
Topic: Could not locate required Boost files
Replies: 9
Views: 241

Re: Could not locate required Boost files

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...
by acasta69
Mon Apr 01, 2019 7:37 am
Forum: Development
Topic: Adding LuxCore to own application
Replies: 6
Views: 280

Re: Adding LuxCore to own application

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...
by acasta69
Thu Mar 28, 2019 2:04 pm
Forum: User Support
Topic: Luxcore build error
Replies: 7
Views: 224

Re: Luxcore build error

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...
by acasta69
Thu Mar 28, 2019 10:27 am
Forum: User Support
Topic: Luxcore build error
Replies: 7
Views: 224

Re: Luxcore build error

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...
by acasta69
Thu Mar 28, 2019 8:30 am
Forum: User Support
Topic: Luxcore build error
Replies: 7
Views: 224

Re: Luxcore build error

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.
by acasta69
Tue Mar 19, 2019 8:34 am
Forum: User Support
Topic: Ply ASCII
Replies: 18
Views: 470

Re: Ply ASCII

it complains of a Ply: Not a PLY file. Expected magic number 'ply\n' I think I've already met this problem time ago, it's because your ASCII file has Windows-style line breaks (CR+LF) instead of Unix-style (LF only). Our ply import code is probably an old version that understands only the latter. H...