Vray 51001 doesn't work with my model anymore !?!?!?!?!?

[jason_cafferty]

Seriously there are some big stability issues with this new release that is really stressing me out as its going to damage our reputation and earnings at this rate.
We have a model that is 95% complete and now Vray just won't render it at all. I am using an RTX3090 with the latest driver. It was working fine yesterday, now nothing. You hit the render button in the Frame Buffer and the Teapot never gets a stop button. The system fans spin up for a couple of seconds and the progress window is blank with a 0% progress bar.
Our switch to Vray started so well with both the initial version of 5 working so well, now this new one is utter garbage that has introduced a lot of cool features and a ton of problems. I've a project worth a few grand needed by next Friday and right now Vray refuses to render it.

I restarted the system and made a new SU file with just a cube in it and it works fine so why has this mode l stopped working?

[nikoleta.garkova]

Hi jason_cafferty

Sorry to hear you are having such issues. Allow me to assist you to the best of our abilities so we can resolve this as soon as possible.

You've mentioned that

I restarted the system and made a new SU file with just a cube in it and it works fine

so this might mean that it is something project-specific.

• Have you tried copy-pasting the entire model into a freshly opened SketchUp file?
• Are you rendering with CPU or GPU - is it working as expected if you switch from one engine to the other?
• Would it be possible to forward us the project in question so we can have a look and troubleshoot. You can get in touch with us via our contact form - make sure to use the Pack Project tool from Extensions > V-Ray > Pack Project and please mention this thread in the email.
• Additionally, please provide details regarding your OS, CPU/GPU/GPU driver version.

[konstantin_chaos]

Hi jason_cafferty,

As you are in a hurry, I'd recommend that you share the project with us.
This will let us very quickly find the root cause for the issue and give you a workaround.
Providing you with a custom build including a fix is also an option.

Naturally, answering Nikoleta's questions might also help us determine the cause but sharing the project file will be faster.
You can use a file-sharing platform of your choice and send the link as a personal message to me or Nikoleta.

And I also want to say I'm very sorry for your inconvenience!
You are correct by pointing out that the strive for adding features sometimes hurts the software stability.
We will focus on stability and reliability in the following months so please don't hesitate to share any other issues that you find.

Konstantin

[jason_cafferty]

I believe I have tracked down the issue. Before I get on to that, my system spec is as follows:

X570
3950x
64gb 3200 Ram
RTX 3090 FE
All drives are Nvme or SSD
Windows 10 Pro - up to date.
SU Pro 2020

So my model has real geometry products on the shelves so is pretty heavy but nowhere near as big as other layouts I have done. Where possible, I make all the assets myself however the odd one from somewhere else sneaks in as the client tends to do a rough prelim plan in SU.
I noted the materials that the Asset editor was having issues with (my other post with the exclamation mark) and decided to purge them out of the model. I then purged the model and rebooted. This model then proceeded to render so I can only assume that these models and or their textures were to blame and I would be happy to send you a small SU file with them in it to see if you can work out what the issue with them may be?

I will say though that the material part of the asset editor is defiantly more tetchy than is was in the first 2 releases of version 5. It has a habit to stop working requiring SU to be closed and restarted with pretty much never happened in the prior 2 releases.

[konstantin_chaos]

would be happy to send you a small SU file with them in it to see if you can work out what the issue with them may be?

That would be awesome.
Anything that causes issues in the Asset Editor or during rendering is a bug and should be investigated.

I will say though that the material part of the asset editor is defiantly more tetchy than is was in the first 2 releases of version 5. It has a habit to stop working requiring SU to be closed and restarted with pretty much never happened in the prior 2 releases.

Again, this might be caused by specific shaders.
Having the project to experiment with here will help.

[jason_cafferty]

I'll sort that out then later this week when I get a moment. Regarding the actual project file, that would have to be sent to you rather than posted on here as it's a clients project so sensitive info etc.