I think I finally found the issue. The 3dsMax option "Save strings in legacy non-scene files using UTF8" causes some invisible bytes to be written to the DR config file and the server address becomes invalid. Try disabling this option.

Announcement
Collapse
No announcement yet.
Live link and render animation don't work
Collapse
X
-
That's great!
There is another issue that may or may not be associated with this. When I send an animation to Vantage the GI and ambient light settings reset to default and I can't change them. I've tried setting these new settings as the default settings but I get a message saying "Failed to write settings". The only way I can get the settings to stick is to do an initial animation export, abort it and leave the VFB open, change the settings and send the animation again without closing VFB.
Comment
-
It's strange that you get "Failed to write settings". This should happen if you don't have write permissions for the folder %APPDATA%/Chaos Group/Vantage . Can you create files there, without getting prompted for administrative access (it's a user folder)? Is there a debug_log.txt file there?Nikola Goranov
Chaos Developer
Comment
-
Hmm, does %APPDATA% resolve to user/AppData/Local in your case? For me it's in user/AppData/Roaming. This Vantage folder normally contains up to 3 files - debug_log.txt, vantage.ini and defaults.vantage. The first two are created/saved every time you run Vantage. The "defaults" file is the one you're trying to save. It looks like for some reason Vantage fails to save any of those on your machine.Nikola Goranov
Chaos Developer
Comment
-
Ok I see it, here's the log and yes I can create new files in this folder also.Attached Files
Comment
-
So apparently until now the file defaults.vantage was being created with the Read-Only attribute. I've fixed this for the patch that we should release tomorrow. You can also fix it yourself today by removing the read-only attribute from the file.
Thanks for reporting this bugNikola Goranov
Chaos Developer
Comment
Comment