Loading video...

Video Failed to Load

Go Home

NVIDIA did it again.. they trained a GPT that generates human movement instead of text.. next-token prediction, but the tokens are body motions. it's called GPC and it hit a 99.98% success rate reproducing a massive corpus of motion clips.. cartwheels, vaults, flips, all of it. → 99.98% success...

102,590 views • 2 months ago •via X (Twitter)

29 Comments

Chen Tessler's profile picture
Chen Tessler2 months ago

Fully open-source --

How To Prompt's profile picture
How To Prompt2 months ago

Paper:

Albert Renshaw's profile picture
Albert Renshaw2 months ago

Nothing more than stochastic parkour

Husni Marwan's profile picture
Husni Marwan2 months ago

I want to see them collaboratively plays football

Alex 3yb0^'s profile picture
Alex 3yb0^2 months ago

Great! How can I use that with my rigged characters in Blender ?

Frosty40's profile picture
Frosty402 months ago

felt a chill down their spline* fixed it for you

🧩's profile picture
🧩2 months ago

so it's just a basic movement diffusion model?

capt's profile picture
capt2 months ago

Every time people say transformers have reached their limit, someone applies the same idea to a completely different domain. I had a similar reaction after spending time with Claude Opus 5 - it wasn't one feature that impressed me, it was how much more generally capable the model felt. If this trend continues, motion generation is probably just another step, not the destination.

Da Bitcoin Bandit's profile picture
Da Bitcoin Bandit2 months ago

great now install the model in a kill bot

VND's profile picture
VND2 months ago

All this technology to make devs jobs EASIER and CHEAPER to produce things yet the prices are absolutely astronomical for games. Make it make sense.

theH's profile picture
theH2 months ago

cool!

未知's profile picture
未知2 months ago

说实话,99.98%的动作重现成功率确实亮眼,但这恰恰暴露了当前AI在物理世界理解上的致命短板:它只是在像素或骨骼点层面做“下一个标记预测”,本质上跟GPT生成文本没有区别,根本不理解重力、动量、肌肉发力这些物理约束。GPC能完美复现侧手翻,但换个没见过的动作组合可能就崩了。NVIDIA用Transformer暴力堆算力解决动作生成,思路很直接,但离真正的具身智能还差一个物理引擎的距离。这更像是高级动作数据库的插值检索,而不是智能体��…

Trevor West's profile picture
Trevor West2 months ago

As interesting as this is, it was the wrong approach... No human moves perfectly, the real money is in imperfect movement (a perfect model is step one only). The same goes for speech in regards to communication tech. using AI.

ata's profile picture
ata2 months ago

love how committed nvidia is to the whole stack. i will love my future humanoid being able to do these neat tricks

Abdulmuiz Adeyemo's profile picture
Abdulmuiz Adeyemo2 months ago

Looks cool

Sebastian Buzdugan's profile picture
Sebastian Buzdugan2 months ago

i've seen motion models pass replay then fail on foot contact in rollout

Mente Prompt • Inteligencia Artificial's profile picture
Mente Prompt • Inteligencia Artificial2 months ago

great paper from nvidia

CreatAlpha's profile picture
CreatAlpha2 months ago

@grok 这个论文说的什么?能预测机器人的下一个动作?

expulvar's profile picture
expulvar2 months ago

why do i feel tired for the thing?

Alexander Petrov's profile picture
Alexander Petrov2 months ago

So, will a robot actually move around in real world, using it?

bitmin's profile picture
bitmin2 months ago

When NPC's created their own NPC's, what happened to the game?

byMAR.CO's profile picture
byMAR.CO2 months ago

Give it a physical body

Anna A. Sobczak's profile picture
Anna A. Sobczak2 months ago

Does it adapt to different body geometries?

takeshi fujita's profile picture
takeshi fujita2 months ago

、

Aryan's profile picture
Aryan2 months ago

this will be super useful for building high fidelity simulations

BlueSfaira's profile picture
BlueSfaira1 month ago

This is so big for the gaming industry! Could this be mapped to humanoid robots?

Tommaso Bianco's profile picture
Tommaso Bianco2 months ago

If this is the resulting video, does not seem completely natural to me. Besides movements, gravity

PlainSightLogic's profile picture
PlainSightLogic2 months ago

If it can be applied to this, it can be applied to almost anything.

Corsyphus 🚀's profile picture
Corsyphus 🚀2 months ago

Fifa this immediately on my Xbox!

Related Videos

