(done, open) [HOU-1965] [HOU-2032] IPR node

[david.anastacio]

Hi,

The use of the IPR node has generated quite a bit of confusion with new users here, and I can totally get the issue from their perspective.
The issue being that users need a separate IPR node for each Vray render node, or they have to change the render path in the IPR node, and most times the Vray render nodes don't have an IPR, so they can't get the IPR render started. Can't the Vray render node just generate an IPR output by itself? This would make things much easier. Or is there a technical reason to do it this way?

Best,
David.

[chakarov]

I've added your request as HOU-1965, and will write you once I have more information if integrating IPR into the V-Ray ROP itself is possible.

[david.anastacio]

chakarov, that's great, thanks

Best,
David.

[chakarov]

Hello david.anastacio , starting with today`s builds, when V-Ray ROP is created, an IPR one is automatically created and linked to it.

[david.anastacio]

Hi,

Thanks for the update chakarov, but I have to be honest here, wasn't expecting this was going to be the solution. This is not really what I was asking for and I don't see this solving the issue at all.
Artists add the render node to the scene maybe once, all nodes after the first one are just copied from that first one (this saves them time setting up the ROP again from cratch, plus is just faster do copy), so the confusion with the IPR node will continue....

I'll ask again for what I had in mind; is there any reason to have an IPR node in the first place? Can't just the VFB render IPR/Production from the same ROP node? Just like other renders do it, this would help a LOT the artists. Maybe I run the danger of saying something stupid now, but could't you just hide the IPR node (in case you really need to have it in a seperate node from the ROP) inside the V-Ray ROP? And make it's name the same as the parent.

Best,
David.

[bdancer]

> is there any reason to have an IPR node in the first place?

Yes, there is. This is the only way to have IPR. ROP_Node class which is the base for ROP nodes can't be used for IPR.

[david.anastacio]

Thanks for the clarification bdancer. I guess I'll just have to keep reming artists about the IPR nodes

[bdancer]

We'll try to think of some fix for existing scenes.

[david.anastacio]

bdancer thanks for looking into that.
Maybe the solution could be to just create the IPR node when trying to start it, if there is non on that VFB, just create one. Either through the IPR shelf button of IPR VFB button.

Best,
David.

[Gosho.Genchev]

Maybe the solution could be to just create the IPR node when trying to start it

Hey David,

an IPR node is always created when you create a Renderer ROP. Does that not work on your end ?

[david.anastacio]

Artists add the render node to the scene maybe once, all nodes after the first one are just copied from that first one (this saves them time setting up the ROP again from cratch, plus is just faster do copy), so the confusion with the IPR node will continue....
.

From my post before Gosho.Genchev.

[Gosho.Genchev]

Hey David,

yeah, I didn't actually understand the problem because an IPR ROP is also created if it's not present but seeing that you have multiple Renderer nodes, I see how that could be an issue.

A straightforward solution on our end would be to list the Renderer ROPs when you Shift + Left Mouse click on the IPR (VFB) button on the shelf. Right now the menu that shows up will list IPR ROPs but we could list the Renderer ROPs instead, and create a IPR ROP for the selected Renderer if there isn't one present already.

Would that work for you ?

Best regards!

[david.anastacio]

Gosho.Genchev, that sounds ylike a great solution.