Multiple views - elements naming problem

[billboggins]

Hi,

I could be overlooking something very simple here but I have an annoying problem when I’m saving multiple renders their elements from the same scene (i.e. multiple camera angles in one model).

So for example: I have a model set up and ready to render with 2 cameras in it. I will be using Rebus to render them so tick the main render output save function and set the path/filename. I select the elements I require and their file paths/names match the main render output. I upload and all is fine. I then go to camera 2 and rename the main output filename to Cam2. However, when I look at my elements, their file paths and names are still for Cam1. Meaning the original Cam 1 elements would be saved over by Cam2. I have to either manually change all the file paths and names for each element, or delete them and then re-select them. I often work with multiple camera angles and it gets very frustrating every time I want to automatically save the files out.

Someone please help. Hopefully it’s just something very simple I’m overlooking!

Thanks in advance.

B

[Frood]

The "trick" is to not touch the filename in the RE window at all, only the elements name. Once you change the filename manually it does not react dynamically to the output name any more.

Good Luck

[djc501]

The "trick" is to not touch the filename in the RE window at all, only the elements name. Once you change the filename manually it does not react dynamically to the output name any more.

Good Luck

Thanks for the reply, but this is happening without editing the render elements name at all  - the only thing that is changing is the main save location under Common - Render Output.  When this changes the render elements don't.  This appears to be the same problem in the post I made earlier.
https://forum.corona-renderer.com/index.php/topic,13831.0.html
We're aware that manually editing the location of the render element can break the link, but if the link isn't there in the first place, it seems like the only option.  As an aside, we never had this problem when using Vray, which makes me think that it's an issue with Corona.

[maru]

I just checked this with Max 2016 and Corona 1.5.1 and it seems to work fine. After I change the output path, the elements are changed accordingly - both their paths file names. That's really odd.

[Frood]

Yes.. no idea. This should at least not happen with a fresh scene (reset) or/and new created render elements. If so, you may attach such a (almost empty) scene here for investigation.

Good Luck

[matsu]

I have the same problem. And it's a very odd behaviour, to say the least, beacuse it's not easy to reproduce.

If I make a new scene, and add elements, it works correctly - the names update.
If I open an old scene, and add elements, it works correctly.
If I, in a scene where the problem exists, remove all the elements, and then create new ones, it works correctly.

Seems that somehow, sometimes the naming just gets stuck, and remains stuck unless you make new elements.
Removing the element name alltogether, fixes the problem for the current session, but the faulty names are reinstated as soon as you open that scene.

I have no clue how to fix it, other than creating new elements when the problem appears.

[maru]

Are you sure that this never happens when using Vray or some other renderers? Only when using Corona? It sounds like some general 3ds Max issue. Anyway, removing and re-adding elements seems to do the trick, right?

[matsu]

Been using Vray/Max2016 since max2016 was realeased, and never had that problem. With Corona, I have the same problem on two completely separate machines. Same Max/Corona versions on both machines.
I just looked into Vray, and they use their own "save-file" dialogue, so the render elements never have an output path attached to them. They completely bypass the 3dsmax dialogue. Maybe this is why it also always worked?

But yes, removing and re-adding the elements seem to work atm. Only a little tedious having to set up Z element range, Masking properties etc every time. It may also cause problems when submitting multi-frame jobs, when you can't manually reset the elements.