Error after upgrading to 6.1

V-Ray V-Ray for 3ds Max Issues
1

After updating to the newest Vray yesterday I got this on the small file I was working on:

image.png
image.png1225×802 37.7 KB
​

I am thinking I will try reverting to the previous hotfix but thought it should be logged. It is a linked Revit file if that helps. If I continue with the load the object box on the right stays crossed out.

2

I have the same issue when i am using window 11, after revert it to window 10, no more issue like this

3

Dear @Sawyer , hello.

It will be interesting to consider this an issue related to V-Ray, but we are here to help.
In general looks more like a 3dsMax related question.
Please take a look at this Autodesk forum thread, the discussion and the provided solution.

I have made a quick test with V-Ray 6.01 with Revit file linked and everything is well working.
Since you have pointed this out, is it happening only when trying to link Revit files?
After looking at the linked above information and trying the recommended, please share is everything back to normal.

Waiting for your answer.

Best regards,
TS

4

So … I just got a new CPU and this was the first file I created with it. It happened right after the Vray upgrade to 6.01 but looks like its still an issue after reverting. I will look into the solution posted to the Max forum that was posted.

5

I have had this happen when importing older models. Of course, deleting my MAX ENU was the solution, which seems to be all of MAX’s problems.

6

Thanks Bobby - I did try that but no change. Having IT look into it. So far its stumped them…

7

Happend to me again today. I don’t think it is a V-Ray thing. It is a MAX sucks thing.

8

Hi again,

You could awaken the already mentioned Autodesk forum thread or start a new one and share a link here.
It will be interesting to follow the progress there, since the issue is more related to the host platform.
Fingers crossed for you to get it solved soon. I could not be more helpful at the moment…

9

Yea, that is a dead end street. You read things all over the internet, post the issue on the AD forum and they act as if they never heard of it and it is something we did to MAX. However, I agree, it is a MAX issue.