It’s probably the usual teething problems of having something new, but we are having quite a few headaches with file and display performance so far. I had hoped that as it was on SP3 (hot fix 1.1) it would be ‘ok’ by now.
One chap has some pretty major performance issues with his project so he is going back to 2016 for now. In Max2017, the scene (which - granted- is fairly heavy with Forest pro objects, trees, shrubs etc) barely loads. RPManager doesn’t seem to be functioning properly either.
The same scene loads flawlessly in Max 2016 without issue.
It is so difficult finding the right time to upgrade software. With many concurrent projects, there is never a perfect moment.
I fought with it since April, but now, after the service packs, I like it. I had the issue with Walls & Tiles, but once that was removed, the viewport issues were resolved. You don’t need Walls & Tiles in the scene, just installed, for it to seriously break something in MAX.
One of the worst releases.
I understand usual 3dsmax behaviour, but hey, when it crashes randomly on “cut”,“connect” or “weld” on usual polygonal modelling… I am sorry - i will pass it. Working on 2016 now, no problems at all for now. They don’t have money for good testers or something ?
That “cut” crash problem has been there for longer than I care to remember. I’ve made the switch about 6 months ago and all things considered, it’s not been more or less stable for me than 2016. And I’m certainly not one to usually defend AD but we cant expect beta testers to account for the shitload of scripts, plugins and external assets with all stack on top of it. But hey, 2018 is coming out in a couple of months from now…
I am working for 2 months already in 2016 - only single crash. 2017 crashed like 3 times a week. I don’t use “shitload” of scripts plugins and etc. But their job is to test BASIC stability. That’s exactly where autodesk completely sux. Not to mention A LOT of other issues.
Yeah 2018 incoming with … what ? New super stingray integration ? New background for viewport ?
They should take off 2-3 years to resolve shitload of problems, incorporate proper multithreading and other stuff which community has been begging for years now.
But hey, let’s just earn money.
Personally I’m just so tired of autodesk and 3dsmax’s endless bugs. I don’t understand how could they brake so much stuff from 2016 to 2017. Since i started learning Houdini it has been a relief (and a struggle at the same time), i can’t remember the last time it crashed, and most of the stuff just work, period. Can’t wait for Vray for Houdini, and their 16 release looks fenomenal.
Yep, same here. Constant bugs and broken/unfinished tools. I’m waiting to see what Blender 2.8 brings to the table. I heard it’s going to have a proper layering system with nesting capabilities which is a big thing for me. It could be the first time we move part of our work (at first the smaller scale jobs) off 3ds Max to another 3d app.
In my experience 3ds max 2017 is quite stable the only thing that drives me up the wall is that their new selection system doesn’t work sometimes. When I hover over adjacent edges I get the selection preview for loops or rings, but when I click to confirm nothing happens. So I have to deselect and reselect the edges and than maybe it works.
It used to be that, maya / max back in the day were released once every few years, but they were solid releases. You could use initial version without much issues.
Since autodesk acquired both of them, they suffer from the same problem. Initial release is not usable period. It becomes usable perhaps after 4-6 service packs, in itself this idea is ridicules. Why force the hasty release of the software? Is it to drive sales, perhaps. Let’s sell as much as we can, and deal with fixing stuff later. You sign a huge EULA where you wave them from any financial losses you incur due to instability of their software. This idea in itself is also ridicules. Its like buying a car without breaks, knowingly signing waver that if you crash, whoever sold it to you is not responsible for it (some one mentioned this already before).
However mentioning this, I also realize that back in the day maya cost $16000 , autodesk did bring the cost way down.
In production we’re currently using 2015 with Vray 3.4 but in my spare/down time I use 2017 and Vray 3.5. Viewport performance is a massive plus for me - With full car data sets (exterior and interior) in Max 2015 I get 5-30fps in the viewport whilst playing a 360 turntable. With 2017, I get smooth feedback and 90fps+ on the turn table. The layer manager is much improved - one guy recently had to ditch 2015 briefly because the layer manager is broken (and will never be fixed). I’ve not had any random crashes or bugs whilst using it. Although yesterday I’d imported some plant geometry from an Evermotion scene which would crash every time I tried to save the file. Wasn’t able to test 2015 as I was at home.
I find 2016 pretty okay. It really does annoy me (and I’ve said this before) that we users pay thousands of pounds/dollars on this product and still have such a hit and miss piece of software. It’s like they have totally different teams working on alternate releases of max. I remember 2009, 2012 and 2014 being good…the others iterations were not as reliable. You say that we get what we pay for but the user base since the initial releases has increased substantially. Autodesk are getting a lot of money from us but still not delivering a reliable product.
HI, I also have gtx 970 although i’m using 2014 version still, but I was thinking about upgrading to 2017, do You know if there is any solution to this problem ?
, autodesk did bring the cost way down.