Since moving to 2026 Vray 7.2 we are having issues connecting to our network server. At first Cosmos would not allow saving to a network path, however that was solved with the DB del fix which works as long as a previous version of cinema isn’t booted. We also cant save out proxy objects/files, which we were have been doing by running a second instance of 2025… For whatever reason we can save out vrscenes to the network server. And we can clearly save out scene files so it isn’t the new Cinema.
Any help?
Can you please check your proxy export settings? Does the export selection parameter have a value? It was missing a default value previously which could completely break vrmesh export.
This is what ours looks like. - Looks like you are on an older version of cinema. We are on 2026 7.2 Windows 11
This was an older version of Cinema4D, however, your screenshot does look like a symptom of the same problem I described. This was fixed recently in our internal builds and will be available in our stable builds really soon.
Actually never mind, the fix is already available in our 7.2 stable builds here Chaos
Note that you may still need to manually change the Export parameter that I have highlighted above.
Thank you.
vray_adv_72000_c4d2026_dr2_x64_stable_33568 - didn’t work
vray_adv_72000_c4d2026_dr2_x64_stable_33561 - this older one does work however
Thanks again!
I ran into something similar before, and in my case it turned out to be a file permissions/path issue rather than the proxy itself. It might be worth trying a different output location with a simple folder path and checking if any special characters or network locations are involved. Sometimes that narrows it down pretty quickly.