Two data points dropped in the last few months that should terrify every software company that thinks its codebase is a moat. First, one engineer at Cloudflare, working with Claude via AI agents, rebuilt 94% of Next.js, one of the most widely used frontend frameworks on the internet, built over 10 years by a large engineering team in a single week. Total cost was $1,100 in API tokens. The result, called Vinext, is a drop-in replacement that builds production apps up to 4x faster and produces client bundles 57% smaller and customers are already running it in production. Second is Cursor CEO Michael Truell deployed a swarm of hundreds of GPT-5.2 agents that ran uninterrupted for an entire week and built a fully functional web browser from scratch called FastRender. 3 million lines of code, thousands of files and a custom Rust rendering engine with HTML parsing, CSS layout, text shaping, and a custom JavaScript VM. Total cost was roughly $30,000. For context, Google has spent billions of dollars and decades of engineering building Chrome. And the benchmarks say by next year, you will be able to one-shot prompt anything. The moat that software companies spent decades building, the complexity of their codebase, the years it would take a competitor to replicate it, the switching costs that moat assumed humans were the unit of production. AI does not care how long it took you to build it, it only cares how long it takes to rebuild it. And right now, the answer is one week.

Milk Road AI

16,781 views • 5 months ago

Not a preplanned motion sequence. A robot deciding mid-jump what to do next. [📍 paper + demo] Researchers just showed a humanoid doing real parkour using only onboard perception. No motion script, no fixed obstacle layout. The system is called Perceptive Humanoid Parkour (PHP). Instead of memorizing a path, the robot reads depth from its cameras and continuously chooses actions. Step, vault, climb, or roll depending on what geometry appears in front of it. To make that possible, they combine three ideas: First, they stitch together human motion clips into long movement references so the robot learns fluid transitions instead of isolated tricks. Second, they train tracking policies with reinforcement learning so contacts land at the right time and the robot keeps balance during dynamic moves. Finally, everything is distilled into one perception policy that runs directly from depth input to action selection. The result on a Unitree G1: about 3 m/s vaults wall climbs up to 1.25 m nearly one minute continuous obstacle traversal adapting when obstacles move What matters is not the tricks. It is the shift in capability. Earlier humanoids executed motions. This one navigates situations. Once robots react to geometry instead of replaying trajectories, environments stop needing to be predictable. Warehouses, homes, and outdoors suddenly become the same problem. Thanks for sharing, Zhen Wu! Paper + demo: ——— Weekly robotics and AI insights. Subscribe free:

Ilir Aliu

22,127 views • 7 months ago

OpenAI. said. this. publicly. their own engineers just proved one idea on themselves, in writing: stop telling AI what's wrong. hand it the whole broken thing and let it find out they gave GPT-6 Astra a slow test build of their own coding tool. one cause found, a memory bottleneck, one allocator swapped, every turn 25× faster this is GPT-6 Astra, the layer that fixes the cause instead of the symptom, $0 on top of the ChatGPT plan you already pay for: - open ChatGPT or Codex, pick GPT-6 Astra, hand it the whole thing: the folder, the file that takes a minute to open. it works in apps with no API and reads your screen - type one sentence: find the one cause, prove it, fix it, do not patch around it - leave the room. it asks without stopping, keeps working on what does not need your answer, waits only where the answer changes the outcome - keep it in one Codex session with the experimental notes setting on: it remembers across context windows why an earlier fix failed - expect the first pass to land: handed a program with no source, it worked out how it runs 88% of the time first try, 99.2% within four you never find out what was broken. it gets fixed anyway the catch is on the same page. roughly 30% more memory for that speed, and the safety checks can pause a long job until you approve the next step describing the problem was the expensive half of fixing it. that half just ended every hour you spend explaining the symptom to a chat window, someone else has handed theirs over whole bookmark this before the next thing breaks, the playbook for handing a whole job to an AI worker is in the piece below ↓

Argona

107,134 views • 14 days ago

