VRay 5 for Rhino 7 fails to load some proxy objects

VRay 5 in Rhino 7 fails to load some vrscene proxy objects.

I have already imported some proxy vrscene objects.
Some were exported from 3ds Max and the others were exported straight from Rhino.

After, I’ve exported one more object from 3ds Max but it repeatedly fails to load.

Here is the vrscene for that object.

Rerna_Micro.rar (735.7 KB)

After I’ve tried importing some objects from previous projects made with Rhino 6 and VRay Next and VRay 5.
Some of them import without a problem, but some fail to load.

Rhino 6 and Vray 5 import everything without problems.

Thank you for reporting this. The issue will be investigated.
As a temporary workaround, please import the vrscene file by creating a Proxy Scene using the Asset Editor. Make sure to set its Preview Type to ‘Bounding Box’ and its preview object will appear in the Rhino 7 viewport.

Kind regards,

1 Like

Yes, it’s a workaround.

Thank you, but… you know… :smile:

Waiting on the fix.

I know. I am sorry about the inconvenience.
A solution is now scheduled for the next update (v5.1).

Kind regards,


With 5.00.2 even more import stuff is broken.

vrscenes that I could import before when I made this thread, cannot be imported now.

With these, it doesn’t say that the proxy object failed to load, they get listed, but they are nowhere to be found. - ‘‘select object in scene’’ doesn’t select anything.

Hello @ANDhitecture

I went through the same issue you are having, it seems to be Vray 5 is having a problem displace certain mesh topologies in rhino 7 viewports. my solution works for me as follow

in 3DS MAX
1- Select the object you are including in the .vrscene.
2- Apply “Subdivide Modifier”
3- Apply “Optimize Modifier”
4- Apply “Edit Mesh” Modifier
5- export to .vrscene.

This should Generate a mesh with less trouble, and worked for me when I imported it to rhino.

1 Like

Thanks for the tip.

I’ll try this out in the upcoming days.

The thing is, these were vrscenes that were created when I opened the thread, when I could import them without a problem, but those same files, cannot be imported now.

I sure hope this workaround will work.

Thank you again.
I’ll report on the outcome.

Yes, I can confirm that this tip works, just by using the “Subdivide Modifier”.

You just saved me a lot of time and nerves.
Thank’s a ton!

I tried the new Vray 5 update 1 By dragging and dropping a vrscene to rhino. I still get the same " failed to add proxy" @Peter.Chaushev issue is not fully resolved.

Now even the “Bounding box” walkaround is not working.
Nice keynote tho.

Hi @Peter.Chaushev

Can you please give us an update about this problem?

This is a major inconvenience and it’s interrupting our workflow.

Being able to transfer .vrscene files [and preview geometry!] is one of the most important reasons we have adapted VRay in our workflow.

I honestly wonder how this major version made it to release with a bug like this.


.vrscene import failure might be caused by a lot of things. Mostly unsupported scene objects - like Instancer for example, which does not translate directly into raw mesh, but there might be other issues

Currently we’re exploring an option to have a fallback to a box with default size if something goes wrong with reading the meshes. This way you will have some Rhino geometry to serve as a placeholder, no matter what happen during vrscene readout.

However it is quite hard for me to find a .vrscene that does not import. In fact apart from the presence of an instancer I can’t find another .vrscene that fails to import.

Could it be possible to share such file privately (no texture maps, just the .vrscene file), so we can explore the solution

Thank you

In the Next version I’ve never had any problems importing .vrscenes. Never.

After the jump to Rhino 7 and VRay 5, almost 60% of our asset library fails to load, so I don’t know what you mean when you say that - you cannot find any models that fail to load.

A bounding box won’t do. When we import highly detailed construction or mechanical building parts - we need a full preview of the geometry.
Also, when doing ArchViz we need to adjust the placement of the imported assets.

I understand that a lot of people that build assets are shitty modelers and don’t proof their modes for universal use, but you’ve had it nailed in the previous versions.

W.rar (12.8 MB)


every single one of those .vrscene files imports wihtout any trouble

The Rerna_Micro.rar file you shared in the first post also imports without a trouble

I don’t get it…
I’ve checked on few different systems and licenses.
Different people have recreated the problem.
@Peter.Chaushev confirmed that the previous .vrscene doesn’t import.

V-Ray Core Version: 5.00.50

V-Ray AppSDK Version: 2.91.00

This is a problem persisting for months, through few different versions of VRay and Rhino.

Here how it goes - when it doesn’t says that the scene “fails to load” it shows it as loaded, but it doesn’t show the .vrscene.


Wow wow wow. Scratch all that!

I’m so sorry!!! All this was our mistake.

The imported proxy models always go in the first layer - which was hidden.
While working someone turned it on and all of them showed.

My deepest apologies.
Deadline pressure.

Hm, they shall go in the active layer, aren’t they

Still a bug from my perspective

I’ve noticed that before, but apparently - today I’m quite off.

I agree that this is a bug.
The imported models always go to the first - [top-most] layer.

Again, my apologies for panicking.

Correction - Even when you create a new layer and place it first, the models still import to the previous layer which was hidden.
Recreated this in a new document. And the moment you first import a vrscene, it sets the first layer as default. Even when you create a new Import layer, it still remembers the first one.

PS. Here is one example vrscene, that fails to load.
PPS. Thankfully, Subdividing the core model still works.
kaput#2.rar (406.1 KB)

Note that the active layer isn’t necessarily the top-most layer. It is the one with the checkmark in the Current column.


That said, the active layer can’t be hidden.

Yes, of course.

The problem is - When you import a proxy scene, no matter what active layer you have currently, the import will be assigned in the first top-most layer [in your list] that’s listed at the moment when making your first import.
After, that layer is set as a default, and all imports will be assigned into that layer.