Somebody must have already mentioned this (I didn't read all the messages above): 1. It's probably too late for CL to add the "multiple undo" feature to P6. They are already planning what to do with P7. 2. If they do decide they have the budget to add the feature to P7, any use of "multiple undo" will be a far worse RAM hit than the memory bug that affects complex scene renders. 3. If they try to make "multiple undo" a read/write function to scratch disk, this will slow down the Windows version quite a bit, and will probably kill the Mac version, which already has severe problems with excessive page-outs.

YesADoodlyDiddlie!!!

Yes, definately!!

*"If they try to make "multiple undo" a read/write function to
scratch disk, this will slow down the Windows version quite
a bit, and will probably kill the Mac version, which already
has severe problems with excessive page-outs."

I tend to agree but i think the problem would be the
nature of poser files more than an OS problem
for Windows or MAC OSX.
In Maxon Cinema4DXL i have gone backwards 40 steps
no problem in dense scenes containing millions of polys.
On an old Mac G3 with 352 megs of Ram. Message edited on: 05/07/2005 12:55

Multiple undo... you mean like the basic staple of all other MODERN software worthy of note? YES! That would be more than welcome. Especially if done in RAM, not to disc.

Yes I would like multiple undos. Preferably all the way back to the first action performed, but at least up to 10 undos back if more aren't possible.

YES! YES! YES!! :)

Yes. Although I'd be happy if they just got their single undo working correctly.

Y E S

I'll sign up for that in a hearbeat.

YES!

In a word....YEA!

YES!!!!!!!!!!!!!!!!!!!!!!!!

Yes please :)

Yes, Yes, Yes, Yes, Yes!

Yes indeedee! Oh! and please fix the damned memory problems. Just had to add this little bit extra. 8)

Message edited on: 05/07/2005 15:43

Yes Sir! Want Multiple UNDO NOW! ;-)

I think the problem that Carolly points out isn't quite as bad as you might think. Yeah, we are talking about lots of 3d details, but they currently only support the change of a single dial. So, it would just be a matter of retaining N dial changes....which is N x 16 bytes (or whatever a floating point value is) It's not that bad. You would have to recalculate the position after the undo....but you are doing that with dial changes. At worse, it would be like having 30 automatic pose dots in queue. I doubt that is why they never implimented it. It's probably just a can of worms with lower shiny factor than the other options that fall ahead of it on the list of upcoming features. eric

It depends on what is being undone. Deleting a character needs that a LOT of information must be remembered for the delete to be undone.

Yes for me too please ! no matter how much info it need to remember

OMG, YES, YES....and oh, YES...that would be wonderful!

Oh yes, yes, yes, yes

YES!!!

Yes, please!!

I vote a resounding yes, but I also agree that the current 1 undo should work "correctly." By that I mean, why are there times when I can undo, but at other times, I just cannot? On the multiple undo plea though, I don't know about what everyone else thinks, but I think if they even gave us 3, that would be enough to save our tails many times over. I know I have spent many a night thinking, "Argh, if only I could go back 2 actions..." The lack of multiple undos has taught me one valuable lesson though...Save early, save often!

Yes Please! And how about a SEARCH FUNCTION for the libraries! My runtime is massive and it's impossible to find anything!

Unconditional multiple undo's would require a rewrite of Poser code. Now we'd all like that for a number of reasons totally unrelated to undo's!!! But if it hasn't happened to date, in fact not even a part of the core Poser code has been rewritten in what 10 years, or ever, then it ain't likely to happen anytime soon for a trivial - in marketing terms - reason like no undo's. But a conditional multiple undo might be do-able without a rewrite. Changing dial values for example doesn't require any complex state retention, just store the prior value(s) and redo the action to equate to an undo. That should be easy to do and deterministic enough (ie. what is covered by multiple undo and when) to be viable.

Of course, yes. It's the first "new" option I looked for and nearly cried when it was never mentioned. But I'll tell you, I'd would take One Undo that actually worked and wouldn't crash the proggie. It's so inutitive to include multiple undos, my only fear is they haven't because they can't. Without a complete rebuild. [same fear exists about resolving the memory issue, by the way] Emily

YES It would rescue me from the times I make a mistake and wish for a do over.

Oh YES!!! please

Max supports something like 20 undos, even old version 3.1, Photoshop does the same, I'd say YES but Poser 6 still has memory problems, doesn't it? Conditional YES, if it desn't make memory problems worse.

YES!!!

User configurable undo would be the best. This would let you, the user, decide how much of your system resources would be used by undo. Those with modest systems wouldn't have to use precious resources for numerous undo levels unless they wanted to.

It's time for CL to wake up and smell the roses, multiple undo is not a new concept, and is a requirement for increased productivity.

Yes please. I would also like to select the number of UNDOs from an option menu. Sometimes I want zero undos, sometimes 20. Thanks

Given the many times it's been requested, I'd say that they haven't implemented it because: A. They're stupid. B. They're just being mean. C. It'd be really, really hard and require messing with code that works and was written be people long gone and might be likely to cause more damage than it's possibly worth to them. Take your choice. Currently, the strategy seems to have been bolt 3rd party add-ons to the old core. Maybe, if the Shade folks keep it long enough, there will be a complete redesign and you'll get undo.

Yes, definately! And I don't see why it should be so difficult to do. You can already keep different configurations of your scene in the various frames of an animation. This is EXACTLY the same kind of stuff that would be in a typical Undo!

1. If it can be done in LW, C4D, Vue, Bryce (!), and a myriad other 3D applications then the argumentation about memory usage is moot - give it up already. I've done multiple undos in C4D with hundreds of thousands of polygons, stage lights (dozens), cameras, complex animations involving XPresso nodes - Poser can't come close to that complexity and it can't do multiple undos?! Quoting the effable P&T: Bullshit!

2. Thank you wolf359 for making my point before I found this post! :)

3. lmckenzie: My vote = C

It has already been stated in another thread that the programmers do not think it can be done. Translated, that means that the codebase is such a noodly, intractable mess that only by completely reworking it could it be made to implement features that have been in every other application for over a decade. :)

KDoug: Animation frames only store value changes in keys - not additions/removals, application of Pose settings, etc. But your point is taken (and I've already made it in another thread).

Message edited on: 05/07/2005 20:28

Y!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Yea.

Yes please and don't just do it for P6. I have P5 and don't want to upgrade just yet. Heck, I just have scratched the surface of P5!

Yes

No ... I never really missed it. I use CONTROL-s instead from time to time ;-) But I desperately beg for an enhancement to the firefly renderer to be able to render a glow effect like in Vue which is so incredibly cool! And there is no way to get it out of Poser. I know some tricks (like this gather-node which is cool too, but it still is not this glowing aura of Vue d'Esprit.)

YES. I don't understand why we have to sign a petition for something much older programs already have. Only problem is the one undo we have works only when it feels like it. ;o)

Yes Please. Poser hasn't been an amateur program for three releases. Why is it still being coded that way?

My hand is UP!

YES... that would be great.

There should a search-and-correct feature for all files (texture AND .obj) that .cr2 (etc) files point to. Like the "Correct Reference" downloadable utility, but built-in and also correcting .obj file references.

Message edited on: 05/08/2005 00:59

If I didn't answer the 'petition': Yes, yes, yes, and yes, yes! At least for changes that impact dial settings (channels)!

That would be a godsend. YES!!!

Yes please!