In this moment daily builds should again be compatible with Blender 2.92.
We will switch again as soon as the problem with 2.93 is solved.
Search found 271 matches
- Tue Jun 01, 2021 2:26 pm
- Forum: News
- Topic: LuxCoreRender daily/automatic builds
- Replies: 222
- Views: 327089
- Fri May 07, 2021 6:57 am
- Forum: User Support
- Topic: No "latest build" for linux on git?
- Replies: 11
- Views: 5503
Re: No "latest build" for linux on git?
Thanks for highlighting this. It seems there is some problem when checking the Python version: * Checking python !!! Python major version '3' is required cp: cannot stat 'target-64-sse2/LuxCore.tar.bz2': No such file or directory mv: cannot stat 'target-64-sse2/LuxCore.tar.bz2': No such file or dire...
- Wed Apr 21, 2021 2:10 pm
- Forum: User Support
- Topic: LuxCore 2.5 Release Installation Error on Linux
- Replies: 9
- Views: 4633
Re: LuxCore 2.5 Release Installation Error on Linux
This should now be fixed, please get the very latest BlendLuxCore.johannes.wilde wrote: ↑Wed Apr 21, 2021 2:00 pm I lookend in
/home/XXX/.config/blender/scripts/addons/BlendLuxCore/bin
and found a file called oidnDenoise but no libOpenImageDenoise.so.1
- Wed Apr 21, 2021 2:07 pm
- Forum: News
- Topic: LuxCoreRender daily/automatic builds
- Replies: 222
- Views: 327089
Re: LuxCoreRender daily/automatic builds
I should have fixed this, some change was required because of upgraded libraries.
A new build should be ready in minutes.
I hope it works also on Linux, I have no way to check.
About MacOS I'm not able to help, sorry, but it's probably a different problem.
A new build should be ready in minutes.
I hope it works also on Linux, I have no way to check.
About MacOS I'm not able to help, sorry, but it's probably a different problem.
- Wed Apr 21, 2021 6:42 am
- Forum: News
- Topic: LuxCoreRender daily/automatic builds
- Replies: 222
- Views: 327089
Re: LuxCoreRender daily/automatic builds
It appears to me as a last update 11 days ago The BlendLuxCore daily builds are now working again. @B.Y.O.B. I have bumped the version number in BlendLuxCore to re-enable daily builds. We were in a corner case for which I have no good solution yet: when the BlendLuxCore pipeline is triggered by a L...
- Tue Apr 20, 2021 2:01 pm
- Forum: User Support
- Topic: Problem with IES file
- Replies: 12
- Views: 4679
Re: Problem with IES file
Can you tell me how to change "." "," ? It is in Control Panel --> Region --> Additional settings Untitled.png Normally the first setting (decimal symbol) is "," in European countries, while the "digit grouping symbol is "." Try if swapping them fixes yo...
- Thu Apr 08, 2021 1:44 pm
- Forum: News
- Topic: LuxCoreRender daily/automatic builds
- Replies: 222
- Views: 327089
Re: LuxCoreRender daily/automatic builds
I just noticed that the automated build for Linux is not working since some days. It stops when building OpenImageIO: ]0;openimageio stage * Cleaning and unpacking openimageio * Compiling openimageio * Patching OpenImageIO '/home/vsts/work/1/s/LinuxCompile/distfiles/oiio-1.8.13-plugin.cpp' -> 'src/l...
- Tue Mar 23, 2021 8:04 pm
- Forum: Development
- Topic: SDK compatibility issues in VS2019 C++ project with std::string
- Replies: 13
- Views: 6599
Re: SDK compatibility issues in VS2019 C++ project with std::string
The main thing was that when creating a new project in VS2017/VS2019, removing the _DEBUG definition was not enough to match runtimes, you also have to go into project properties and set Configuration properties -> Advanced -> Use Debug Libraries to No Your project failed as you described also here...
- Tue Mar 23, 2021 10:14 am
- Forum: Development
- Topic: SDK compatibility issues in VS2019 C++ project with std::string
- Replies: 13
- Views: 6599
Re: SDK compatibility issues in VS2019 C++ project with std::string
"aa" is "char *" while std::string is a different type, do you get the same error if you use something like "string("aa")" instead of "aa" ? I tried, and unfortunately i do... I also tried and it's working here, both VS2017 and VS2019. Code: Propert...
- Mon Mar 22, 2021 4:00 pm
- Forum: Development
- Topic: SDK compatibility issues in VS2019 C++ project with std::string
- Replies: 13
- Views: 6599
Re: SDK compatibility issues in VS2019 C++ project with std::string
prop is already corrupted, with dataType==BOOL_VAL(1) That is also what I am seeing: that piece of data is recognized as BOOL_VAL, and then the corresponding output is: test1.prop1[0] => 1 I have no "bad allocation" error though. Yesterday I compiled it also in a Linux VM and result is th...