Referencing scene with vraySettings

[madcrew]

We have problem when we try to reference a scene that has a vraySettings node in it.
The problem occurs when the scene we reference it into also have a vraySettings node.
One workaround for the moment is to delete the line lockNode -l true; in the Maya Ascii scene file the causes the trouble.

We are on Ubuntu 9.04 64bit, Maya 2009 SP1 64bit. Vray 1.50

www.madcrew.se/media/floorLamp_01.ma.zip

If you create a new scene and make sure you get a vraySettings node by render with vray.
then try to reference the linked scene. The scene shows up but it's corrupt, no shaders assigned etc.

Thanks in advance
/Fredrik

[jensl]

I'm working in XP 64 and when I have a scene with a native vraySettings node and reference a scene that also has a vraySettings node things work fine, and the namespace:vraySettings doesn't appear in the outliner anywhere. My create reference options have shared nodes on, and render layers checked.

You can always unlock any node by selecting it and doing a "lockNode -lock off;" command. Then it can be deleted or renamed or whatever. This might be a linux issue, though.

[madcrew]

Thank you. The shared node option didn't do it.
The workflow for now is to run a cleanup script when saving scenes that need to be referenced.

[shadevfx]

This came up for us today too. We are in a windows vista 64 environment. We noticed that when we initially reference a vray scene with a vraysettings node in it, it comes in fine. But once you hit save, the scene gets bunked, shaders drop, etc. And you can no longer reference anymore of those objects. Since we publish assets as MA, we just had to comment out (or delete) the line "lockNode -l 1 ;" after the vray settings node in the referenced object. Just confirming that this a workaround and that it's not strictly Linux related.

[vladimir.nedev]

The locking of the vraySettings node was implemented so that the user cannot accidentally delete it. It seems it creates more trouble than it solves though. So I've removed it for future builds. Older scenes will still have it locked unfortunately.

Greetings,
Vladimir Nedev

[Morbid Angel]

perhaps its worth looking at how mental rays global node solves this problem.

[vlado]

perhaps its worth looking at how mental rays global node solves this problem.

I'm not sure it does anything specific to avoid this either...

Best regards,
Vlado

[shadevfx]

its actually really handy to be able to show all nodes and delete the MR globals (renderman too). Sometimes they get corrupt, sometimes you switch renderers and want a clean scene...

they're buried enough that you probably wont kill them accidentally... without turning off show DAG objects only, you wont see them.

just a thought...

B

[jensl]

I don't suppose it's possible for something in between locking (since unlocking is a bit of a pain), and no lock at all, where you've got nodes that are rather essential that are easy to delete. A delete confirmation dialogue pop up or something?

[Morbid Angel]

I'm not sure it does anything specific to avoid this either...

Best regards,
Vlado

here is what happens with mr when you reference a scene a couple of times:

2009-10-16 19:00:49.38 - Warning: file: Rig_REF_065.ma line 558657: 'miDefaultOptions.message' is already connected to 'mentalrayItemsList.options'.
2009-10-16 19:00:49.38 - Warning: file: Rig_REF_065.ma line 558658: 'miContourPreset.message' is already connected to 'mentalrayItemsList.options'.
2009-10-16 19:00:49.38 - Warning: file: Rig_REF_065.ma line 558659: 'Draft.message' is already connected to 'mentalrayItemsList.options'.
2009-10-16 19:00:49.39 - Warning: file: Rig_REF_065.ma line 558660: 'DraftMotionBlur.message' is already connected to 'mentalrayItemsList.options'.
2009-10-16 19:00:49.39 - Warning: file: Rig_REF_065.ma line 558661: 'DraftRapidMotion.message' is already connected to 'mentalrayItemsList.options'.
2009-10-16 19:00:49.39 - Warning: file: Rig_REF_065.ma line 558662: 'Preview.message' is already connected to 'mentalrayItemsList.options'.
2009-10-16 19:00:49.39 - Warning: file: Rig_REF_065.ma line 558663: 'PreviewMotionblur.message' is already connected to 'mentalrayItemsList.options'.
2009-10-16 19:00:49.39 - Warning: file: Rig_REF_065.ma line 558664: 'PreviewRapidMotion.message' is already connected to 'mentalrayItemsList.options'.
2009-10-16 19:00:49.39 - Warning: file: Rig_REF_065.ma line 558665: 'PreviewCaustics.message' is already connected to 'mentalrayItemsList.options'.
2009-10-16 19:00:49.39 - Warning: file: Rig_REF_065.ma line 558666: 'PreviewGlobalIllum.message' is already connected to 'mentalrayItemsList.options'.
2009-10-16 19:00:49.39 - Warning: file: Rig_REF_065.ma line 558667: 'PreviewFinalGather.message' is already connected to 'mentalrayItemsList.options'.
2009-10-16 19:00:49.39 - Warning: file: Rig_REF_065.ma line 558668: 'Production.message' is already connected to 'mentalrayItemsList.options'.
2009-10-16 19:00:49.39 - Warning: file: Rig_REF_065.ma line 558669: 'ProductionMotionblur.message' is already connected to 'mentalrayItemsList.options'.
2009-10-16 19:00:49.39 - Warning: file: Rig_REF_065.ma line 558670: 'ProductionRapidMotion.message' is already connected to 'mentalrayItemsList.options'.
2009-10-16 19:00:49.39 - Warning: file: Rig_REF_065.ma line 558671: 'ProductionFineTrace.message' is already connected to 'mentalrayItemsList.options'.
2009-10-16 19:00:49.39 - Warning: file: Rig_REF_065.ma line 558672: 'ProductionRapidFur.message' is already connected to 'mentalrayItemsList.options'.
2009-10-16 19:00:49.39 - Warning: file: Rig_REF_065.ma line 558673: 'ProductionRapidHair.message' is already connected to 'mentalrayItemsList.options'.
2009-10-16 19:00:49.39 - Warning: file: Rig_REF_065.ma line 558674: 'miDefaultFramebuffer.message' is already connected to 'mentalrayItemsList.framebuffers'.