Sometimes when I hit undo it will skip the last change I made and undo the one before it. Then when I hit the undo again, it fixes the lst undo and undoes the one I wanted.

example: 1. I rotate a camera 2. I move a prop 3. I hit undo and the camera rotates back but the box stays put. 4. I hit undo again and the camera goes back the the rotated position and the box goes back to the unmoved position.

I've had this problem in P8 and now in PP2012. Does anyone else have this issue or is it possibly my computer being difficult? I don't have this probmlem in anything but poser and I'm using xp.

You know this is why SM knows almost nothing about Poser bugs. grin

Ask them first, and if they are clueless, then come ask us.

I figured it might be my computer so I thought i'd ask here and if others had it I would go to SM. But I suppose I could go straight to them and let them tell me my computer is messed up.

Or maybe if two of you reported the same thing, they'd think "hmm, maybe we have a bug".

Seriously I can't tell you how many times I'm on a call with them and I say "somebody in the forum says blah blah" and they say "well, we've never heard of this - no previous reports along these lines - who is it - what is the computer setup - what versions of this and that" and I go "hell I don't know any of that" and I am not going to relay all that info back and forth. They have a customer support staff for that very purpose.

This isn't about you or me wasting time. It's about them not knowing we're even having this conversation, first of all, second you not getting to tell them your story and add that to other stories, and third maybe they already know about it and can tell you what they know.

I have had this exact problem with Poser 8 and Poser Pro 2010.

However, I didn't know that if I hit undo again, it would work.

I never report bugs because I've had negative experiences doing so in the past (though not with Poser support). I got tired of being told that every bug I reported was a problem with my machine, and concluded that reporting bugs was a waste of time for people like me. If a bug affects enough people, it will get reported by someone else, and if it doesn't affect very many, then it won't be high enough priority to be fixed.

ETA:

I ask about possible bugs in this forum because I want to know 1. if anyone else experiences them (because if not, then maybe it is a problem with my machine) 2. if anyone knows the cause (because sometimes there are specific triggers) 3. if anyone knows a work around.

I've never tried to contact SM, but I'm going to guess that reporting a bug that may not even be a bug to SM support is not necessarily going to get me a quick answer that will help me finish a render, whereas posting a question in this forum has definitely helped, and I've often got solutions with remarkable speed.

Well, I've reported this. I'll see what they say and if I am albe to get it resolved, I'll report back here too.

Moriador, please DO report bugs you find. As BB already explained, the people who try to find them need hints where to look at. The more people report a bug the more data is there to find it.  It may not give you a quick workaround, but it will help SM to find a real solution. Asking the forum for a quick workaround is fine too, best to do both.

This is actually a known bug. IT's just so squirmy it's never been pinned down. Any input you have will help. I suspect it has to do with using the space mouse to move cameras. Any of you have a space mouse?

I don't even know what a space mouse is. I just have a simple opticle wheel mouse.

Dang, so it's not the space mouse that's the trigger. OK In my case if I set my preferred state so camera undo's aren't stored. (There's an option in each camera's properties) I never hit this bug. It only seems to trip when you flit back n' forth between moving an object and moving cameras. Though as you've discovered there's more to it than just that. That missing X-factor keeps this squirmy bug alive.

If you think you have figured out what that X is please let me know. This is one of my bugs and I want it dead.

I thought I'd let you know what the last was in trying to resolve this. Basically they could not reproduce it so they couldn't help much. The 2 suggestions they made were 1. make sure I give the program a chance to finish the last thing before trying to undo. Poser might be slow and not have updated the undo list. 2. uninstall and reinstall poser.

Hope this helps somebody.

Quote - I thought I'd let you know what the last was in trying to resolve this. Basically they could not reproduce it so they couldn't help much. The 2 suggestions they made were 1. make sure I give the program a chance to finish the last thing before trying to undo. Poser might be slow and not have updated the undo list. 2. uninstall and reinstall poser.

Hope this helps somebody.

Doesn't help, but it does reinforce my beliefs about of reporting only the most critical or persistent bugs. :)

Well, maybe the first suggestion will make a difference. It's worth keeping in mind.

The SM and Poser staff are quite active and persistent on finding and killing bugs.

But, and that is the same thing for any software ! ! !

To kill a bug, they have to know it is there, find it, and be able to reproduce it.
Once they can reproduce a bug, they can track it down and fix it.

But, there are soooo many different systems out there, so many little veriations, and be asured, every bit of information helps.
So allways document your reports as complete as you possibly can.

Happy Posering