Daily Builds 1.5

[maru]

Some tests with the new (not yet available) 1.5 daily build with improved displacement. Take a look at the stats. :)

1.4 vs 1.5, full hd resolution

2px - 01:17 vs 00:11
1px - 05:37 vs 00:47 (!!!)

Also it looks like the new displacement, apart from being much faster, is also more detailed in the distance.
You can grab the scene with stones here: https://www.dropbox.com/s/x734e1m754ct9es/caves03.zip?dl=0

PS. There is no single bump map used in that scene, it's all displacement.

[Ondra]

Some tests with the new (not yet available) 1.5 daily build with improved displacement. Take a look at the stats. :)

1.4 vs 1.5, full hd resolution

2px - 01:17 vs 00:11
1px - 05:37 vs 00:47 (!!!)

Also it looks like the new displacement, apart from being much faster, is also more detailed in the distance.
You can grab the scene with stones here: https://www.dropbox.com/s/x734e1m754ct9es/caves03.zip?dl=0

PS. There is no single bump map used in that scene, it's all displacement.

available now :D

[peterguthrie]

wow, those times are impressive!

also, the lens effects get a huge thumbs up from us. agree about changing the terminology to blades, but otherwise its already brilliant.

[Ludvik Koutny]

I am still not getting very good results out of glare and bloom. I mean on the one hand they create nice effect, but they still do not have that exponential falloff from the highlight, that would make them usable to cover up jagged edges, like on real photographs. Right now, you either have too strong glare, or glare with good intensity, but you still perfectly see the sharp pixelated edges around highlights. So when it comes to resolving jagged edges around highlights problem, it still doesn't work.

[romullus]

I am still not getting very good results out of glare and bloom. I mean on the one hand they create nice effect, but they still do not have that exponential falloff from the highlight, that would make them usable to cover up jagged edges, like on real photographs. Right now, you either have too strong glare, or glare with good intensity, but you still perfectly see the sharp pixelated edges around highlights. So when it comes to resolving jagged edges around highlights problem, it still doesn't work.

+1

[PROH]

Rawalanche just did a perfect description of my experience :)

So +1 for that.

[Ludvik Koutny]

Well, actually :D

I take that back :)

I had an older build, and reading through changelog, there was change to a glare. In latest build, glare works the way it should. It will eat into the edges of the highlight and smooth it out.

Now if only same happened with bloom, it would be awesome :)

[Christa Noel]

congrats for superb displacement!! I love it
but just so curious and can't wait anymore... When will the DB with DR improvements released? ;)
edit:
what about multilight.. does it do like what maxwells multilight do or just render elements like the other do?

[romullus]

Probably not a bug, but it's worth noting that while general materials transfers well to dailies with fixed glossiness, shadow catcher renders significantly differently when reflection is enabled . Most likely due to absent legacy mode.

[romullus]

Or maybe it's a bug afterall, because on transfer to newer builds shadow catcher's glossiness spinner gets changed, but glossiness value in rendered picture still doesn't match. And that conversion is rather strange.

Gloss value:
OLD -> NEW
0,9 -> 0,9542
0,8 -> 0,913
0,7 -> 0,8337
0,6 -> 0,7014
0,5 -> 0,6613
0,4 -> 0,6613
0,3 -> 0,6613
0,2 -> 0,6613
0,1 -> 0,6613
0,0 -> 0,6613

Edit: tried to convert values manually by table available in converter and it works almost perfectly, so this definitely is a bug. Can do proper report on mantis if needed.

[fobus]

It seems that bloom and glare effects are not being saved with network rendering. I can't get it saved with backburner job on nodes.

Update: Looks like this node having trouble with saving image with effects. Investigating it.

Update 2: Looks like it is not saved at all. If I render sequence there are no effects saved in file. 3ds max 2014

[aylama]

Some tests with the new (not yet available) 1.5 daily build with improved displacement. Take a look at the stats. :)

1.4 vs 1.5, full hd resolution

2px - 01:17 vs 00:11
1px - 05:37 vs 00:47 (!!!)

Also it looks like the new displacement, apart from being much faster, is also more detailed in the distance.
You can grab the scene with stones here: https://www.dropbox.com/s/x734e1m754ct9es/caves03.zip?dl=0

PS. There is no single bump map used in that scene, it's all displacement.

It is great news!!!!!

and RAM at high resolutions with displacement? It is our biggest problem... We need a  hight detailed displacement on images of 5000px, RAM  in these cases is excessive...

[maru]

It seems that bloom and glare effects are not being saved with network rendering. I can't get it saved with backburner job on nodes.
Update: Looks like this node having trouble with saving image with effects. Investigating it.
Update 2: Looks like it is not saved at all. If I render sequence there are no effects saved in file. 3ds max 2014

It might be this: https://corona-renderer.com/bugs/view.php?id=2033
So we need to wait for the fix.

[VASLAVO]

proxys with displacement crash 3dsmax, tested on 2017 with daily build 07-28-16

[pokoy]

Just came across a potential bug:
In IR, mode when I render through a camera every scene change takes a few seconds to update the render view, for example HDR environment rotation. If I switch to perspective view, IR updates immediately. Happens on quite a big scene, so some lag is expected, but this definitely smells like a bug.
The camera is a Physical camera, not sure if it happens with a standard camera, too.

Daily build from Jul 12 2016, Max 2016.