Don't get a "Insert Keyframe Menu" with either the hot key of using the drop down menues. I assume that's a 4.2 thing and that the key frame is set for all possibilities in the menu? And I see one question answered when I click to open the "Object Transformation" in the Time line there is a LAUNDRY LIST of things going on. Oh dear gawd.
*breathe* *just breathe*
Took me 5 minutes to figure out how to grab the 33?!* handle in the Graph Editor to change the ease in/out. And scaling in the graph editor is just like scaling in the 3d viewport... the closer the cursor is to the handle the faster it scales. THAT was five minutes of hair pulling. But lesson learned (oh yeah, I had to right-click to chose that damn handle.) lol.
... but yay!!! I have a cube animation. And we're underway
Yes, there are quite a few changes in 4.2, especially in the Animation department. (For instance, the Insert Keyframe hotkey has been changed from I to K. I will Insert default Keyframes, that can be set in the Preferences.)
Luckily, the new CORE has the Fundamentals Courses all updated for Blender 4.2.
Maybe something to watch after you finished with the Blender Basics.
MMartin Bergwerf... Thank you - "K" does the trick. And if I had the presence of mind to read the drop down menu from "Object" --> "Animation" I might have deduced that. And that folks is how I lost my job at the CIA.
<> 7:30 When changing the initial color "blue" (with AutoKeying on), why was it necessary to click the keyframe dot at the right of the base color, and when subsequently changing the same Base Color to "green" did we NOT have to do the clicky thing. Shouldn't have the first change been auto keyframed right at the gate? Am I trying to be too technical here? Should I be shutting up and just follow along and not ask so many questions?
Same timestamp area... if the color wasn't changed until frame 10, why is it not white (or whatever color the default cube starts out at) at frames 1-9, and then turn to blue at frame 10?
Dear god, you can edit the shader node curves as well? Oh I can see the Graph Editor being a fresh new hell to step into. (yeah. Yeah. One step at a time - and baby steps at that).
When setting my camera, I had a helluva time trying to zoom my camera back. It would zoom back, but then snap back to the initial position. After some tinkering around, I found that a keyframe was set for my camera and was bouncing it back, just like it did to the cube at the very beginning of this tut. After I deleted the camera keyframe, all was well again in Mudville. Was this do to the AutoKey still being on?
The questions you get from watching and going through a tut twice, eh? (no I'm not Canadian. lol)
Don't worry Scott, Blender is too huge of a beast, it's impossible to hold it all in. Even the guys that make the tutorials have to watch their own tutorials after a while to get a refresher since they forget how to do things all the time. You don't have to learn all of that and memorize it all in the Basics course, it's just an overview. If you later decide to get fully into animation, the Fundamentals of Animation and other animation courses will explain all of it yet again with much more detail, better to not get overwhelmed right now. Most likely you'll pivot into modeling after watching the basics, starting with the Fundamentals of Mesh modeling, and that is going to be a big fun challenge.
OOmar Domenech... you're right. This is an overview and I need to put this into perspective. I forgot this was more of a precursor course to whet my appetite. Silly me. lol. Probably won't stop me from asking questions I suppose.
Have a good weekend
Shouldn't have the first change been auto keyframed right at the gate?
Good question! Blender has a few preferences for when to set keyframes when auto-keying is on, but the short answer is that if a key was set every time you changed any value, the result would be an absolute chaos of unnecessary keyframes. So, in the Properties Editor, Blender only sets an auto-key for properties that already have a keyframe set. But when working in the 3D View, Blender assumes you do want to add a keyframe even if that property has no keys yet. I like to make this consistent by going to Preferences -> Animation -> Keyframes -> Only Insert Available, but that's just personal preference.
if the color wasn't changed until frame 10, why is it not white (or whatever color the default cube starts out at) at frames 1-9, and then turn to blue at frame 10?
Setting a keyframe is saving a value at a particular point in time, so if there are no previous keyframes, then nothing has saved that initial white color. The first 'saved' color is now blue, so it starts out as blue.
Was this do to the AutoKey still being on?
Yep, that's exactly it! It's extremely common to accidentally keyframe things like this, I end up doing it all the time if I have auto-key on, so I usually recommend leaving it off when not actively needed.
Hope that helps!