正在加载视频...

视频加载失败

返回首页

I've compiled some performance tips gleaned from working on my 1 million GPU AI steering agents project. I want to see Twitter compression destroy this video. 🚀 GPGPU: N-Body - O(n^2) - simulations are easily processed in parallel. GPUs are really good at parallel processing = 🫶. 🌐 Spatial...

TheMirzaBeig's profile picture

Mirza Beig

28,961 subscribers

13,252 次观看 • 2 年前 •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

We figured you needed to see LiquiGen today. The simulation, rendering, and meshing are all real-time.
0:58

We figured you needed to see LiquiGen today. The simulation, rendering, and meshing are all real-time.

JangaFX Software

109,829 次观看 • 3 年前

WATER SIMULATION IS WORKING!!! It's extremely non-optimized, and there are still some glitches, and of course the rendering is very temporary, but IT'S WORKING! #indiedev #gamedev #indiegames
1:34

WATER SIMULATION IS WORKING!!! It's extremely non-optimized, and there are still some glitches, and of course the rendering is very temporary, but IT'S WORKING! #indiedev #gamedev #indiegames

Nikita Lisitsa

13,281 次观看 • 4 个月前

Ok, I've decided to implement Particle Life simulation on GPU, using WebGPU, in browser. For now I've spawned 1'000'000 particles and implemented basic rendering & camera movement. I recon computing interaction forces will be the most painful part to implement...
0:20

Ok, I've decided to implement Particle Life simulation on GPU, using WebGPU, in browser. For now I've spawned 1'000'000 particles and implemented basic rendering & camera movement. I recon computing interaction forces will be the most painful part to implement...

Nikita Lisitsa

16,249 次观看 • 1 年前

I wanted to see how far I could realise lapping beach water in #UnrealEngine, Simmed in #Houdini, Using UE5-Main (5.6) Raster rendering with the new Raytraced Translucency and Lumen. #UE5 #GameDev #Cinematic #VFX #Simulation #RayTracing
0:57

I wanted to see how far I could realise lapping beach water in #UnrealEngine, Simmed in #Houdini, Using UE5-Main (5.6) Raster rendering with the new Raytraced Translucency and Lumen. #UE5 #GameDev #Cinematic #VFX #Simulation #RayTracing

Dylan Browne

30,503 次观看 • 1 年前

We're currently working on the endgame fight cinematic and need your help! We're looking for volunteers experienced in any of the following: lighting, rendering, set dressing, VFX arts, and/or destruction simulation Apply as a #3DArtist at:
0:25

We're currently working on the endgame fight cinematic and need your help! We're looking for volunteers experienced in any of the following: lighting, rendering, set dressing, VFX arts, and/or destruction simulation Apply as a #3DArtist at:

Skyblivion

14,343 次观看 • 7 个月前

I am at the 4th iteration on the pixel inspector and light path debugging tool. Eventually I moved the path collection to the GPU, so I don't have to toggle between CPU and GPU rendering, making the visualization fully interactive.
1:47

I am at the 4th iteration on the pixel inspector and light path debugging tool. Eventually I moved the path collection to the GPU, so I don't have to toggle between CPU and GPU rendering, making the visualization fully interactive.

Max Liani

83,377 次观看 • 2 年前

📢Spinners for Three.js . Copy, paste, done. GPU-based point rendering, lightweight and flexible. No hard to get, no mystery. Based on the work of Paidax and Mike Bespalov You can also edit the parameters to achieve even more variations. Link below!
0:34

📢Spinners for Three.js . Copy, paste, done. GPU-based point rendering, lightweight and flexible. No hard to get, no mystery. Based on the work of Paidax and Mike Bespalov You can also edit the parameters to achieve even more variations. Link below!

𝗕𝗮𝗻𝗱𝗶𝗻𝗼𝗽𝗹𝗮

54,406 次观看 • 2 个月前

I don't believe we live in a simulation like in the movie. I believe we are energy, but not a simulation. The video doesn't look real. But. Draw your own conclusions. My Spanish isn't very good, but this guy is saying something about the simulation failing with free energy, and that's why there are pyramids everywhere to generate free energy. Without cables and with a lot of free energy, the system can overload and the simulation ends in failure. I don't know exactly.
7:03

