Mine just feezes for the simple fact of having it installed (even in 2D only files ).
The only effective workarround for me is to disable the plugin and load it only for renders. I have to cross my fingers and disable it again as soon as the render ends.
same problem here in Copenhagen. installed vray 3.0 on 80 machines. cant use it, because it crashes all the time. using vray 2.0âŚthatâs not an update.
For me it also fails even if 2D geometry doesnât go with material by layer and I make sure there is not any non Vray 3 unpurge materials in the file.
Maybe that works for you too? Is not a good solution and Chaos group should fix this but seems to work for us at the moment.
Vray 3.6 for Rhino 5 SR 14 issues again.
Impossible to open/load/read âMaster Fileâ with external block links connected.
Rhino Crash all time.
We found this is because one of the 2 possibilities.
a) Materials overrides causing crash right after open Master File.
b) Every file which have to many block, when opening block manager Rhino crash again.
orâŚ
z) Vray 3.6 change its algorithm from Texture Placement. Now we have to enable Mirror U/V parameters for small textures take place properly all over objects.
I have report this situation to Chaos Group, but as always they take some time to answer.
I am still waiting for their help help.
What??
the linked block is gone? So what we gone about all our architecture project files that have linked external references. I mean every all our files here at office are linked.
Do we have to stay/downgrade in Vray 3.4?
There is a solution?
For now its impossible to access our Master files.
YES⌠The crashing problem is when i insert a block as external linked ref file. Rhino crash right after thatâŚ
We are at process of re-download and re-install it. Although the re-instalation it is with the same V-Ray 3.6.1 version as before when we found this issue.
I hope it solves this. Other wise we need to downgrade to Vray 3.4 and keep it for ever
os build: 16299.19
version: 1709
win 10
intel ÂŽ xeon ÂŽ cpu e5-2260 v4 @ 2ghz
2.00 ghz (2 processors with 18 cores each)
ram 64
nvidia geforce, gtx 1080 ti
everytime someone in our office (100 people) uses vray 3.6 with rhino the computer freezes upto 4-5 times a day.
people now deinstall vray 3 and install vray 2 again, because itâs impossible to work like that.
we tried nearely everything, listed here and aswell downgrading windows etc.
nothing helpsâŚ
if you have been working in Vray 3 and tweak your textures and so, went back to Vray 2 will cause your more troubles then your think.
All textures will be missed and uncalibrated. Your office will need to spend much time tuning all your scenes again. Don´t do that.
First I think you should report ChaosGroup via support method.
Here at my office we have:
Windows 10 Pro version 1709, build 16299.192
Intel i7 6850K CPU
64 Gb Ram
Gigabyte GTX 1080
In the past we have issues in Vray 3.0. We report to Chaos to. And they help us⌠I will tell you what they tell to us. Perhaps you could fix it for your self. Please try this steps.
Reinstall Lastest Nvidia Geforce Drivers with Geforce Experience (check fresh install under menu)
Download Lastest Vray 3.60.01 from ChaosGroup. Install it.
Reboot your pc so your Windows system can reorganize latest DLL files.
PS: when you get back to work, in Vray 3.6 for Rhino you will notice bad mapping textures. But don worry. It is a bug that ChaosGroup are working on. You can turn that around. Check this post, but you need to be login: (if for some reason you cant login i post what is inside there)
this is textures mapping issue.
Read this to correct this bug.
" Hi guys,
Unfortunately there is a problem with view-port texture representation in V-Ray 3.6 that weâve missed.
It was caused by our attempt to support V-Ray U/V tiling in the Rhino viewport.
It will not affect rendering in any way so itâs still safe to setup, render and save your scenes.
In case you want to manipulate a map and see it in the view-port with 3.6 you can do the following as a workaround:
> Disable the âplug-inâ checkbox for the material of interest
> Change a random property of the rhino material parameters (it doesnât have to affect the shader). This is done to make Rhino refresh the view-port map
> The texture should go back to normal at that point
Thank you all for pointing this out and excuse us for the inconvenience.
Weâll do our best to fix it as soon as possible.