Vray and the constant issues and bugs

[jeremy_levitt]

Is it just me or are other people having constant issues with Vray lately?

It seems like every week there is a new problem that comes up, leading me back to this forum to troubleshoot or contacting support for help, which takes at least a couple days with the time zone difference to get some solutions going.

And then when I think I have everything working and going smoothly, I wake up one morning and some gremlin has decided to break things. Some days I spend more time trying to fix Vray than actually doing any work.

Overall, I'm finding Vray very unreliable, very unstable, and, to be honest, I think I'm going to start looking at alternatives. For the cost of this software, it isn't worth the headache. I've spent years learning how to make Vray work for me, but if these issues keep appearing, I'm willing to spend time learning a new render. I hear Enscape is good.

[Micha]

I use V-Ray for Rhino daily since years and I'm quite happy. OK, often I still use VfR4, since I feel more comfortable with the old frame buffer. But never I wouldn't jump from V-Ray to Enscape. I used Enscape in the past for some "low-budget + tight deadline + animation" projects because the quick output and large asset library (before Cosmos was available) and I was very frustrated about the tight limits everywhere. Enscape allow to create very nice looking renderings, but only within the tight limits. If you need a little more than you are flat on one's back. My clients needs realistic looking materials and only VfR give me the freedome to mix surface effects. For example I was not able to create simple milk glass. Or the horrible quality of mirrors at scenes.
From time to time I look at the Enscape side and I miss a development of basic render features. It looks only asset and UI features are added. Maybe the technology is on the limit. Be careful. If you render architecture stuff with limited materials only than Enscape is ok.

For VfR I wished more frequently updates.

[Peter.Chaushev]

Hello, Jeremy,

I аm sorry to hear you have encountered so many issues with V-Ray!
The limitation you encountered with V-Ray Swarm (CPU not usable as CUDA device if no other valid CUDA devises are available) is already logged and will be fixed in a future update.
Another issue related to VFB window parenting is currently being investigated by our dev team.

You also shared with us concerning observations of V-Ray for Rhino on Win11. We, however, were not able to validate them so far.
Coupled with your report on missing materials, I would like to ensure you we are dedicated to resolve both issues as soon as possible.
Your cooperation on this would be tremendously appreciated! Both I as well as our support and dev teams are on standby to get involved as soon as we have sufficient info to work with.

Kind regards,
Peter

[Peter.Chaushev]

For VfR I wished more frequently updates.

Our teams are currently working hard to deliver a rather large update (v5.2) soon. Sincerely hope you'll find its new additions useful!

So far six V-Ray for Rhino updates were released this year (one each month with a delay since August to allow us to focus on 5.2).
Beside the major 5.1 update bringing Chaos Cosmos, VFB and Vision improvements the rest were mostly stability updates with a feature or two each.

Would appreciate your feedback on this schedule and what you would like to see changed!
If any new feature requests have come to your mind recently, please let me know!

Kind regards,
Peter

[Micha]

Good news.

It would be great if the subselection (poysurface) materials could be fixed again, It was very useful.

[nikolay.bakalov]

They are fixed. More precisely redeveloped. Simply not released yet

[Micha]

Great! Thank you very much!

[jeremy_levitt]

Our teams are currently working hard to deliver a rather large update (v5.2) soon. Sincerely hope you'll find its new additions useful!

Would appreciate your feedback on this schedule and what you would like to see changed!
If any new feature requests have come to your mind recently, please let me know!

Is there an update on 5.2? The several issues I have identified and troubleshooted with you (for free, mind you - you charge us a premium for this product but you get free issues testing) are still causing us great headaches. I can't speak for others, but right now I need more stability and less bells & whistles.

[Peter.Chaushev]

Hello, Jeremy,
You can find improvements based on your feedback in the v5.2 update of V-Ray for Rhino we just released!
It is available for download at https://download.chaosgroup.com/down...and7-52001-adv
You can read more about the highlights of this update, including its stability fixes, at https://forums.chaos.com/forum/v-ray...-now-available

This update does not include a new V-Ray Swarm build though, meaning one of the issues you reported is yet to be resolved.

Kind regards,
Peter

[jeremy_levitt]

Yet there are more bugs. Incredibly frustrating.

File path editor loads for several minutes then crashes.
Swarn Network discovery doesn't work. I have to turn OFF the Network discovery setting and then surprisingly, it discovers the tags.

[jeremy_levitt]

Asset editor all of a sudden loads up blank. Have to restart Rhino. The quality of this software is beyond belief.

[Peter.Chaushev]

Hello, Jeremy,
The vray-neui log files located in %APPDATA%\Chaos Group\V-Ray for Rhinoceros\vrayneui can help us determine what went wrong with the Asset Editor.
We can also offer you live assistance via TeamViewer at a time convenient to you between GMT 08:00-15:00, Mon-Fri. Please let me know if you feel comfortable with receiving direct help from our Support and Dev team.

Kind regards,
Peter

[jeremy_levitt]

This issue is still unresolved - patch rendering selects a different part of the image to render. Stopping & restarting fixes it, but it's annoying

[Peter.Chaushev]

This issue is still unresolved - patch rendering selects a different part of the image to render. Stopping & restarting fixes it, but it's annoying

A fix for this problem is available in the following stable build: https://nightlies.chaosgroup.com/#/v...table/20211112
It will also be included in the upcoming v5.20.02 hotfix planned for release soon.

Kind regards,
Peter