Displacement broken edges

[stevesideas]

I'd be very inersted in the result. I am experiencing exactly the same issues.

[LudvikKoutny]

Hi,

any news on solving this problem? I need to displace some mountain slopes with cliff texture, and this issue is responsible for me failing to finish the project at the moment :/

[Morbid Angel]

is the mountain uvs made from separated shells? can you post part of this scene + displacement map here for investigation?

[Svetlozar Draganov]

We are working on this issue now but the test scene that we have here is way too simple and our developers doubt that the fix they are working might not be applicable in more complex geometries.
Would anyone of you is able to share a more production oriented scene which we can use in our tests? The scene with the tree from the fist page would be perfect.
More that one scene are also welcomed, the more we have the better.

Thank you very much in advance.

[LudvikKoutny]

We are working on this issue now but the test scene that we have here is way too simple and our developers doubt that the fix they are working might not be applicable in more complex geometries.
Would anyone of you is able to share a more production oriented scene which we can use in our tests? The scene with the tree from the fist page would be perfect.
More that one scene are also welcomed, the more we have the better.

Thank you very much in advance.

Hi, I am sending you the tree scene on the mail address in your signature. It should arrive in about 20 minutes from this post.

Thanks

[Svetlozar Draganov]

We got the files, that you very much for the sharing.
I'll update the thread when we have some progress.

[Jiri.Matys]

How is it going with this problem please?

[Jiri.Matys]

I just found out that when export 32bit image from ZB seams are always bad. But when I export only 16bit, seams are ok, weird.

[matanov]

There are some improvements in the beta for the broken edges issue ("keep continuity" = on). Have you tried it?

[stevesideas]

Is this improvement in the latest 3.4 version or only betas still?

[matanov]

It was in all Next betas and now in the official V-Ray Next. No plans for adding it in 3.x versions.

[anthonyh]

Sorry, is Vray 3 to be improved at all any more ? 3.6 is still full of issues for us and while I understand all the new tech won`t make it in, bug fixes for this would be appreciated. If Vray 3 is no longer supported then we may be stuck on 3.4, too many issues with 3.6. GPU rendering just makes us spend money on new hardware. Looking at Corona`s new features being able to render Vray materials/scenes now, it seems like Corona could be the best upgrade option if no more development is coming ?
Also is it still possible to get the latest Vray 3 Nightly as it would be good to have the latest stable at least for the forseeable future. ?
thanks
anthonyh

[matanov]

I think 4 years of new features and bug fixing for V-Ray 3 is close to enough for now. We are trying to not leave a version with issues that could block someone's workflow so please list those issues.

For access to 3.x stable nightlies, you can a drop a line to support@chaosgroup.com

[anthonyh]

Hi,
thanks for responding. Please note I really didn`t mean to imply any salt here.
I`ve already sent a request to support (I realised after the fact).
What might be good is to release a `final` Vray 3 version instead of the current 3.6 for download, call it 3.7 ! Easy.
- (seperated for potential salt ! caution advised)
Having said that for a list of my issues please see the forums, after all we`re in a thread where you state 3 posts above that no fix is forthcoming for Vray 3 on this issue. Other issues I have is with Adaptive Sampling having too many situations where it has to be turned off due to render errors, like low quality reflections of IES lights, The inability to work with clamping/sub pixel. The first release with Adaptive didn`t automatically turn sub/clamp off so I assume that it was always intended to work until you found out it was incompatible and auto-off added. The shadow edge bump mapping problem(there`s a big thread on that one). I`m sure there`s a bunch more but this is already starting to seem like an attack, which it really isn`t.
We never used nightlies in a production situation, only full releases so forgive me if any of these or others were fixed.
-
One further thing was, I was asking because up until now I thought Vray 3 might still have been developed further as I believe I read that in another post from someone in support. If that is no longer the case an announcement would be appreciated. Do I remember you guys doing the same for Vray 2 at the end of its life, a cumulative version release ?
cheers
anthonyh