LuxCore v2.3 proposed features

Discussion related to the Engine functionality, implementations and API.
User avatar
lacilaci
Donor
Posts: 1807
Joined: Fri May 04, 2018 5:16 am

Re: LuxCore v2.3 proposed features

Post by lacilaci » Tue Oct 01, 2019 6:27 am

happyboy wrote:
Tue Oct 01, 2019 6:18 am
BTW: I don't know what is rayswitch, and only interested in issue 148, but I guess your use case might be similar to mine, so could you tell me how would you use rayswitch? Maybe I'll added it to my wishlist after understanding your use case 8-)
issue 148 is about being able to hide from certain ray type, but rayswitch shader or texture could actually switch from one material or texture to another...

in cycles they call it light path node, in corona it is rayswitch (https://coronarenderer.freshdesk.com/su ... l-and-map-)

Basically for example you could have two materials, where one would be visible for every ray type except reflection, and another one would be visible in reflections (or you would use null material in reflection and have a Vampire :D)

happyboy
Posts: 63
Joined: Sat Jun 22, 2019 5:39 am

Re: LuxCore v2.3 proposed features

Post by happyboy » Tue Oct 01, 2019 7:10 am

lacilaci wrote:
Tue Oct 01, 2019 6:27 am
Basically for example you could have two materials, where one would be visible for every ray type except reflection, and another one would be visible in reflections (or you would use null material in reflection and have a Vampire :D)
Ok, I understand you (theoretically), but since I'm only doing regular arch-viz type render, I don't really need to have a Vampire :)
Any more real-life use cases? 8-)
BTW: I'm using ray visibility to mainly reduce render time and hide artifacts, not to produce interesting effects. But rayswitch, if I understand you correct, can be used to create some specific effect?

marcatore
Donor
Posts: 359
Joined: Wed Jan 10, 2018 8:04 am

Re: LuxCore v2.3 proposed features

Post by marcatore » Tue Oct 01, 2019 7:17 am

My wishlist (by priority)
High Medium
  • Custom split normals support
  • Micropolygon displacement
  • raytraced bevel shader
  • raytraced ambient oclusion/dirt texture (with support for mapping distance)
Low

User avatar
lacilaci
Donor
Posts: 1807
Joined: Fri May 04, 2018 5:16 am

Re: LuxCore v2.3 proposed features

Post by lacilaci » Tue Oct 01, 2019 7:22 am

happyboy wrote:
Tue Oct 01, 2019 7:10 am
lacilaci wrote:
Tue Oct 01, 2019 6:27 am
Basically for example you could have two materials, where one would be visible for every ray type except reflection, and another one would be visible in reflections (or you would use null material in reflection and have a Vampire :D)
Ok, I understand you (theoretically), but since I'm only doing regular arch-viz type render, I don't really need to have a Vampire :)
Any more real-life use cases? 8-)
BTW: I'm using ray visibility to mainly reduce render time and hide artifacts, not to produce interesting effects. But rayswitch, if I understand you correct, can be used to create some specific effect?
You can make non reflective object be visible for GI - disable caustics per object to boost performance
Have an object that emits strong light but for camera is much weaker so that it won't be overexposed visibly.
Have a complex mix of materials for camera but a very simplified version for reflections for better performance.
Have one texture of floor saturated and visible in camera but another desaturated for GI rays to remove color cast...

The list goes on, it's just much greater flexibility.

User avatar
Dade
Developer
Posts: 3596
Joined: Mon Dec 04, 2017 8:36 pm
Location: Italy

Re: LuxCore v2.3 proposed features

Post by Dade » Tue Oct 01, 2019 7:29 am

Updated the list.
Support LuxCoreRender project with salts and bounties

User avatar
Dade
Developer
Posts: 3596
Joined: Mon Dec 04, 2017 8:36 pm
Location: Italy

Re: LuxCore v2.3 proposed features

Post by Dade » Tue Oct 01, 2019 7:40 am

lacilaci wrote:
Mon Sep 30, 2019 11:01 am
raytraced bevel shader
raytraced ambient oclusion/dirt texture (with support for mapping distance)
Amb... occl... I can not even write it....

