He does

@@Junk1234. not really

@@AhmedTarbine what evs

Why thank you!!!

Could be that the points are too close together or the 3 points don’t really work well together. I’ve had times where my track is good but the floor is giving me problems. Just try to keep selecting different sets until one works or just track some points manually for like 10 frames and then solve the camera and then try using those points as the floor. Very finicky but you’ll get the hang of it. Hope that helps!

Haven't tried doing a separate track just for the floor. Will definitely give it a try. Thanks for taking the time to reply!@@Jacob_Zirkle

@@guillecareaga yeah ofc! It should be within your same track for the camera just adding points to it.

Yeah that just means that you don’t have atleast 8 trackers that exist in your a and b keyframe range. You might have more than 8 in the range but if they don’t exist all throughout the range then they aren’t common and blender has a hard time tracking. Try detecting more features and don’t delete as many or select a slightly smaller range for a and b. Blender just needs 8 at one time for a track but the more the better

@@Jacob_Zirkle okay thanks for your response, I will see if I can solve it now

Just because it’s easier to work with and won’t cause problems with the camera tracking. Also it’s not tied down to a specific frame rate so there’s nothing that can happen if you accidentally set the wrong frame rate. I’ve had blender be weird before with certain codecs and video formats so it just helps with that.

It is the only thing that’s a little finicky is getting a shadow pass since eevee doesn’t have the ability to do shadow catcher objects. I’m looking into some workflows to hopefully do a future tutorial with eevee for low end vfx so stay tuned

@@Jacob_Zirkle Ok, thank you!

Hold z and then go to rendered view once your viewing through the camera

Did you get an answer? None of his videos show that

Sup man, I have the same error, did you figured a solution?

Sometimes certain things like camera tracking can act weird depending on the codecs you use. I’ve had problem with video files before and with the footage converted to a sequence it’s not tied down to frame rate. Just a good habit to start getting into as artist like working with sequences better!

@@Jacob_Zirkle thank you very mush

I'm also having the problem "Failed to solve the motion: most likely there are no good keyframes" first it solves correctly but if i press solve again (with the same clean up) it throws that error, it doesn't even make sense, what is going on with this feature?????

How many tracks do you have left

You’re totally right! I left out that step for this tutorial because I didn’t want to get too complicated and overwhelm beginners.

Don’t take this the wrong way, but if you want to continue with vfx or most post workflows like color, compositing, etc, you’ll have to understand nodes. It’s a fundamental part of most of the work and it’s much better for multiuser workflows where projects go through many different hands. I don’t believe you’ve really put in the time to learn it since nodes are actually relatively straight forward compared to other workflows since it’s more visual. Again not an attack, but practice makes perfect and so especially for nodes unless you’re actually using them yourself and problem solving with them, you won’t learn as fast if you’re just watching tutorials to understand. Hopefully this helps and you can figure out a learning method that works for you to learn nodes since they are a game changer once you understand!

You have to put everything in the same collection "Foreground"

Actually working on a paid full compositing course for Nuke right now so stay tuned!

Another question what we will hit? "render Image" or "render animation"?