Introducing Immutable Audience: the growth engine for pre-launch Steam games. (btw we didn’t spend $50k on a viral launch agency - so if you think this is cool just share it for free i guess) Game marketing is broken. Every year PC studios spend billions to grow their games, and yet: - they don’t know which channels are actually working - only a fraction of wishlist sources can be tracked - of those people who DO wishlist games, the rate of those who go on to purchase is falling After 8 years building games ourselves, and working with over 700 studios, the need for something new was obvious. So, we built Audience. How it works: 1. Audience pulls in real time data from your players across Steam, social media, ad platforms, influencers and more 2. It stores this marketing data in your player CRM, and uses our Enhanced Attribution to identify the one channel driving 80% of your wishlists 3. Finally, it generates a custom growth audit, reviewing your real time data against winning strategies from hundreds of games to identify the most effective ways to get you wishlists each week During Audience’s beta we’ve already seen incredible results. We helped one game grow by over 300k wishlists in 2 months, and then more than *doubled* the rate of those players who converted into paying customers, compared to relying on Steam alone. For the last few months the team at Immutable has been heads down building. We’re incredibly grateful to our community for your support as we onboard the world. Slowly, then all at once. To celebrate the launch, we’re offering one month of Audience for free to any studio that signs up by commenting on this video. And for the first 100 studios that comment, we’ll create you a custom growth plan for free. Comment “Audience” and we’ll send it through.

Robbie Ferguson | Immutable

24,819 views • 1 month ago

This work makes a humanoid robot do simple parkour moves by looking with a depth camera and choosing the right move on the fly. The big deal is that it turns lots of small human moves into long, real-time robot behavior, without hand-coding every transition or retraining for each new course. A humanoid robot is usually good at steady walking, but it often fails when it has to do fast moves like jumping up, vaulting, or rolling, and then keep going to the next obstacle. The hard part is that you cannot easily collect training data for every possible obstacle shape, distance, and mistake, so robots end up learning a few moves that only work in a narrow setup. This work starts from short clips of real human parkour moves, like stepping over, vaulting, climbing, and rolling. It uses motion matching, which is basically a smart “pick the next clip that fits best right now” search, to stitch those short clips into a long, smooth plan that looks like a human doing a whole course. Then it trains a controller with reinforcement learning (RL), which means the robot learns by trial and error to copy that plan while staying balanced and not falling. After training separate expert controllers for different moves, it compresses them into 1 controller that uses only onboard depth sensing and a simple “go this fast in this direction” command. In real tests on a Unitree G1 humanoid, it can clear multiple obstacles in a row, adapt when obstacles get moved, and climb a wall up to 1.25m.

Rohan Paul

37,121 views • 7 months ago

Why the character movement in my custom game engine felt janky and how I fixed it. In a game engine, most often, a character moves using the physics engine. Meaning, the player is not just a coordinate in space but a physical body. It has velocity, it handles collisions, and it interacts with the world. Now, as you might know, physics engines need stability. If you run them at variable framerates, things start breaking. Objects phase through walls or fly off into space because the math becomes unpredictable. This is why most game engines lock their physics loop to a 60Hz fixed rate. But here’s the problem: If you have a high-end system, you don't want to limit it at 60 FPS. That's a waste of good hardware. Now, that said, if the GPU is rendering at 144 FPS but the player's position (physics driven) only updates 60 times a second, it creates a micro-stutter that ruins the "smooth" feel of the game. A good way to fix this is to treat the character as two separate things: 1. The Physics Body (Invisible part): This is the "real" character. It lives in the 60Hz physics world, it moves the player and handles collisions. 2. The Visual Model and Camera (Visible part): This is what the player actually sees. It doesn't care about collisions, its only job is to look nice and smooth at whatever framerate the GPU is pushing. Once you have this separation, you can use interpolation to keep them in sync. Every time the physics clock ticks, you save the previous position of the invisible body before moving it to the new one. Between those ticks, calculate how far we are between the last physics update and the next one. By using this to drive the visible parts of the game, the stutters disappear. The physics loop stays fixed behind the scenes, while the visuals slide smoothly between the snapshots. Example: - Right after a tick: blend_weight= 0.0 (The visual model stays at the old physics position). - Halfway to the next: blend_weight= 0.5 (The visual model slides to the middle point). - Just before the next: blend_weight= 0.9 (The visual model is almost at the new physics position). Pro-Tip A critical mistake I made initially, and one many devs make, is parenting the camera and visible parts directly to the player body. If you do this, the camera inherits the discrete 60Hz physics movement by default. In that setup, interpolation won't work because the camera is "stuck" to the physics clock. For this fix to work you must decouple the camera and visuals from the body and move them separately. Player movement processing in Detis Engine: - fixed_process: Physics runs at 60Hz. Handles collisions and raw movement. - process: Variable rate. Mainly used for player input caching in the player case. - late_process: Variable rate. Handles interpolated camera movement after physics and everything else is done being processed. - render. Submits the final interpolated transforms to the GPU. The test environment in the video is running on an old 2070-based laptop. Hopefully the video compression won't introduce any stutter... I’m sharing this in hopes it helps a fellow dev. Cheers.

Ioannis Koukourakis

48,703 views • 8 months ago