Production render in IPR mode

[vlado]

@mnewberg

I assume object and node property changes are yet to be implemented?

Sure; I did say it’s a WIP

Best regards,
Vlado

[vlado]

@glorybound

Would be nice if render settings could be changed on the fly too. The less restarts, the better Especially in bigger scenes that can take two or three dozens of seconds to translate. Most of the render settings, except for a few in system rollout, shouldn’t really require complete re-translation of scene. And even if they do, it would still make more sense for IPR to just re-translate entire scene to make the change happen, rather than silently fail.

Yep, for sure - this is on the “to do” list as well.

Best regards,
Vlado

[Nicinus]

Hmm, I guess the choice between spending the money on CPUs or GPUs just got even harder.

[M.Max]

That’s a killer feature for me! We almost decided to look into c* renderer for this specific feature here at our studio.. But not anymore! =D.
Is it planned to be implemented in the next SP (if there is any SP before V 4.0? ) or it is too early to talk about that :).

[vlado]

It will be in the next SP (V-Ray 3.5)

Best regards,
Vlado

[Nicinus]

Vlado,

Does this effectively replace the Vray RT CPU mode?

If so, I assume this could also mean speedier development of Vray RT GPU as the focus is now clear for that team.

[vlado]

@KELPER

Does this effectively replace the Vray RT CPU mode?

Yes, pretty much.

If so, I assume this could also mean speedier development of Vray RT GPU as the focus is now clear for that team.Yes, this gives us more freedom on the GPU side as we will no longer be bound to implement things *exactly* as on the CPU and instead we can focus on making the GPU renderer better in its own way.

Best regards,
Vlado

[AndresAhumada]

Hi vlado…

When is the release date?

[vlado]

@ricoholmes

When is the release date?

In a few months towards the end of the year, but we will probably do a few beta releases first to get some feedback like we did last year with the 3.3 release.

Best regards
Vlado

[Nicinus]

@ArnaudT

In a few months towards the end of the year, but we will probably do a few beta releases first to get some feedback like we did last year with the 3.3 release.

Great work, guys! Really super happy about this, a game changer! Now if we could apply the same technology to the material preview also?

[Mennovandijk]

@ArnaudT

In ActiveShade, we are using V-Ray RT, which is in fact a completely different renderer than the regular V-Ray one. While both of them work very similarly with the same rendering core, the shaders are different - f.e. procedural textures are slightly different, 3rd party texture plugins do not work in V-Ray RT etc. With this new implementation, the interactive rendering is done by the regular V-Ray renderer itself, so the result matches 1:1 your final render.

Best regards,
Vlado

Thanks! Looking forward to the new updates and implementations

[Art48]

Oh my god, it’s happening! Looking forward to it! Don’t let us down (I don’t think you will), I appreciate you guys for doing stuff right, and not half-a**ed like some other software developers we know.

[Nicinus]

@ArnaudT

In a few months towards the end of the year, but we will probably do a few beta releases first to get some feedback like we did last year with the 3.3 release.
Best regards
Vlado

When can we hope for this to show up in the stable builds?

[vlado]

@Brendan_Coyle

When can we hope for this to show up in the stable builds?

This will be included in the 3.5 stable builds as we get closer to the release of the 3.5 service pack in a few months. It won’t go into the 3.4 stable branch, as it will immediately stop deserving the “stable” label.

Best regards,
Vlado

[Dave_Wortley]

@Phantom-Studio

Oh my god, it’s happening! Looking forward to it! Don’t let us down (I don’t think you will), I appreciate you guys for doing stuff right, and not half-a**ed like some other software developers we know.

Don’t forget that it was the half-a**ed software developers who made the new 2017 render API that the IPR Rendering is being built on.

[Moriah]

@snivlem

Don’t forget that it was the half-a**ed software developers who made the new 2017 render API that the IPR Rendering is being built on.

I think he’s talking about OTOY

[Nicinus]

@snivlem

Don’t forget that it was the half-a**ed software developers who made the new 2017 render API that the IPR Rendering is being built on.

How so? Vlado stated above that this will be implemented in earlier versions as well once things become more stable.

[Dave_Wortley]

@mikeh

How so? Vlado stated above that this will be implemented in earlier versions as well once things become more stable.

And it will be a lot more work for Vlado to make this work in 2016 and before than it was with 2017.

[Sbrusse]

That’s a shame
we are planning to upgrade to 2016 from 2014 in few weeks/months, we wont go on 2017 before at least 2 years as we never go for new releases in production

[vlado]

@Neilg

That’s a shame
we are planning to upgrade to 2016 from 2014 in few weeks/months, we wont go on 2017 before at least 2 years as we never go for new releases in production

Don’t worry, it will work fine for older versions too.

Best regards,
Vlado