robcat2075

I was exaggerating a bit. I hope. He has some sort of health complication of which I don't know the exact details.

I did suggest v17 earlier and I haven't been deleted. Now we have three people with a video problem in v18. Before it was just ToreB as ar as I knew. Matt and nemyax, do you have NVidia video cards? Something has changed since v18c. We'll need to get Steffen to look at that when he gets out of the ICU.

If you point a camera or a kleig light at the ground plane and look at that from another angle , you should be able to see the portion of their field-of-view cone that is above the ground. Instead it's all being obscured by the ground plane. I just tried some earlier versions. The problem first appears in v18c

That is definitely a bug! That is new, I get it in v18f but not in v17. I had not noticed it before. I will write that one up and report it to Steffen.

Turn off Mirror mode. I'm sure that's not the problem but you just never want that on unless you WANT it on. Give v17 a try.

nemyax, another thing to try... In v18... In Tools>Options>Global try switching "Real-time driver" to whatever it's not set on now and restart.

from the 1970's... MK0ITXBWpHE Edit: corrected link:

I tend to do that with FK spines when posing. Blender has never given me trouble with undos Another reason I don't frequently do that with chains of bones is that rotating them together forces them all to have identical angles of rotation. It's exceedingly rare that I will want that so... i just do them one at a time... plunk, plunk, plunk... and get what I really wanted.

Yes, update your video driver, restart and see what happens. You may also try downloading and installing v17 and see how that does. You can have several versions of A:M installed with the same license. Copy the master0.lic file from your v18 folder to your v17 folder. There was a time about 10 years ago where if you even looked at the corner of the keyboard where CTRL-Z is it would crash. Maybe that's why I got away from using undo much except for the most trivial things. What are you doing that needs to have multiple bones moved at once?

It IS pinned. I'm not sure what more one does.

Happy Birthday to the finest Tinkering Gnome in all of A:M-land!

I have noticed that before. It's fairly rare that I move any bones simultaneously, except on a long chain of bones like a monkey tail. That happens because (I think) one user interaction may be more steps internally than we perceive. I just did a quick test and it appears that the undo buffer records rotates as a succession of small units (one degree?) added together In some situations, deleting the keyframes your initial move made might get you "undone" faster than "undo" will. Tell us what's happening.

You are right. So far, this list only goes back five years so it doesn't reach back to tuts I did for TWO. I've added this one and someday I'll get around to sorting through all the TWO vids.

You can't turn off 'no pick" temporarily?

Do all our post counters get reset to zero?

That sounds like a great relocation! Good-bye moose! I hope it goes smoothly for you and we see you back here again.

So is the forum going to look like it does now or is it still going to be a huge change?

Hey, those worked pretty well!

Currently, I'm thinking an Intel i7-4770k is a good better-performance but not absurdly-expensive choice. A:M doesn't make huge video card demands. Most of the rendering is in the CPU although the ScreenSpace Ambient Occlusion(SSAO) effect added in V18 is done by the video card. You DO want an AMD or NVidia video card and not the Intel graphics that are built into the CPU.

I'll note that Mark has noted before that he wasn't using bias adjustments and that has motivated me to depend on them quite a bit less which has led me to making better meshes overall.

Thanks Matt!

If you're doing what you're doing without needing bias adjustments... keep doing what you're doing! It looks great!

that's freaky! It's like they are vacuuming up the moss on the ground.

The behavior of any default bias is to be parallel to an imaginary line between the next and previous CP on the spline. Bias alpha and gamma adjustments are like offsets from that imaginary line. If the next or previous CP is moved across that line, a non default alpha or gamma bias will flip to maintain the same offset to the imaginary line as before. However, that is only in the modeler, where you do want the bias to truly represent its offset to the imaginary line. Bias "flipping" (if that's what we are talking about) is normal in the modeler, but is prevented from happening in animation. If there is a case where biases flip in animation that would be something to look at here. To avoid annoying bias flipping in the modeler, do bias adjustments last in your workflow, after you are fairly certain your CPs are as best placed as they can be.

I recommend the annual $79 subscription. That way you're always up to date with the current version.