There are bigger Problems than this fx stuff.
Yes, it should have a fx sim solution out of the box but:
Fx sim tools are difficult to setup and you need a really strong Computer to get it done in time.
As allways, sims tent to do what they whant and its allways a long rocky road to success.
This is why there are Specialized Artist which do that stuff 90% of there time.
Don't think you'll get a one-klick solution which is computing in some minutes, that is not Possible.
Its more like a secound rendering process without beeing able to see just frame xxxx without simulating the frames before.
Also i think that all users who really need this fx stuff, had allready buyed a Pugin to do that.
They put jears in it to get a feeling for it and they'll continue using there Pugin even if max includes its own one.
For me it would be way more important to finaly get the big Features which are not or (just "sort of") avalible as Plugin:
Viewport Tear off!!!!!!!!!!111
Note based wire parameter Editor
Skin Sliding and Muscle jiggling
Ihno Oetjen
Senior 3D Artist
Whishlist:
Calculator for all Parameter inputs.
Random seed for adv. Wood.
Curvature map node.
and again implement Vray making a deal with Chaos.
Hopfully this never happens. Every time AD bought something, it goes EOL very soon.
Exept a view (much to less) bug fixes nothing happens.
The full modifier list sometimes feels like an graveyard.
Nealy every of the old features you pointed out to be replaced, ones was an exiting and good plugin AD bought...
Hair, Cloth, Biped, Cat and countless other corpses are rotting in max's guts.
They are not native, ther code isen't from AD and it seems that AD's Developers can't continue developing it.
Maby because they can't handle the 3th Party code. Maby they're just to view to keep all those features up to date while making new ones.
Maby the problem is that they forced ther selfs to make a new version with new features for us ungrateful users every jear.
Don't let this happen to Vray!
Chaos is a incadible good Plugin forge. They should continue to do what they want.
I don't want AD to have a finger in that pie.
The Features AD writes are working mutch better than the Features they bought.
I want them to make there own muscle, rigging and hair system's.
Ihno Oetjen
Senior 3D Artist
Whishlist:
Calculator for all Parameter inputs.
Random seed for adv. Wood.
Curvature map node.
Even at the risk of sounding combative and harsh...I'd like to say that if any of you that come to these forums griping every so often care as much as you say you do, you'd sign up to be a Beta tester (if you haven't already).
That's the one way to get your voice heard, see the future of the software, and test it before it comes out. Put that discontent and disappointment in the past to good use, in a constructive way.
These yearly gripe fests about "still no news" don't help anyone, because you should know by now that no, in fact, there "still" is no news - nothing is made public until right around or exactly at release. We're still a little over two months away from the usual April release. Like it or not, this will never change so long as Autodesk is a publicly-traded company.
While there were disappointments and real head-scratchers in the early 2010's, this new development team hasn't given us a single reason to not be optimistic about the future of this prodcut. 2015 was lackluster, but didn't they take over mid-cycle (I forget)? 2016 was much improved and the team delivered a nice product. I have high hopes for 2017 and forward...and you should, too!
@mhaZe23 wrote:
just read about the bug in this thread and it´s gonna be clear Max has become too instable because of patchbuying tons of features:
Bought 3rd party tools is certainly NOT the reason for the groups bug in SP2, and it certainly was not the reason for the Nitrous memory leak in SP1. Quite the contrary: those are typical bugs that may happen just because they touched core parts of Max. In those two cases it certainly and definitely was QA dropping the ball: Such things never should slip through final testing...
And don't hang such layoffs onto dev teams - ever . Those are the people who got no warning and are hit by it in their personal lifes. If you want to rant, rant against people who are really responsible for this style of running a business .
Just so that new testers are aware, they are to be BETA testers. Not product managers. Not setting the direction of the product for the next decade. Not throwing on the breaks because they want/can't stand something. If you have an idea, great; if you can spell it out clearly, even better; just don't expect it to added to the release you are testing. I've seen quite a few people sign up only to be disappointed they "aren't being listened to" because their expectations were different than the role.
@Anonymous wrote:
I blame the do team and team leads because they continually insist that Max IS getting attention and NOT just archviz...as soon as they agree that they are being told to focus on arch viz I will accept that.
But then make THAT the response to the #1 voted feature...officially announce that you don't care what users vote, Max is archviz and isn't getting fluids.
They insist because it's a wrong assumption on your side. And a fantasized, magical fluid solution will not happen. Are you actually aware how limited Bifrost in Maya is right now? If you seriously have a need for fluid simulation so badly now, go for a 3rd party solution.
It's plain ignorant to shut the eyes on the good things which happened since the Max 2014 release.
Even more so since Eddie took over and brought the team up to speed...
Are you aware in how many areas Max has to be improved to provide a stable platform for the future?
Eg.: Do you think they should ignore High DPI monitor support ( which will be a HUGE undertaking in Max , by the way ) ? Or the internal performance bottlenecks (which piece by piece get attention as one can simply verify by comparing performance from release to release). Max core code is a 20 yr. old monster, ( i bet big parts are even older and coming from 3D Studio DOS ). It's impressive that it still keeps up with todays demands...
BTW:
What version are you working with, somehow i have the impression that you are one of the persons who sticked with Max2012 or 2013, because they were so disappointed by the lackluster features (and viewport performance) of those releases.
