Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Mesh Concept | Universal Answer Any hash. Any defense. Call it anywhere. Formations, shifts, and motions change the picture. The QB progression never changes. Pre-Snap: Alert Okie (6-step speed out) Progression 1 - Rail 2 - Low Mesh 3 - OTB 4 - High Mesh Rules & Landmarks Rail...

12,503 Aufrufe • vor 6 Monaten •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

Ferris State HC Tony Annese - Mesh (QB/Ball Carrier) & Motion Fundamentals QB Mesh Fundamentals - Regardless of play, the first thing the QB needs to do to make sure he has a good mesh is stab the ball back off his hip towards the ball carrier as far as he can. - His arms should be straightened with his eyes at the HOK. - The ball should move with the back through his track. - If the ball is pulled the decision must be made by the time the ball gets to the QB's front hip. Ball Carrier Mesh Fundamentals - The potential ball carrier is the one that is responsible for his track. He needs to make sure his is at the mesh point that the QB is creating. - He must maintain a pocket that is firm enough to secure the ball but loose enough that the QB can pull the ball if the read is a pull read. - Do not deviate from the track until you fully clear the mesh. - If you do not get the ball then track away from the HOK and make him chase you. Motion Fundamentals - All of our motions start up at FULL SPEED! It is incredibly important to make every motion at full speed so the QB has a consistent timing. - The QB is responsible for sending the motion back on every play except for the triple option. - This allows us to control each motion easier. - Every Jet motion should be timed as if the jet back was getting the ball regardless of play. - The motion back will change his depth based on play. - This allows us to use motion with a multitude of schemes. - The motion stops at different spots on different plays and each perimeter player must understand where he should stop for each play.

James Light

19,145 Aufrufe • vor 8 Monaten

Ferris State HC Tony Annese - GT Counter Triple Option - Quarterback Fundamentals... Catch the ball and make a 1/8th turn to face the DE you are reading. Stab the ball back off of your back hip. Mesh with the RB while reading the DE. The DE must squeeze hard enough to tackle the RB in order for you to pull the ball. If he does pull and seed the ball at your chest. Attack the pitch key's outside shoulder (1st man outside the tackle box). If he darts to the slot keep the ball. If he stays with you, pitch the ball and avoid the hit. -Running Back Fundamentals... Take 2 shuffle steps for depth (almost like a OT pass set). Wait for the ball to be brought back to you. Once it is, track behind your pullers making sure to keep a big pocket so the QB can get a good mesh. Once you get the ball follow your pulling tackle and fit off of his block. Get upfield at the first opportunity. -Slot Fundamentals... The motion timing is on the slot on this play. Motion as late as possible to still get in pitch position (we would try to motion at the snap on this play but depending on how fast each slot is they may have to cheat it a bit). Motion at the QB's heals and run full speed. Once you get into pitch phase yell for the ball to let the QB know you are there and stay in pitch phase till you get the ball. -Perimeter Blocking - On this play we will switch block with our WR and Slot. That means the WR is going to block the high safety and the Slot will block the corner. We leave the OLB as the pitch key. We still want to make sure we are square to the man we are blocking so the slot will go flat down the LOS until he gets to the same vertical plane as the corner and then he will climb to block him.

James Light

25,590 Aufrufe • vor 3 Monaten

Vibe Coding 3D Garment Software with ThreeJS : A Small Step For Me So, after modeling the human i did what any reasonable vibe coder would do, i asked codex how to get clothes for my models After it was done running subliminal ad campaigns for Marvelous Designer and CLO 3D, i asked it to explain their architecture to me and adapt it to my threejs app. Guess what it did? You damn right, it built the most basic shit interpretation you can think of. And this is the average interaction the Anti-AI coders have until they conclude that AI is slop and/or it can only work if you micro manage it on every line of code. Well, eons of humanities knowledge are now packaged in tiny silicon and transferred across the globe in realtime, available on tap. So anyways i just iterated quite a lot over it, told it repeatedly why it was bad (the initial one used rapier physics and a naive cloth simulation) We found out together that: 1. A ground truth document model is needed 2. The visual mesh in 3D should be triangulated from the 2D shape 3. The physical object is running independently through different solvers: - A fast proxy which is generated by reading all the bones in runtime and just inflating these areas with spheres and capsules - A medium quality proxy which resamples the human model and creates a lower-poly mesh for simulations - Full mesh simulation (can't run it, every simulation tick takes about 5 minutes on my machine) It ended the session by telling me that this is still crap because it runs everything on CPU (thanks, not that i care, but i guess we'll be fixing that?) Oh yea also built a 2D canvas editor with boolean operations so i can build cool stuff like ponchos. It also allows me to mark stitches between two objects, which is how the shirt in the video pulls towards the other half. The garment's properties and materials are not yet exposed, yes i know it looks very stiff like a poncho made from a persian rug, we're working on it, okay? So, yea, tbh this is another endless rabbit hole, let's go i guess

robot 2.0

39,381 Aufrufe • vor 4 Monaten

Jev + Opus 5.5: Anthropic's new model beats GPT-6 Astra for 1/5 the cost, and 4 API changes will 400 your agent before it writes a single line I pulled these 10 steps from the migration docs so you don't learn them in production step 1 → $4 / $20 per 1M. Opus 5 was $5 / $25. cache reads dropped from $0.50 to $0.20 step 2 → 66.4% on Terminal-Bench 4.0 vs GPT-6 Astra 57.9% and Opus 5 52.3%. +14.1 points in one release, and on FrontierCode it beats Astra at default effort for 1/5 the cost step 3 → thinking can't be turned off anymore. send thinking: disabled and you get a 400. drop the field, set effort step 4 → tool_choice any and tool are gone. 400. switch to auto + strict step 5 → edit anything above a thinking block and the request dies. append only, or opt into drop_block step 6 → computer_20251124 is dead on the API. 400. move to computer_toolset_20260801 step 7 → the quiet one: default effort fell from high to medium. your agent thinks less than you set it up to and nothing tells you step 8 → hop Opus 5.5 → Sonnet 5 → Opus 5.5 and you pay 4.36 instead of 3.32. +31%, the cache dies and Sonnet can't read Opus's reasoning step 9 → change effort at the top of the request and the cache is gone. Jev sets it per message and the cache stays step 10 → switch fast - standard mid-session and it's a full cache miss. Jev picks speed once, on turn one one model, three knobs, zero 400s. that is Jev + Opus 5.5 send this to your Claude Code before you touch the model ID, then read my full Jev deep dive in the article below ↓

Carnage

16,674 Aufrufe • vor 5 Tagen