non-existing camera doesnt throw errors when rendering...

[jurweer]

Hi guys,

we were in a fix mode on some shots today and bumped into a weird issue.
we had to recreate a ROP node and change all the values per hand, but forgot to write the correct camera in the rendercam entry.
it automatically fills in cam1 when a new ROP is created, which doesnt exist in our scene.

when the job rendered on the farm it rendered 20-30+ minutes (10% finished) instead of 2-3 minutes per frame. there was no print about a possible error, in this case the non-existing camera.

obviously, i should have added the correct camera in the first place, however an error message, to make any debugging go faster, would be very nice to have.
a check on vrscene export that the camera that is in the entry exists would be even more awesome!

thanks!

[bdancer]

There is no camera check for export (there was such a check before) because of a user request that wanted exactly the opposite - export scene without camera without error message window shown.
I'm not sure how to resolve that for you...

[jurweer]

bdancer thanks for the fast reply. seems a bit odd that a scene renders with a non existing camera and there is no print or error about that.

also, that user request seems rather specific, could that easier to tackle with a checkbox when the export menu is selected saying 'export without camera'... and keep a (in my view) common thing as a camera check in the ROP?

[bdancer]

Scene will not render with non-existing camera, this check is skipped only for vrscene export.

[jurweer]

ah ok, I have seen that when rendering in Houdini.
It would be nice to have some sort of warning or print in the log to find out what is happening when exporting/rendering a vrscene sequence with a camera that doesn’t exist.
besides that it would prevent user errors, it would help a lot with debugging.