Загрузка видео...

Не удалось загрузить видео

На главную

1/5 🧵 Three.js Blocks Physics demos are live 🚀 Three.js-first API, WebGL fallback ✅. Native Mesh/InstancedMesh/BatchedMesh integration. Runs in a Service Worker with instant SharedArrayBuffer sync. Physics is just so fast. Surf Mode is getting better, try it! 👀🎮

35,557 просмотров • 9 месяцев назад •via X (Twitter)

Комментарии: 20

Фото профиля Renaud
Renaud9 месяцев назад

2/5 Physics is FAST, thousands of bodies build & load in a few ms. Collisions: BVH + frustum culling + spatial hashing. Runs in a Worker with instant scene sync via SharedArrayBuffer + interpolation for buttery-smooth movements. See by yourself:

Фото профиля Renaud
Renaud9 месяцев назад

3/5 Physics is fully customizable via Model Presets + Extensions. For the CS Surf demo, I start from a Half-Life preset, then override movement + collision rules to match that CS 1.6 surf feel. 2026 is going to be fun for 3D web games 😄 Demo:

Фото профиля Renaud
Renaud9 месяцев назад

4/5 Designed for Three.js from day one → adding collisions is trivial. Register thousands of instances of a BatchedMesh as individual static bodies: physics.addBody(BodyType.STATIC, batchedMesh) That’s it. Optimized, each instance can be tuned. Demo:

Фото профиля Renaud
Renaud9 месяцев назад

5/5 Best part: collisions are automatic + blazing fast thanks to three-mesh-bvh, with fully customizable responses. This is an early sneak peek, API cleanup & proper alpha release coming soon 👀 Join the waitlist (new batch this weekend!):

Фото профиля Garrett Johnson
Garrett Johnson9 месяцев назад

I see three-mesh-bvh 👀🔥 This looks great!

Фото профиля Razel
Razel9 месяцев назад

I’m literally surfing the web🥹

Фото профиля Andrew Eiche
Andrew Eiche9 месяцев назад

Is this a home grown physics engine?

Фото профиля Renaud
Renaud9 месяцев назад

Yes!

Фото профиля Andrew Eiche
Andrew Eiche9 месяцев назад

Interesting choice. I’ve been using Jolt, but I also need network rollback and some other complicated features. For most it looks like what you have is excellent.

Фото профиля Kongzi
Kongzi9 месяцев назад

Build Wars is heating up on MultiversX – still wide open for submissions till Jan 13! $60K+ prizes up for grabs: - $10K EGLD cash ($3K per track: DeFi, Gaming, Infra/Tools + $1K best AI) - Token prizes: $2K FOXSY, $1K USDC, $1K XOXNO & more - In-kind: $30K Tencent credits, $8K Certik audits, advisory perks Whole event: $100K total across tracks. Jump in, build on Supernova, and let's crush it 🛠️🌌 Register/submit: Event hub: #MultiversX #BattleOfNodes #BuildWars #Supernova #EGLD

Фото профиля 0xRonVbald0r
0xRonVbald0r9 месяцев назад

good work

Фото профиля Zen
Zen9 месяцев назад

This is really really impressive. Loved 1.6 surf…..

Фото профиля Renaud
Renaud9 месяцев назад

@C_A_DOT_IO Thanks! I did love it too! 😁

Фото профиля Jacob Martysius
Jacob Martysius9 месяцев назад

map nostalgia

Фото профиля Doug Dimmadome
Doug Dimmadome9 месяцев назад

is this fully-JS web-browser source surfing? what the fuck is going on?!

Фото профиля Mark w/ 🏈🏆
Mark w/ 🏈🏆9 месяцев назад

Ngl, was watching it on the feed not full screen and your mouse pointer had me thinking I had a spec on my phone. 2~ secs wiping till I realized it 😂 Oh cool demo btw, bookmarked for later. lol

Фото профиля Karan Jagtiani
Karan Jagtiani9 месяцев назад

Impressive work on the physics engine! The performance boosts with BVH and spatial hashing sound promising. Curious about the customization options for different game types

Фото профиля Ademola
Ademola9 месяцев назад

Nice 🔥, will vehicle physics be supported?

Фото профиля Coder
Coder9 месяцев назад

Impressive, very similar to surf ski

Фото профиля 『』
『』9 месяцев назад

OMG CSGO surf server 😆 nice one!

Похожие видео

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 просмотров • 9 месяцев назад

Special thanks to Google DeepMind for inviting me to try out Genie 3. I'm excited to share my thoughts on this early research prototype and also some of my live recordings below: I spent the whole day playing with the system and when it works, it is truly mind blowing🤯. It is the first neural game engine / world model I have tried that generalizes so well and has long term world consistency. Here’s a couple of examples from my live recording and some thoughts on what it means for the future of gaming, robotics, digital experiences and ASI. Where it shines: - Truly general-purpose and quick startup time. Works exceptionally well for gaming environments but also generalizes to other industrial and real-world scenarios. - It learns physics. Although there are systematic failures even for rigid body physics, it was clear to me that it can learn game engine and non-rigid physics without an underlying engine (and in limit learn from game engines via training data). - It works exceptionally well for stylized environments with characters walking around. This will have implications for concept artists, level designers and game devs. - It is way more fun than video models, indicating that there are high retention consumer experiences waiting to be built with this in the future - Photorealistic walk throughs and drone shots work exceptionally well - Global illumination and lighting works surprisingly well - Visual memory is quite powerful and the same objects approximately remain coherent under occlusion and longer time horizons Open Problems: - Physics is still hard and there are obvious failure cases when I tried the classical intuitive physics experiments from psychology (tower of blocks). - Social and multi-agent interactions are tricky to handle. 1vs1 combat games do not work - Long instruction following and simple combinatorial game logic fails (e.g. collect some points / keys etc, go to the door, unlock and so on) - Action space is limited - It is far from being a real game engines and has a long way to go but this is a clear glimpse into the future. The Future: - It is impressive enough for me to have strong conviction that this is going to disrupt the gaming industry. It is super early days and there are a lot of failures but the writing is on the wall. Lots of challenging scientific, engineering and scaling problems to be solved but it is going to happen in the next 5 years. - This is the final piece before we get full AGI and now I think we are well on our way to truly solve it once something like this is scaled up. In many ways it is more ASI than AGI but this is a matter of definitions. The fidelity and generalizability will reach human-level and quickly surpass humans - People are going to combine this with 3D AI and LLMs to build AAA games.

Tejas Kulkarni

88,083 просмотров • 1 год назад