I don't believe we live in a simulation like in the movie. I believe we are energy, but not a simulation. The video doesn't look real. But. Draw your own conclusions. My Spanish isn't very good, but this guy is saying something about the simulation failing with free energy, and that's why there are pyramids everywhere to generate free energy. Without cables and with a lot of free energy, the system can overload and the simulation ends in failure. I don't know exactly.

Bronze Giant

456,269 次观看 • 9 个月前

The next frontier of AI is physical. 🤖 From simulation to synthetic data, developers are training robots to understand the real world with NVIDIA Cosmos, Isaac simulation frameworks and open-source physics engine, Newton. Watch the video to see how partners like Hon Hai Technology Group (Foxconn), Hexagon, Humanoid, Noble Machines, and Skild AI are building the future. 🎥
0:51

The next frontier of AI is physical. 🤖 From simulation to synthetic data, developers are training robots to understand the real world with NVIDIA Cosmos, Isaac simulation frameworks and open-source physics engine, Newton. Watch the video to see how partners like Hon Hai Technology Group (Foxconn), Hexagon, Humanoid, Noble Machines, and Skild AI are building the future. 🎥

NVIDIA Robotics

21,515 次观看 • 2 个月前

testing my osu rendering in roblox with a 9 minute long XNOR XNOR XNOR osu aspire entry! there's still visual bugs i need to work out, especially with sliders, but i'm happy with the performance 🙂
1:15

testing my osu rendering in roblox with a 9 minute long XNOR XNOR XNOR osu aspire entry! there's still visual bugs i need to work out, especially with sliders, but i'm happy with the performance 🙂

littensy

22,595 次观看 • 1 年前

🌊: Ever wondered what cutting-edge physics simulation looks like in the browser? Check out saharan / さはら's collection at - Realistic water droplets with WebAssembly SIMD - Interactive fluffy ball sim using GPGPU - Coupled cloth and fluid dynamics in real-time - A digital clock powered by a custom physics engine Saharan built everything in Haxe using techniques like MLS-MPM and parallel computation. The physical accuracy and performance are exceptional. All MIT-licensed on GitHub. Perfect if you're exploring GPGPU techniques, browser physics, or just want to see what's possible with WebGL/WebGPU. #WebGL #WebGPU #Physics #GameDev #ComputationalPhysics
1:55

🌊: Ever wondered what cutting-edge physics simulation looks like in the browser? Check out saharan / さはら's collection at - Realistic water droplets with WebAssembly SIMD - Interactive fluffy ball sim using GPGPU - Coupled cloth and fluid dynamics in real-time - A digital clock powered by a custom physics engine Saharan built everything in Haxe using techniques like MLS-MPM and parallel computation. The physical accuracy and performance are exceptional. All MIT-licensed on GitHub. Perfect if you're exploring GPGPU techniques, browser physics, or just want to see what's possible with WebGL/WebGPU. #WebGL #WebGPU #Physics #GameDev #ComputationalPhysics

WebGL / WebGPU

14,778 次观看 • 5 个月前

For my 3d simulation I needed to implement new rendering. To replace "sphere par particle" with marching cubes. I never implemented that kind of stuff, so I decided to first try a simplified 2d version, the marching squares. It worked, very fast rendering now.
0:23

For my 3d simulation I needed to implement new rendering. To replace "sphere par particle" with marching cubes. I never implemented that kind of stuff, so I decided to first try a simplified 2d version, the marching squares. It worked, very fast rendering now.

Zolden

90,679 次观看 • 1 年前

FASTER for #Amiga OCS/ECS: I never imagined saying this in a million years, but I seem to be struggling to get the performance I need out of the blitter, and I don't even have all the stuff on screen yet! Anybody know a faster way of rendering bobs than the cookie cutter method?
1:58

FASTER for #Amiga OCS/ECS: I never imagined saying this in a million years, but I seem to be struggling to get the performance I need out of the blitter, and I don't even have all the stuff on screen yet! Anybody know a faster way of rendering bobs than the cookie cutter method?

Jonathan Thomas @atariste.bsky.social

