Yesterday, we updated to Vray 2.40.01 and we are experiencing some issues with proxys.
1) The forest pack pro trees in our scenes are scalled down, they look tiny now. We updated to Forest 4 Beta, so it might be that, a quick scale up and it’s fixed, not a big deal for the moment. But to let you know
2) The Vray Proxys if the scale is not set at 1, the proxys are rendering not at the right place, like if they have moved. And it’s proportional to the scale we put in, the more we go up, the more the proxy is moving.
The viewport is fine though, it’s only at rendertime, and that’s annoying. The only way to fix it in the mean time, is to put the scale back to 1 and scale physicly the proxy.
Another problem with proxies I found in 2.40.01 is that if the proxy is missing the .vrmesh extension the proxy fails to load, even if the path is correct. It use to work fine in previous versions without the extension.
Yeah, definitely, since this is how a few of them were accidentally named and I never noticed it until I upgraded. I didn’t notice they were missing the .vrmesh extension because I just kept merging them in from other scenes. I was on 2.2xxx before if that helps to explain it. Anyways, not a big deal really, I just browse for them in the asset manager, rename with the proper extension, and reselect.
I tried the nightly build because I saw that it was fixed in the logs but for some reason, the spawning wasn’t working through BB, so I reverted back to 2.40.01
I can´t prevent from venting a bit. Vlado, are you having laugh with that respond ?
There might be lots of people out there relying on that fix cause they have deadlines to attend to.
You announced the fix for Monday the 8th. Today is Wednesday and none is released. Now it´s gonna be next Monday.
When is it going to be precisely ? A nightly build doesn´t cut it. How many times should one invest valuable time for
updating the workstations or renderfarms ?
Next time you release something open wide I suggest you might be better off sending it to some pro company working on real big stuff. In that case this heavy bug could be seen instantly under stress testing. And if you did, it leaves the question in what terms the testing procedures need to be overseen.
I was simply saying that it would be easy to recognize the fixed build.
There might be lots of people out there relying on that fix cause they have deadlines to attend to. You announced the fix for Monday the 8th. Today is Wednesday and none is released. Now it´s gonna be next Monday. When is it going to be precisely?The build is being uploaded on the server as we speak. We worked as fast as it was physically possible to implement the fix.
Next time you release something open wide I suggest you might be better off sending it to some pro company working on real big stuff.We did that. The fact is that no-one reported this issue for months and months since the changes went it.
In that case this heavy bug could be seen instantly under stress testing.But it wasn’t even though the builds were used in production by customers. So what gives?
And if you did, it leaves the question in what terms the testing procedures need to be overseen.We did test this quite carefully. Unfortunately some things slip through.
As a word of advice, if you have little time to spend on updating farm/workstations, wait a little bit after a new version has been released. There are always some problems/issues that occur. With that said, V-Ray team is one of the best supporting teams out there and the feedback/solutions they provide are unsurpassed.
V-Ray is used on the biggest productions out there, by the biggest studios in the world. Please do more research before posting such comments as it is unnecessary, we as beta testers try our best to report/fix bugs and issues and a little respect for developers work would be greatly appreciated.