IPR not updating with camera changes - also camera blur not working

[fixeighted]

This is coming from tests in the separate topic about long exposure motion blur.

IPR does not update at all when changing motion blur settings - using cpu. It needs to be stopped and restarted after each change.
Once changes are made it will update when scrubbing timeline.

IPR under GPU does not update properly either with blur settings changes - and worse than cpu, as with no changes made it will reset when scrubbing timeline, as if no blur is there.

Camera motion blur does not work at all with cpu. It does with GPU but with the above issue of resetting as if there was no blur activated.

[kosso_olli]

Both issues have been reported in the past. Seems they never got fixed.

Camera motion blur does not work at all with cpu. It does with GPU but with the above issue of resetting as if there was no blur activated.

The camera motion blur is working in CPU, but it does not work in IPR:
https://forums.chaosgroup.com/forum/...y-wrong-result

IPR does not update at all when changing motion blur settings - using cpu. It needs to be stopped and restarted after each change.
Once changes are made it will update when scrubbing timeline.

You still need to update manually
https://forums.chaosgroup.com/forum/...-t-get-updated

[fixeighted]

LOL....unbelievable really. Thanks for letting me know.
To be honest I am not surprised that I didn't realise/check, with all the issues here and there, it is hard to keep up

EDIT: Just checked those posts you linked....really old. I would have thought something like camera functionality would be a priority.

I wonder why it all just works in Corona...I mean, If I had a job right now that I needed to use mblur on, there is no way
that I would even look at Vray to do it, after the chaos of the last few days testing (which I am so glad I did).
It's simpler to buy a month of something that works as expected for this (sorry Chaos, Vray is great...but) for 24 quid and save on the stress and non-results

[kosso_olli]

EDIT: Just checked those posts you linked....really old. I would have thought something like camera functionality would be a priority.

To be honest, I do not care anymore. Packing up scenes and sending them to support takes us quite some time, too and there are so many issues or ideas I reported which never get adressed. Thing is I keep losing track of all the stuff I reported, because there is the daily work which keeps me from doing so. But with Covid and a few hours a day at hand, I can spend more time doing that. Also thankful for any user who has the same problem as me, like the ground projection issue which took 8 pages to debate.

All of this is also the reason why we did not upgrade to 5 yet. No errors fixed, but costs go up and up.
And I do have to say: By looking at the alternatives, it seems I miss a lot in terms of features and ease of use. For us, it is artist time that costs the money, not the rendering itself. So if there is a way to cut costs, it is artists spending less time fiddling around with non-working features.

[fixeighted]

For sure, Vray is awesome and I have no desire to change. Other things do suffer from issues also.
It's just that I like results and getting them quickly is crucial, as I am sure we all would agree.
I don't mind being wrong about stuff and being shown how to do something I thought wasn't possible in Vray, but so far
that's not coming from the devs in this case.
So I revert to the the principle of 'whatever gets the job done'

Without wanting to be harsh, I think Chaos has grown from being just Vray to all the other things it now is, with all the competing
drains on resources; they are stretched. I might be wrong, or it may be a case of
'it'll get fixed if/when there is sufficient call from users to make it a priority'.

If most people just want to point a camera and output a pic of a house or an object, which to be fair is much of what I now do, then there's little impetus to
implement a more capable camera model for vfx or other more demanding purposes.
But then, as I say, with this particular thing Corona just works, so not sure where the trickiness lies in updating it in Vray.

[nikoleta.garkova]

Hi guys, we're indeed aware of the issue and it has been logged in our system under ID nr.: VMAX-9364. I will make sure to bump its priority and notify our devs about this discussion. Thanks for the patience!

[fixeighted]

Thanks but please also have a look at the other motion blur discussion
I've been testing this for days along with Oliver but nobody has really added to it from your side

Interestingly I just discovered that by dragging the timeline, after changing something, it will actually force an IPR update on cpu without having to restart, so that's something.

LOL I am beginning to feel like a beta tester

Work is a bit Covid slow here - you wanna employ me to update your docs maybe?

[kosso_olli]

Hi guys, we're indeed aware of the issue and it has been logged in our system under ID nr.: VMAX-9364. I will make sure to bump its priority and notify our devs about this discussion. Thanks for the patience!

Which issue specifically: The IPR not being updated when changing shutter values or the camera motion blur not working with IPR?

[Joelaff]

As cool as IPR is, it is very buggy and inconsistent. I still find myself doing regular test renders much of the time.