IPR render bugs + numbers not inputting

VRay Version: vray_adv_43003_houdini18.0.416_3819bc8_7070_windows (just ripped from the zip file)
Houdini Version: H18.0.454

Firstly, when selecting a section in the main IPR view in houdini, it will render the entire frame, not just the selection. This is true for volumes and just geometry.

Secondly, when inputing numbers and such into the material fields (currently only tested on the VolumeGrid shader), it won’t accept anything if I use my main keyboard. I can only input numbers using the Numlock to my right, but the upper numbers won’t work, neither will delete or backspace.
This doesn’t happen until I actually fire up VRay.

Finally, not quite a bug, but still annoying. If I fire off a render in the IPR, then houdini will freeze completely until something actually shows up. This means if I hit render in the IPR, but forgot the change a value, I have to wait until the self illumiunation of a explosion has been calculated, which can take several minutes if I’m pushing high-res.

> not just the selection

which selection? ROP object lists? Viewport object selection?

> currently only tested on the VolumeGrid shader

So, does this happen only with volume grid? or in general?

> If I fire off a render in the IPR, then houdini will freeze completely until something actually shows up.

Well yes… stuff needs to be initialized…
You may try using VFB IPR (toolbar icon).

Ah yep, that’s my bad, I should have been way more specific.

So this happens with both the VFB and the default Render View window inside of Houdini. I am talking about the “Render Region” specifically, not the ROP object list or viewport list.
This means that if I want to render just a specific region to check my progress on a material, but also keep my rendering time low, it just won’t happen. It’ll render the entire scene, giving no thought to the render region.

I’ve tested this some more, and it takes some time before it sets in. If I open a new scene, and start laying down materials and such, it’ll behave fine. After I’ve done a few test renders, using either the Houdini built in Render View or the VFB, then the materials will stop allowing me to enter values in via my keyboard. I’ve tested this on a lot more of the shader nodes now, and can confirm this does happen.

For the last one, I can appreciate that some things need to be initialized, sending the stuff to the GPU memory \ RAM memory so that the renderer can easily use them. But I’ll be specific, and lets say I’m rendering an explosion.
If it’s just starting up the Render engine, that happens in seconds. If its sending files TO the render engine, that also takes a minimal amount of time. My main concern is that when rendering an explosion, and it has to calculate the self-illumination (I get the Houdini Console at all times, so I can see what’s happening), then I have to wait several minutes before the render happens. Thats fine, but whilst it calculates that illumination of the explosion, it also freezes Houdini. I feel it shouldn’t do that, when all the files should be loaded into the VRay renderer itself.
If that’s not what’s happening, please do let me know!

+1 for this, the only thing keeping me from using Houdini’s Render view.
Drawing a region holding down Shift, it still renders the entire frame. But the render region built into Vray’s frame buffer works

“Render View” crop support should be restored in the next nightly.

Thannks a lot!
Will be quite helpful :slight_smile:

@bdancer Hi Andrei

This works nicely in today’s nightly build. Thank you!

I needed to restart the IPR every time I draw a region, which is fine honestly.

> I need to restart the IPR every time I draw a region, which is fine honestly.

You mean now or before the fix?

It updates nicely after the fix :slight_smile: sorry for the typo
I’ve been playing with it for an hour now. To reset the region(to render the full frame) I use Shift + left click outside the frame. This doesn’t work now, even after restarting the IPR
Other than that, everything works perfectly