It is not possible to trace rays inside a texture (or a material), nor will ever be. So any solution must be implemented as a pre-processing step (it is a bad idea to repeat a work at run-time, instead to do something once before the rendering) and/or something like the current pointness support.
lacilaci wrote:
Mon Sep 30, 2019 11:01 am
texture caching in ram?
What do you mean ? Use CPU ram to store image maps and GPU as a (smaller) cache of the image maps set :?:
Support LuxCoreRender project with salts and bounties

User avatar
Dade
Developer
Posts: 3596
Joined: Mon Dec 04, 2017 8:36 pm
Location: Italy

Re: LuxCore v2.3 proposed features

Post by Dade » Tue Oct 01, 2019 7:41 am

epilectrolytics wrote:
Mon Sep 30, 2019 11:39 am
- Implement persistent cache for DLSC and EVLC in LuxBlend #293
I consider this a "bug" fix and I assume it will be done anyway (so it is not included in the list).
Support LuxCoreRender project with salts and bounties

User avatar
Dade
Developer
Posts: 3596
Joined: Mon Dec 04, 2017 8:36 pm
Location: Italy

Re: LuxCore v2.3 proposed features

Post by Dade » Tue Oct 01, 2019 7:42 am

jgrover110 wrote:
Mon Sep 30, 2019 8:18 pm
-Custom split normals support
This is a BlendLuxCore feature, right ? It doesn't involve LuxCore API :?:
jgrover110 wrote:
Mon Sep 30, 2019 8:18 pm
-Principled hair bsdf shader
Only the shader or also a dedicated geometry primitive too ?
Support LuxCoreRender project with salts and bounties

User avatar
lacilaci
Donor
Posts: 1807
Joined: Fri May 04, 2018 5:16 am

Re: LuxCore v2.3 proposed features

Post by lacilaci » Tue Oct 01, 2019 7:59 am

Dade wrote:
Tue Oct 01, 2019 7:40 am
lacilaci wrote:
Mon Sep 30, 2019 11:01 am
raytraced bevel shader
raytraced ambient oclusion/dirt texture (with support for mapping distance)
Amb... occl... I can not even write it....

It is not possible to trace rays inside a texture (or a material), nor will ever be. So any solution must be implemented as a pre-processing step (it is a bad idea to repeat a work at run-time, instead to do something once before the rendering) and/or something like the current pointness support.
lacilaci wrote:
Mon Sep 30, 2019 11:01 am
texture caching in ram?
What do you mean ? Use CPU ram to store image maps and GPU as a (smaller) cache of the image maps set :?:
So maybe you could trace the ao/dirt mask before render with given amount of samples and then do rendering? I'm sorry I'm not sure how vray or corona or cycles do these shaders internally (here's how vray dirtmap looks like: https://docs.chaosgroup.com/display/VRA ... C+VRayDirt)

As for texture, I meant it like "out of core" feature just for textures, you said yourself that geometry isn't big issue for VRAM in luxcore, but large amount of high res textures is.
So maybe this could be a toggle in render settings, where I would enable using just system ram for textures for some speed penalty...?
Last edited by lacilaci on Tue Oct 01, 2019 8:06 am, edited 1 time in total.

User avatar
lacilaci
Donor
Posts: 1807
Joined: Fri May 04, 2018 5:16 am

Re: LuxCore v2.3 proposed features

Post by lacilaci » Tue Oct 01, 2019 8:04 am

Dade wrote:
Tue Oct 01, 2019 7:42 am
jgrover110 wrote:
Mon Sep 30, 2019 8:18 pm
-Custom split normals support
This is a BlendLuxCore feature, right ? It doesn't involve LuxCore API :?:

Yes, blender has multiple tools for handling normals, but the only options available for luxcore when rendering are flat, smooth, autosmooth... No custom sets, splits or weighted normals seem to work (this is a pretty big problem for cad models, booleans, and in general blender has nice normal editing tools that are useless for luxcore atm)

Post Reply