13,879 次观看 • 1 年前

#OctaneX was featured in today’s Apple keynote! Apple users can augment the massive increase in rendering power on the M4 with access to near unlimited high performance decentralized GPU compute power on The Render Network using Octane X.
0:32

#OctaneX was featured in today’s Apple keynote! Apple users can augment the massive increase in rendering power on the M4 with access to near unlimited high performance decentralized GPU compute power on The Render Network using Octane X.

The Render Network

536,930 次观看 • 2 年前

Amiga OpenGL remote rendering. OpenGL commands get serialised on Amiga, sent over a TCP socket to a remote rendering server. That is Amiga 68k GLQuake (running in winuae) rendering on my PC RTX3080 GPU :)
0:28

Amiga OpenGL remote rendering. OpenGL commands get serialised on Amiga, sent over a TCP socket to a remote rendering server. That is Amiga 68k GLQuake (running in winuae) rendering on my PC RTX3080 GPU :)

Claude Schwarz

40,876 次观看 • 5 个月前

NEW RENDERING: Bena Road 🚄 Here's a visual rendering of a high-speed train passing over Bena Road on a viaduct in the Tehachapi Mountains south of Bakersfield. *This is an initial design subject to revision.
0:55

NEW RENDERING: Bena Road 🚄 Here's a visual rendering of a high-speed train passing over Bena Road on a viaduct in the Tehachapi Mountains south of Bakersfield. *This is an initial design subject to revision.

CA High-Speed Rail 🚄💨

19,026 次观看 • 1 年前

Casually rendering ~a hundred million triangles, in the browser. All thanks to Sunag's cool Nanite-style renderer for Three.js. I've added GLB-to-meshlet and PBR rendering to it, very exciting to see where this is going!
0:30

Casually rendering ~a hundred million triangles, in the browser. All thanks to Sunag's cool Nanite-style renderer for Three.js. I've added GLB-to-meshlet and PBR rendering to it, very exciting to see where this is going!

herbst

203,736 次观看 • 19 天前

AI for robotics has some monumental challenges, like high dimensionality and reasoning with the physical world. Ashok Elluswamy, AI lead at Tesla, thinks the hardest problem is Evaluation. - Loss isn't a perfect indicator of Policy Neural Network's quality. - Testing in the real world for all the long-tail failure cases is not possible. To solve the evaluation challenge, Tesla has developed a World Simulator Model. It is trained on state and action pairs, so for a given current camera feed and current action, the model generates the next frame in the cameras. Once the world simulation is good enough, it can be hooked up to the policy network for a closed-loop simulation. In this setup, the model generates the next video frames, and based on those, the policy network comes up with the next action, which feeds back into the world simulation; this continuous loop creates a coherent simulation. The world simulation neural network is not just applicable to self-driving but also to humanoids, because Tesla trains it on common data. The examples show Optimus navigating or manipulating inside the world simulation, with all the pixels being generated by the world simulation model. The robotic agents can be tested in an accurately reproduced edge case and in other potential variations of the same edge case.
1:29

AI for robotics has some monumental challenges, like high dimensionality and reasoning with the physical world. Ashok Elluswamy, AI lead at Tesla, thinks the hardest problem is Evaluation. - Loss isn't a perfect indicator of Policy Neural Network's quality. - Testing in the real world for all the long-tail failure cases is not possible. To solve the evaluation challenge, Tesla has developed a World Simulator Model. It is trained on state and action pairs, so for a given current camera feed and current action, the model generates the next frame in the cameras. Once the world simulation is good enough, it can be hooked up to the policy network for a closed-loop simulation. In this setup, the model generates the next video frames, and based on those, the policy network comes up with the next action, which feeds back into the world simulation; this continuous loop creates a coherent simulation. The world simulation neural network is not just applicable to self-driving but also to humanoids, because Tesla trains it on common data. The examples show Optimus navigating or manipulating inside the world simulation, with all the pixels being generated by the world simulation model. The robotic agents can be tested in an accurately reproduced edge case and in other potential variations of the same edge case.

The Humanoid Hub

15,907 次观看 • 4 个月前

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.
0:23

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,497 次观看 • 5 个月前