I am very sad to hear about the Baltimore office. As a V-Ray for Rhino user since it was beta, a member of the team that helped create V-Ray for Matrix and a person that worked very closely with the Baltimore team almost daily, I hope the next generation of leadership on this product will be as passionate about it as they were.
That said, I also agree with the posts made by others. There are several changes that have made daily usage almost unusable and v2 is the much preferred version at this point even with the new features that are working.
Some items that I would like to add to the list of problems are..
Locking the exposure so that it doesn't change with the viewport dimensions or camera length. (this is crippling me the most currently, if its hiding in the UI i can't easily find it).
Per object map evn / reflect / refract overrides will often have different exposure levels than objects without overrides, especially when utilizing a light dome.
Bring back subdivision level settings for glossiness in the UI.
Those items would be greatly appreciated if they returned and or worked again.
That said, I also agree with the posts made by others. There are several changes that have made daily usage almost unusable and v2 is the much preferred version at this point even with the new features that are working.
Some items that I would like to add to the list of problems are..
Locking the exposure so that it doesn't change with the viewport dimensions or camera length. (this is crippling me the most currently, if its hiding in the UI i can't easily find it).
Per object map evn / reflect / refract overrides will often have different exposure levels than objects without overrides, especially when utilizing a light dome.
Bring back subdivision level settings for glossiness in the UI.
Those items would be greatly appreciated if they returned and or worked again.
Comment