OctaneRender™ 2019.1 XB1 Tweet

[divasoft]

Hi, I can't run app. Anybody knows what happened? I have v4 lic.

[shaddam]

Working wonderfully so far, here are a couple of tests and a video of the new denoiser

64 samples for both :





Thanks for the hard work

video : Noise test with Raw - Denoise w/ non-static noise - Denoise w/ static noise - Raw w/ neat video

[rohandalvi]

This is a great release. Love the vertex displacement and the new camera. Really nice work. Haven’t tried the layered shader as yet.

Is there an example of what kind of maps are needed for distortion and aperature in the new camera node?

And would it be possible to add noise maps to the density of volumes. I know it can get slow but it would be really useful.

Regards
Rohan.

[Notiusweb]

Finding the Displacement doesn't work right, as if the node is inactive/broken.
Texture-type works fine at first, but then goes dead after you change values.
Vertex, and Vertex Mixer, do not outright work at all.
Also noticing that Vertex does not have a "Level of Detail" Enum Value node, like the Texture Displacement has.
And, the default Height Value for displacement is "1.00"....wouldn't it be like .001 or something smaller, right?

Did you subdivide the mesh that you are trying to displace?. Vertex displacement doesn't need the level of detail pin. For most of the vector maps, the height scale will be set to 1, so I thought that would be ideal, but for the height map we need to tweak.

Hi,

Default Height-
I initially just was noticing compared to prior versions. 2018 has at "0.001", which works good for Texture Displacement, because I find often when I move values closer to "1.00", often that will bust up the mesh pretty severely displacement-wise, which, I rather enjoy actually...
but it sometimes is too extreme where it can stall the app because it is heavy duty processing wise, I guess.
So in 2019, the height is "1.00" for *both* Vector and Texture Displacement. Maybe if it was tweaked, say, "0.001" for Texture and then it would be "1.00", for vector, we wouldn't ever notice it.

Vector resolution-
Sometimes on a traditional texture displacement you might have different resolutions, so you might want it selectable at different sizes to achieve a different effect....
thought this might be the same for vector, but if by nature the vector is displayed at a max resolution (like as in "vector in Illustrator" vs "Photoshop raster") I see what you mean then.

2018 vs 2019-
The most important thing actually was that displacement overall doesn't work in 2019, as in if you do, say, set a texture displacement in 2018, and then set the same in 2019, the 2018 works and resets the render correspondingly when you modify any values, but not the 2019 one....so it's like the 2019 appears broken.

Thanks!

[VVG]

Dear all,
In the mean time, we look forward to your feedback on this release. If you have a V4 license or an all access subscription, you can test 2019.1 XB1 until the first stable release.

Please ensure that you have a NVIDIA driver version 419.x or newer.

.

v4 regular license dont work?

[linograndiotoy]

The new Displacement works beautifully, at least with procedurals and projections.


https://www.facebook.com/groups/OctaneR ... 573878685/

Finding the Displacement doesn't work right, as if the node is inactive/broken.
Texture-type works fine at first, but then goes dead after you change values.
Vertex, and Vertex Mixer, do not outright work at all.
Also noticing that Vertex does not have a "Level of Detail" Enum Value node, like the Texture Displacement has.
And, the default Height Value for displacement is "1.00"....wouldn't it be like .001 or something smaller, right?

Did you subdivide the mesh that you are trying to displace?. Vertex displacement doesn't need the level of detail pin. For most of the vector maps, the height scale will be set to 1, so I thought that would be ideal, but for the height map we need to tweak.

Hi,

Default Height-
I initially just was noticing compared to prior versions. 2018 has at "0.001", which works good for Texture Displacement, because I find often when I move values closer to "1.00", often that will bust up the mesh pretty severely displacement-wise, which, I rather enjoy actually...
but it sometimes is too extreme where it can stall the app because it is heavy duty processing wise, I guess.
So in 2019, the height is "1.00" for *both* Vector and Texture Displacement. Maybe if it was tweaked, say, "0.001" for Texture and then it would be "1.00", for vector, we wouldn't ever notice it.

Vector resolution-
Sometimes on a traditional texture displacement you might have different resolutions, so you might want it selectable at different sizes to achieve a different effect....
thought this might be the same for vector, but if by nature the vector is displayed at a max resolution (like as in "vector in Illustrator" vs "Photoshop raster") I see what you mean then.

2018 vs 2019-
The most important thing actually was that displacement overall doesn't work in 2019, as in if you do, say, set a texture displacement in 2018, and then set the same in 2019, the 2018 works and resets the render correspondingly when you modify any values, but not the 2019 one....so it's like the 2019 appears broken.

Thanks!

[divasoft]

-

[rohandalvi]

A couple of question/thoughts regarding the new camera.

1. Is it possible to achieve chromatic abberation or can it be implemented? Even if it's a little slow to render it would be great to have that as an option.

2. Is it possible to implement optical vignetting? It would allow for a proper cats eye type bokeh.

I think those are probably the only two options missing from the new physical camera.

I love the new Abberation and distortion mode. The parameters are a little technical but the look is great. I'm reading online to understand what they actually mean.

But currently the focus in the Abberation and distortion mode seems to be locked to auto focus. The Focus depth value does not work.

regards
Rohan

[cmittenaere]

Thanks, but I can't test it with my v4 license ... I think it's work with all access in contrary to the description.

[review.architecture]

I would really like to test, as in any software, this last version - seems awsome!
I'm on a regular V4 License and considering upgrading.
At the moment only Studio subscription can test.
I could buy 1 month but it would be nice from Otoy to let V4 customers test the beta version.

Thanks

M