If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Exciting News: Chaos acquires EvolveLAB = AI-Powered Design.
To learn more, please visit this page!
New! You can now log in to the forums with your chaos.com account as well as your forum account.
Is there any serious technical reason for that? or this is just resource allocation issue?
If 3.0 version supported 2012 it is only fair that this support is continued until last VRay 3 service pack.
not cool in my opinion. this is leaving considerable number of people behind in the middle of VRay 3 life cycle.
I can imagine all 2012 users just switching from VRay. its simple math after comparing prices of new autodesk subscriptions with monthly rental of competing engine still supporting 2012.
Is there any serious technical reason for that? or this is just resource allocation issue?
If 3.0 version supported 2012 it is only fair that this support is continued until last VRay 3 service pack.
not cool in my opinion. this is leaving considerable number of people behind in the middle of VRay 3 life cycle.
I can imagine all 2012 users just switching from VRay. its simple math after comparing prices of new autodesk subscriptions with monthly rental of competing engine still supporting 2012.
i think it's a bit unreasonable to expect support for a product that is 6 years old.
As more and more people stop paying the ridiculous upgrade fees Autodesk demands, I think it will be increasingly appropriate to continue to support older versions. I know people that still use Max 2011 and 2012. I just can't imagine how many people will still be willing to upgrade after 2019 when their upgrade fees will be 40% higher than they are now (as per the email I received from Autodesk). It's an absurd price to ask for a product with such development pace and reliability. Just don't get me started on Max 2017, worst release in 7 years!
i think it's a bit unreasonable to expect support for a product that is 6 years old.
While true, I have to agree that with autodesk's shift to rental only, we're likely to see a lot of people keeping older copies of max, and the vray userbase may not be as large for current copies of max. We could potentially see a time where the majority on max users stay with say max 2018, even 6-10 years later. Worth watching at least.
Vray is the only thing that is even making me consider 2014. But in this situation there's nothing to gain with 2014 except vray 3.5 compatibility. I don't think I'd ever move past 2014 because of how AD butchered the layer manager. So far I haven't seen anything in max worth upgrading year after year.
Will see what can be done about it, but we can't support 3ds Max 2012 for much longer so you'll need to find alternatives sooner or later. The compiler that we use for 3ds Max 2012 is very old now and prevents us from using newer versions of libraries like Embree, OSL, OpenVDB etc. All of them are moving to C++11 for their newest versions and we will have to update them soon-ish. We *could* use a newer compiler even for 3ds Max 2012, but that would break plugins like ForestPro.
Comment