Main problem is that Chaos doesnt tell any news about this problem for a year. Even dont reply to this thread. 
But they bought Corona so I think it will bring something great to VRay too. Like solving this problem.
Corona has better bump and normal mapping so maybe Vray could learn this. I love Vray and dont wanna migrate.
I started similar topic some time ago and got answer. I’m also looking forward to Chaos Group for solving this issue.
You got answer about something else, not this bug.
I hope that Chaos Group will face this and will try to solve it and inform us.
Still no reply fom anyone from Chaos?
maybe its worth trying with vray NEXT beta and posting there to get enought attention?
its definitelly vey dissappointing to see thos is not important issue to solve.
one cant even say Chaos has different approach to computing this…its clearly a bug and its being left aside for way too long.
why is this relevant user feedback/request (you name it) being so overlooked please?
Can we please get some info whether this is going to be fixed in NEXT?
Thanks!
Curious as well. This is a major annoyance with V-Ray.
I`m picturing chaosgroup employees hurriedly walking by while whistling.
Funny picture in my mind. In all honesty though I don’t think they’re ignoring it right now, that wouldn’t be their style. They would just announce something like “Sorry this will be a feature and USP of VRay forevah!1” instead of ignoring it :P. JK - let’s hope this gets fixed soon.
There are things more important than new features.
Fixing something like this should be among priorities for something that wants to call itself NEXT. You can flame me for saying this, but i think i have a right to be upset when this is being overlooked. Moreover when it has been promised a long time ago in this forum for a major release. And speaking of major release, there are not so many new features packed in NEXT beta at this point for CPU anyway. Look at the Corona 2.0 list 
I am sure GPU users must be overly happy with the upcoming release, but the CPU version, forgive me, reminds me of a car facelift…i dont get the hype around it.
I will have to buy it anyway to keep up with the rest, but since for me its five licences and 10 nodes, i would appreciate if i was buying something that sorts out more of the current problems.
That’s true. I think Chaosgroup has managed a way better balance than many other big software companies in this regard though.
I also have to say that I am very dissapointed with the Chaosgroup support feedback. I have two open issues, where no one from Chaos staff even replied in the threads. For one of the issue I got a reply via eMail that was just plain nonsense…
You know, I feel Chaosgroups support has gotten a lot worse in the last 6 months.
Sad but true.
Hello guys,
Please accept our apologies for not replying this thread for a very long time. This is not our style as probably most of you know but since we don’t have a system that monitors forum threads it’s possible to miss a thread like this one. If that happens I would like to ask everybody to give us a call or to drop us a line at support@chaosgroup.com - filling the thread with negative comments is not very inspiring for us and we will greatly appreciate if you find a better way to let us know that we are not giving enough attention to the thread.
Chaos Group main mission/goal is to listen the customer/user - we really put a lot of efforts to communicate and listen our customers on all possible communication channels, look for example the forums - there are posts from support, qa, developers and other Chaos Group employees in almost every thread. Doesn’t this speak how important is customer opinion for us? Can you point us a company in the industry with better customers engagement? Maybe there are things we could learn from them.
Some of you mentioned that you are disappointed with the support - may I ask some examples or where we haven’t done our job well? We all give our best to help everybody, if there are cases where we failed to do that we would like to know which are those cases in order to learn from them and improve ourselves. I admit that something we may delay a reply cause overloading, I could guarantee that we never miss an email or a phone call (if it’s in our working hours). And regarding the quality of our replies, they are never plain and nonsense, we invest a lot of efforts in each reply especially if it’s about a bug - we always try to find a workaround and propose a temporary solution until the bug fix comes out.
This is what we always do. Of course there are always exceptions, we realize that sometimes we fail to do our job in the best possible way, but we are always open to listen and to apply the necessary changes in order to not disappoint the customer. And yes we expect from you guys to give us that feedback, and please don’t judge us if we miss a forum thread - just pick up the phone or drop us a line to bring this thread to our attention.
Regarding the bug, I’m sure that all of you know that it’s not fixed yet. Yes it’s been long time since the initial report, yes it’s promised that it will be looked more carefully for 3.6 release, yes it’s only V-Ray issue and all other render engines are better in this regard but no it’s not fixed. What I can do is to discuss this matter with Vlado on the next meeting and to inform him that from customers perspective this bug is overlooked and critical. Since the development priorities are something extremely complex I cannot promise that we’ll be able to handle that immediately, but at least will prioritise it higher in the list of things we have to do asap.
Best Regards,
Svetlozar
Hey guys,
Just to let you know that the bump should be a lot better in the coming Update 2.
WOOOOOOOOOOOOOHOOOOOOOOOOOOOOOOO
thank you
Since this thread was originally made for Vray 3.5, any chance this improvement will find it`s way into a Vray 3.7 build at some point ? Be much appreciated.
thanks
anthonyh
It’s not very likely unfortunately; this was not a trivial change - I had to modify code in a number of places and the code has already drifted apart between the two versions.
Best regards,
Vlado
Could you please elaborate on the changes and why bump should now be better?
Omg thank you!!!