Hi,
I’m not sure if this is intended or not… I received a report from an artist who have issues with VRayScene nodes breaking after having optimized her scene by executing a “Delete history”.
Are you aware of any such issues?
Yes, in fact this exact should should have been fixed a few months ago already. What V-Ray version are you using? It was a problem with 3.30 and should be fixed in all builds starting 3.40.01 and later.
Are you sure thats vrscens Yolov?
It was fixed for proxies quite some time ago, but Im still having the same problem with vrscenes (imported through the vrscene manager).
Please give it a try and see if they dont break for you.
I did and I can’t delete history on a VRayScene node, we do the same locking as for proxies. But if it happens on your end, then something’s wrong. Can you show me a screen recording so I can see if I’m missing something?
Hrm, had to give it a try again, and I realized you are right.
But Im sure I’ve managed to break them a few times. So I did some testing, and if you freeze transform them, after that you can delete history on them and they break like before (with the file node being removed). I also noticed that just freeze transforming makes them not render right, even if you dont delete history on them afterwards.
Im not sure thats what happened here, and I dont remember freezing vrscenes on purpose. But atleast that kills it.
I didn’t think of that 
Thanks for the info, I’ll let the devs know.
Hi,
The artist here who had issues with this were using V-Ray for Maya 3.52.01.