Particle Flow Improvement "Multi-Threading" & more

[wal3dz]

Particle Flow improvement Requests

- improved Particle Flow UI, specially "box#3"

- Recompile PFlow from 32bit to 64bit "Multi-threading".

- Including Advanced Particles Mesher.

- Including Advanced Particle splines tracer, splines and Polygons connector like Atom & plexus plugins.

- integrate Particle Flow and Bullet FX to simulate multi-physics.

- Including mParticles physics presets.

- Other engine than Physx, like Bullet Physics, FEM and Sand solver

- More accurate and precise Collision of Mp/physx Shape on Box#2.

- More data operators, like noise and turbulence

- Better caching system.

- Dynamic fragmentation.

- Integrated 3d Fractal system like mandelbulb 3d

- Reaction diffusion system with presets

- Vertex color support In Viewport.

Maybe its too much, But this is my wish list
Thanks

[timC93P4]

I really believe in this idea! Pflow makeover would be amazing. tyFlow looks amazing

[Anonymous]

This is very expensive and kinda stupid, and they are not ever gonna do that and thats for the best, instead of rewriting PF from ground up they can buy TP and implement it in Max and just leave PF as it as or just remove it from the app along with a whole lot of other useless old crappy stuff for **** sake.

[JohnnyRandom]

@Anonymous 

Expensive, maybe. IMO no more expensive than any other major initiative, regardless of what you believe it is a major part of max, just like the matEdit, UVWunwrap, modeling tools, rendering, et al. Stupid no. Even in its antiquated state, PFlow is still a solid tool. It has deep integration into many other tools/plugins that make up for some of its shortfalls AND it has a much easier learning curve compared to Thinking Particles.

Besides, what even gives you the notion that Cebas would even consider selling, their cash cow, TP? Even if they did, how long have you been around? We have seen what has happened for two decades, time after time, with acquisition and integration. It is not a great track record. Tools get bought, stuffed in and put on life support and occasionally see some feature dev time. Although, it has gotten much much better in recent years, and it looks like they are trying to turn the reputation around. FYI Naiad was purchased seven years ago, that is a long time in "career" years; it does have very active dev; we are just seeing it integrate into Max.

Removing Pflow isn't an option, replacing it is. For max to be a swiss army knife that it is, it needs a capable particle system. It makes the most sense to work,  rework, or rewrite based on the current architecture (ie similar to the approach TyFlow has taken) to keep usability and two decades worth of plugins/tools more easily compatible.

[alitanucer]

@JohnnyRandom 

I couldn't agree with you more. As you said it, TyFlow exactly is doing what you described as a solution. It will be really interesting to see Autodesk's take on this. I know many times that they adopt an idea or even acquire a tool, cripple it and call it done. (ColorCorrect, Vray Physical Camera, etc.) In a case like particle engine; it is so essential that you can not mess it up. Especially when you market a software for game and motion graphics.

[Anonymous]

Autodesk sucks big time and here's the undeniable reason. A guy called Tyson Ibele has single handedly rewritten pflow from ground up, its multithreaded and fully functional, he has named it tyflow. Go ahead and check it out, it could compete houdini to a distance. Why have we stuck with a redundant company like autodesk?? I have a suggestion, let Max users gather on and throw a fund raiser, then lets buy Max from autodesk and give it to maxon or sidefx or any company other than autodesk, Im sure they will bring Max to glory in no time. I know this sounds silly or maybe stupid, but I have lost hope in autodesk so I wont expect anything from them.

[gavinwhelan3d]

BUY TYFLOW!!!!!!!!!!!!!!!!!!!!!!

[RGhost77]

@gavinwhelan3d They already bought SkinFX , ShaderFX and hired Kees Rijnen and what happened... ShaderFX mostly broken in 3ds max and seems does not develops anymore... SkinFX was closed and we lost good plugin for making muscles. https://forums.autodesk.com/t5/3ds-max-ideas/muscle-jigling-skin-sliding-wrinkling-and-volume-preser... So I don't think that good idea suggest to buy it...

BUY TYFLOW!!!!!!!!!!!!!!!!!!!!!!

---

[gandhics]

@RGhost77 

It was Maya team who hired Kees Rijnen . Autodesk never bought SkinFX code. I heard he sold the code to someone else.

[mateusz_s]

Hello,

Since you get Particle Flow you didn't developed it too much. 

It should have new advanced nodes like in Thinking Particles.

Tyson Ibele, who was developing PFlow is developing his new particle system TyFlow

that looks like PArticle Flow but has lots of advanced funcions..

Why you stop developing PArticle Flow and will you do something about it in max 2020?

I am attaching a screencast from Tysnon Ibele webpage with TyFlow nodes

[Anonymous]

Autodesk is about to make a ton of money off of the release of TyFlow.

If there's any justice in this world they'll take whatever bonuses they were saving for their development and marketing execs and send it to Tyson instead.

[Gregory.Glezakos]

As far as i understand from Tyson's interview, he doesn't have any intention on leaving his daily full time job at Make and the benefit on working from home for them. He mentioned he had already turned down offers in the past from other bigger studios, just for that reason.

Now, in an ideal world, AD would have to come up with a proposal to buy TyFlow code and implement inside Max and at the same time, hire Tyson to remotely support and update the code. But, realistically speaking, this will never happen and it's probably for the best interest of both sides. AD will keep on selling Max, as people who can't get their heads into Houdini, or even TP, would want to use TyFlow as the PFlow replacement and Tyson will keep selling and update TyFlow as a plugin and keep all the rights to himself. We, the end users, may have to pay extra for that tool not having it by default installation inside Max, but in the end of the day that's the Max reality with all the great tools that exist for it and make Max what it is anyway.

I would prefer AD to put all the effort to modernize the interface, update the core of the program to make it super responsive and fast than keep on buying stuff only to drop support afterwards...

Having said that, i wouldn't mind a "free" or "locked down" version of TyFlow inside Max by default, just like Arnold licensing and then if needed buy a "full" license from Tyson...

[Anonymous]

Forget about Tyflow and ParticleFlow, it seems that the future for 3dsmax and Maya is Bifrost Board.

[Anonymous]

(1)one dude made, its making what was Good to have been done for years.
Tyson Ibele.
Tyflow is, and it's getting Amazing.
small, fast, a lot more practical, more Intuitive, many more options, more powerful, 
and the basics Works(at least, a Lot better)

Help him to do this, yet Better, good to all.

Cheers!!

[JohnnyRandom]

LOL, not to harsh on dev,  I will be retired by the time we see Bifrost board come to fruition! It is going to be at least three more major version releases before maxFluids sees another round of heavy development.

TyFlow is a solid step forward and shows what you can do without the constraints of a juggernaut institution to feed.

[Anonymous]

i would suggest that autodesk buys tyflow and implement it and more importantly to hire tyson ( tyflow developer ) and leave the whole particle things at his hands he's genius

i am sure autodesk has tons of money to do so with no problem

[Anonymous]

Won`t happen and with the advent of Bifröst Board irrelevant.

[Anonymous]

Hire Tyson Ibele, remove particle flow and go with Tyflow!!! 😄

[Anonymous]

Already all Better than TyFlow?!

Really,
 pflow is a trauma, I don't plan to touch it again.

Regards!

[Anonymous]

So is this consideration really just bifrost to replace pflow? Since it does what we need. Multithreading, node based, and multiphysics solver?

[Anonymous]

Bifrost (Graph) already includes a Particle System build from basic nodes. However i think what we need is a more high-level, easy to use interface on top of that Graph. ParticleFlow/Tyflow style.