Johannes Hinrichs

Reopening because I found a remaining bug: - [ ] When GPU backend is OCL (not CUDA), then the connection is still made. Looks like the actual setting of shadow...

Hello, could you please add some description of the original problem, i.e. why this is necessary to fix to begin with? Does it affect a specific BlendLuxCore version? Is this...

> On install of Lux renderer through documentation. The addon requested that all required modules are installed from python. Obtaining these modules using the given documentation, multiple errors were met...

The license is not an issue. Apache 2.0 Only applies to "LuxCore", i.e. the core engine. The Blender addon "BlendLuxCore" is under GPL (it must be due to the use...

Update on the extensions platform publication, regarding our violation of the self-containment: There is an option described here: https://docs.blender.org/manual/en/latest/advanced/extensions/creating_repository/static_repository.html which allows to create a custom repository. Users still have to...

Hello, indeed, additional color space support seems a relevant feature. From recent personal observations, I can't seem to fully match the output between Cycles and LuxCore even for a simple...

The feature to switch nodes has nothing to do with it. LuxCore itself still needs knowledge of the color space of its inputs, and/or appropriate conversions need to take place.

Addressing an issue like this may be difficult, if it can't be reproduced. And arbitrary crashing of OIDN is not something I observed. So we need to identify more specifics:...

@d23lygjdpzok Any follow-up on this?

Updates thoughts for 2025: - The code issued in commit https://github.com/LuxCoreRender/BlendLuxCore/commit/56157c7b381104c600ef3ab192098d1e16afb96d still appears to be valid, i.e. specifically all Intel devices are discarded. - By now, Intel does make "big"...