Hello there,
I'm a professionnal maya user and I've been using the software for quite a bit, but I was wondering;
Is there a way to limit the amount OR Control the type of construction history that can be stacked on an object?
Let's be honest, When Modeling, the history stack is Useless 99% of the time;
It's relatively rare that you'll need to tweak parameters on old modifiers in the stack and doing so will often straight up Not Work or Destroys the Mesh. Moreover, it quickly Slows Down the scene, sometime Create Problematic Ghost Nodes that needs to be manually deleted, and in the end, it Is the Cause of Most of the Crashs.
I know it's Possible to Completely Turn Off history but it is NOT a Viable Solution because you can't even tweak the parameters of the current modifier you're trying to apply on the object.
What would be a better alternative in my opinion, is to Be Able to Choose the Amount of Operations kept in the History Queue.
So for exemple, if the history queue is set to Keep only 1 Operation, We could actually perform an action (Let's say a bevel) and be able to tweak the parameters as desired, UNTIL a new operation is applied. Then the older modifier's history would be Automatically Deleted and Replaced by the New Operation.
And Finally, (this is a less crucial feature but,) beign able to Choose what type of History should be conserved would also be efficient.
For exemple, it would be useful to have the possibility to Turn off history for specific operation like UVs , Mesh display operation, etc. While keeping Turned on the History Queue for geometry deformers.
So yeah, am I just a simp and turns out that there's already hidden controls over history in Maya?
Or Am I stuck to have to manually delete history on all my objects every 3sec forever?
In the later case, I'm convinced that if the implementation of (such a simple feature as) History Limitation was to be made in the future, it would Greatly Benifit all Maya users and improve the overall quality of the software!
Thank you,
-Eti
PS. It seems that one of your employee Mr. @trevor.adams (Bonjour mon fellow Montrealais!) has touched on similar ideas in a thread 2 years ago. It looks like it was never adressed and then archived... So I'm hoping this message has been to the point and that other users and devs reading this will empathise with us :')
