What is new in the under development LuxRender v1.7 ?

Discussion related to the implementation of new features & algorithms to the Core Engine.

Moderators: Dade, jromang, tomb, zcott, coordinators

What is new in the under development LuxRender v1.7 ?

Postby Dade » Fri Aug 19, 2016 9:40 am

The list of (major) new features in the under development LuxRender v1.7:

User avatar
Dade
Developer
 
Posts: 8354
Joined: Sat Apr 19, 2008 6:04 pm
Location: Italy

Re: What is new in the under development LuxRender v1.7 ?

Postby B.Y.O.B. » Fri Aug 19, 2016 11:41 am

We seem to have the same thoughts. I created the draft for the "New in 1.7" wiki page a few hours ago :)
http://www.luxrender.net/wiki/New_in_1-7
User avatar
B.Y.O.B.
Developer
 
Posts: 5131
Joined: Wed Nov 10, 2010 4:10 pm
Location: Germany

Re: What is new in the under development LuxRender v1.7 ?

Postby sharlybg » Tue Aug 30, 2016 7:17 am

For Me the most wanted feature for better user experience should be :

1/ viewport rendering start resolution for better responssivity (like in cycles)

2/ material Node conservation while importating asset (but this will be fix only if the blender limitation get fixed first )

Not so important but could be very nice :

Glare like in Fstorm render
i7 6700k + 32 Gb DDR4 + 2X R9 390 sapphir nitro.
User avatar
sharlybg
 
Posts: 725
Joined: Tue Nov 02, 2010 10:22 am
Location: Ivory coast

Re: What is new in the under development LuxRender v1.7 ?

Postby Dade » Tue Aug 30, 2016 7:37 am

sharlybg wrote:1/ viewport rendering start resolution for better responssivity (like in cycles)


This is available in new RTPATHCPU, it just requires a LuxBlend update to use this new feature for previews (that it should be as easy as add "RT" in front of the "PATHCPU" string and nothing else).
User avatar
Dade
Developer
 
Posts: 8354
Joined: Sat Apr 19, 2008 6:04 pm
Location: Italy

Re: What is new in the under development LuxRender v1.7 ?

Postby B.Y.O.B. » Tue Aug 30, 2016 8:13 am

This is available in new RTPATHCPU

Internally the resolution is reduced, yes, but is the transferred film resolution reduced as well?
If not, it does not lift the key limitation: slow Python operations on many pixels.
But I have to say I still could not test your patch in this area because no daily builds are available, maybe this problem is already solved.

Dade wrote:(that it should be as easy as add "RT" in front of the "PATHCPU" string and nothing else).

I tried that (with RTPATHOCL), I only get a black viewport.
User avatar
B.Y.O.B.
Developer
 
Posts: 5131
Joined: Wed Nov 10, 2010 4:10 pm
Location: Germany

Re: What is new in the under development LuxRender v1.7 ?

Postby sharlybg » Tue Aug 30, 2016 8:25 am

This is available in new RTPATHCPU
:

Nice can't imagine that it is at a near futur like that :D :

I tried that (with RTPATHOCL), I only get a black viewport.


It's like there is no OCL acceleration version available at the moment .... :?:
i7 6700k + 32 Gb DDR4 + 2X R9 390 sapphir nitro.
User avatar
sharlybg
 
Posts: 725
Joined: Tue Nov 02, 2010 10:22 am
Location: Ivory coast

Re: What is new in the under development LuxRender v1.7 ?

Postby kalel » Tue Aug 30, 2016 9:20 am

sharlybg wrote:
I tried that (with RTPATHOCL), I only get a black viewport.


It's like there is no OCL acceleration version available at the moment .... :?:


I don't know if this is at all related or not, but when I try to use RTPATHOCL for rendering (not preview) by using the custom parameters field, the screen is also black (and sample count per second is weird),
but only until the render is stopped. When I stop the render, I get the image.

Video: https://cdn.streamable.com/video/mp4/rjar.mp4

(in the video, path ocl was not chosen before adding the custom parameter, but it produces the same result)
kalel
 
Posts: 258
Joined: Sun Jul 17, 2016 6:35 am

Re: What is new in the under development LuxRender v1.7 ?

Postby Dade » Tue Aug 30, 2016 9:25 am

kalel wrote:I don't know if this is at all related or not, but when I try to use RTPATHOCL as rendering (not preview) by using the custom parameters field, the screen is also black (and sample count per second is weird),
but only until the render is stopped. When I stop the render, I get the image.


LuxBlend has to call WaitNewFrame() at each screen refresh for RT modes or the end result is the one you described.
User avatar
Dade
Developer
 
Posts: 8354
Joined: Sat Apr 19, 2008 6:04 pm
Location: Italy

Re: What is new in the under development LuxRender v1.7 ?

Postby Dade » Tue Aug 30, 2016 9:27 am

Side note: while RTPATHCPU is slower than RTPATHOCL in term of samples/sec, its major advantage is that any scene editing operation is pretty much instant (and doesn't require any kernel recompilation for obvious reason).
User avatar
Dade
Developer
 
Posts: 8354
Joined: Sat Apr 19, 2008 6:04 pm
Location: Italy

Re: What is new in the under development LuxRender v1.7 ?

Postby B.Y.O.B. » Tue Aug 30, 2016 9:39 am

Dade wrote:LuxBlend has to call WaitNewFrame() at each screen refresh for RT modes or the end result is the one you described.

Cool, this works. Is there any harm if I call this with every engine? Should I do a check for "enginetype == RT..." before calling it?
edit: I looked into the sourcecode and since the default implementation is an empty function body, I think it's ok to omit a check.

I pushed a commit, so after you update LuxBlend you can test it.
Put something like this into the custom properties:
Code: Select all
renderengine.type = RTBIASPATHOCL
Last edited by B.Y.O.B. on Tue Aug 30, 2016 9:50 am, edited 1 time in total.
User avatar
B.Y.O.B.
Developer
 
Posts: 5131
Joined: Wed Nov 10, 2010 4:10 pm
Location: Germany

Next

Return to Architecture & Design

Who is online

Users browsing this forum: No registered users and 3 guests