What this serves to do is to increase setup time significantly, and confuse user with 10 different user interfaces, yet with no more functionality than a single combined Principled/Ubershader material.Ī cherry on top is fresnel effect (“conveniently” called IOR even in shaders that don’t have transmission) which is disabled by default - instant throwback to scanline renderers in 90’s where fresnel was that secret sauce you had to manually turn on on every newly created material Instead of having one, combined ubershader (something like principled), you are presented with 10 different fragmented material types, each of them very limited to a specific BSDF combination. So when you finally get it working, you are greeted with somewhat reasonably looking integration, but the ugly parts start to show up.
Luxcorerender blender 2.8 archive#
In a typical opensource fashion, there’s an unwritten rule nothing must work out of the box on a first try After a bit of the digging, you realize that Win64 with OpenCL archive is actually only OpenCL part of Win64 archive, so it has to be installed over already existing Win64 non-OpenCL archive, of course installation guide doesn’t mention that You will follow the steps precisely and get to a point where the addon doesn’t show up in your addon list at all. You will download the zip, and since you try to be smart, you will actually take a look at the installation guide: Since you want to render on GPU, you will probably download Win64 with OpenCL support. You will then proceed to pick a right install. You will find BlendLuxCore (why not just name it LuxCore for Blender?). You will go to a website seeking Blender addon. So imagine you are a new user interested in LuxCore:
From my experience, first impression matters, a lot.
0 kommentar(er)
