First couple of Issues with Vray5

[Doger]

For the 4th question there is no need to save the proxy in a C4D file. You can drag and drop the "vrmesh" file directly in to the scene, and it will be opened/imported. So if you drag and drop the file it will open the proxy on a new scene, but if you hold Shift and Drag and Drop it in to Cinema 4D then the proxy will be merged in to the current scene.

But the textures will be missing then, right?

[forumer101]

This version 5 is still a work in progress. So many bugs .
Other than financial reasons, why did Chaos release it as an official one?

[MichaelLammens]

This version 5 is still a work in progress. So many bugs .
Other than financial reasons, why did Chaos release it as an official one?

I disagree. Works better than ever on my end.

[index]

I disagree. Works better than ever on my end.

you probably never tried to convert a vrayforc4d 3.7 file.

[MichaelLammens]

you probably never tried to convert a vrayforc4d 3.7 file.

I have & you are right. Doesn't work, goes super slow. If you copy the geometry in a new scene with new vray5 materials it works great.

[forumer101]

you probably never tried to convert a vrayforc4d 3.7 file.

Absolutely. Vray is telling us to start from scratch and forget all of our existing libraries and projects.

[forumer101]

HEy MichaelLammens ,
Thank you for the feedback it's much appreciated.


Currently, we don't have one. It was already requested a few times, so I'll add your request as well. Currently, we're researching for a better way of doing the whole conversion so it might take some time.


This might vary based on the scene unfortunately. The material previews are native this time and not like in 3.7 a separate file so a doubt that this is the problem. Keep in mind that old scenes sometimes do have some leftovers (even hidden ones) that might slow down the rendering. It will be best if I can investigate the scene to tell you what might be wrong. You can try Merging the scene instead of Opening and converting it and apply a "Global material override" to see if it is still slow. This will tell if the materials are a problem or not. During the conversion we're removing anything that is unsupported. You can find out more about the scene conversion in this topic


I'll record a quick video for you about this.


Yes they are supported in the official version. I'll use one scanned material on the video that I'll record about the White balance and Auto exposure.


V-Ray 5 for Cinema 4D is rewritten from the ground up and is very different from V-Ray 3.7 under the hood as a code base and workflow as well. Unfortunately this is why won't find any, or at least not "fully compatible" with V-Ray 5 materials or assets. We will be working hard on interoperability between the other V-Ray integrations and once we do any kind of material importer you should be able to use existing material libraries made with other V-Ray integrations (like Max or Maya) and import them in Cinema 4D.

I wouldn't recommend starting with V-Ray 3.7 because it is a very old version and many workflows (and even tutorials) there won't be applicable with V-Ray 5 since as I mentioned above V-Ray 5 is a full rewrite.


We're planning on doing tutorials for the most used workflows and basic usage of some essential features. Here in this Topic I'm showing how you can use the Cinema 4D help function to reach our Documentation page where you can find help for most of V-Rays parameters.
In the future the Documentation page will also be filled with various tutorials with different topics. I'll be happy if you share what tutorials would you like to see first.
[/QUOTE]

You should not have release it as final version if it is not ready yet. It is disservice to your existing customers. Where are the promised material library?

[MichaelLammens]

The V-Ray Proxy object is new and with a new workflow but the vrmesh file format itself isn't changed, so you shouldn't be having issues with your libraries. It depends however on how the library is build and how do you handle the materials for the proxies. Let me know how it goes when you have a chance to test them. I would still recommend to rebuild your library anywas.

It is Ok with the steps you've decided to go with. However, I would suggest to wait with the reexporting of the proxies if possible since we're going to be adding some improvements in that regard with our next hotfix.

For the 4th question there is no need to save the proxy in a C4D file. You can drag and drop the "vrmesh" file directly in to the scene, and it will be opened/imported. So if you drag and drop the file it will open the proxy on a new scene, but if you hold Shift and Drag and Drop it in to Cinema 4D then the proxy will be merged in to the current scene.

Dear Shaio,

Any idea on when the hotfix would be around? I am really struggling without any libraries a the moment. We do arch viz, so trees, people, cars, etc are crucial.

[sirio76]

As far as I know there's a new build available right now, I'm not sure if it solves your specific issue though..

[MichaelLammens]

you sure? Latest release is 10 december? Am i missing something?

[sirio76]

There's one just released: https://nightlies.chaosgroup.com/main#/vray5c4d/stable

[MichaelLammens]

The V-Ray Proxy object is new and with a new workflow but the vrmesh file format itself isn't changed, so you shouldn't be having issues with your libraries. It depends however on how the library is build and how do you handle the materials for the proxies. Let me know how it goes when you have a chance to test them. I would still recommend to rebuild your library anywas.

It is Ok with the steps you've decided to go with. However, I would suggest to wait with the reexporting of the proxies if possible since we're going to be adding some improvements in that regard with our next hotfix.

For the 4th question there is no need to save the proxy in a C4D file. You can drag and drop the "vrmesh" file directly in to the scene, and it will be opened/imported. So if you drag and drop the file it will open the proxy on a new scene, but if you hold Shift and Drag and Drop it in to Cinema 4D then the proxy will be merged in to the current scene.

Hi Shaio,

Any news on this issue? Has this been fixed yet?

[shaio]

Hi Shaio,

Any news on this issue? Has this been fixed yet?

Hi MichaelLammens ,
By saying that there will be improvements in the "next hotfix" it doesn't mean that it will be fixed in the next version released in the "stable" folder in our nightly builds server. When I said "next hotfix" I was referring to the next official release of V-Ray for Cinema 4D. I'm sorry if I mislead you in any way since the versioning of V-Ray for Cinema 4D isn't really explained anywhere yet. I'll make sure to update the post as soon as we add the improvements and fixes in the "stable" builds, so you can check them out.

Thank you!

[forumer101]

Absolutely. Vray is telling us to start from scratch and forget all of our existing libraries and projects.

Underwhelming release.

[MichaelLammens]

The V-Ray Proxy object is new and with a new workflow but the vrmesh file format itself isn't changed, so you shouldn't be having issues with your libraries. It depends however on how the library is build and how do you handle the materials for the proxies. Let me know how it goes when you have a chance to test them. I would still recommend to rebuild your library anywas.

It is Ok with the steps you've decided to go with. However, I would suggest to wait with the reexporting of the proxies if possible since we're going to be adding some improvements in that regard with our next hotfix.

For the 4th question there is no need to save the proxy in a C4D file. You can drag and drop the "vrmesh" file directly in to the scene, and it will be opened/imported. So if you drag and drop the file it will open the proxy on a new scene, but if you hold Shift and Drag and Drop it in to Cinema 4D then the proxy will be merged in to the current scene.

Dear Ivan,

Has the current hotfix the improvements you mentioned earlier? If so, what changed?