Morning all,
When I go to materials > add attribute > add displacement... it comes up with a box saying that this feature will be legacy shortly.
I created a model. One with the approach above another other by clicking a grouped object > Extensions > vray > vray objects > add displacement to object.
Both seemed to render exactly the same. The only difference I can see is that the first one has the displacement on the material, and the later having the geometry stored in the geometry section.
Should I simply do the later going forward?
When I go to the tutorial page about displacements, it doesn't mention about anything being made legacy, so I'm assuming the displacement function will stay (which is a key one as I understand) but it's more of an interface change!? e.g. where the displacement map is ordered?
I'm still figuring out some of these key features and simply want to know the best practice going forward, ensuring my future models can be accessed going forward? On that note, if this first method is being made legacy, will future versions be able to recognise the displacement?
Thanks
T
When I go to materials > add attribute > add displacement... it comes up with a box saying that this feature will be legacy shortly.
I created a model. One with the approach above another other by clicking a grouped object > Extensions > vray > vray objects > add displacement to object.
Both seemed to render exactly the same. The only difference I can see is that the first one has the displacement on the material, and the later having the geometry stored in the geometry section.
Should I simply do the later going forward?
When I go to the tutorial page about displacements, it doesn't mention about anything being made legacy, so I'm assuming the displacement function will stay (which is a key one as I understand) but it's more of an interface change!? e.g. where the displacement map is ordered?
I'm still figuring out some of these key features and simply want to know the best practice going forward, ensuring my future models can be accessed going forward? On that note, if this first method is being made legacy, will future versions be able to recognise the displacement?
Thanks
T
Comment