Loading video...

Video Failed to Load

Go Home

Working on structural connectivity system. Arrows show direction of load bearing connections, color shows load ratio (red means high degree of stress). This system will allow buildings to collapse under their own weight and be destroyed in more interesting ways #gamedev #indiedev

79,439 views • 1 year ago •via X (Twitter)

11 Comments

August's profile picture
August1 year ago

This is super cool. You should sell this to Sony so they can patent it, use it on exactly one game, and then never use it again and enforce their patent to ensure no one else does either

BigguyDev's profile picture
BigguyDev1 year ago

I'm waiting patiently to take their call

🪄 PSX Bunlith 🏳️‍⚧️ BLM ACAB 🇵🇸's profile picture
🪄 PSX Bunlith 🏳️‍⚧️ BLM ACAB 🇵🇸1 year ago

🤯🤯🤯

ΣTΞCH's profile picture
ΣTΞCH1 year ago

omg real time finite element analysis

BigguyDev's profile picture
BigguyDev1 year ago

Yeah the algorithm for load calculation is really simple. So it can run on a lot of pieces

freezydev's profile picture
freezydev1 year ago

wow thats really interesting. it looks like you simplify the loads as a random generated truss?

BigguyDev's profile picture
BigguyDev1 year ago

I was going to do truss analysis, but after 2 days of watching physics lectures I thought of a simpler way. Basically the structure computes it load paths from the ground (whenever it is changed). This won't be super accurate always, but should be good enough 🤷

Rob Keimig's profile picture
Rob Keimig1 year ago

Is the geometry pre-fractured or is it happening dynamically at runtime?

BigguyDev's profile picture
BigguyDev1 year ago

Prefractured. Dynamic runtime fracture is too cpu intensive unfortunately

McRib of Exile's profile picture
McRib of Exile1 year ago

red faction thanks you for your dedication

BigguyDev's profile picture
BigguyDev1 year ago

Haha yes 👌

Related Videos

In May 2023, a live streaming world record was set with 32 million concurrent viewers watching the finale of the IPL cricket game. How was this system built? Ashutosh Agrawal was the architect behind this system, and he walks us through how live streaming at scale works, how the system was built and tested, and other interesting learnings. Watch or listen: • YouTube: • Spotify: • Apple: --- Brought to you by our wonderful sponsors: • WorkOS — The modern identity platform for B2B SaaS • CodeRabbit — Cut code review time and bugs in half (use the code PRAGMATIC to get one month free) • Augment Code — AI coding assistant that pro engineering teams love --- Three of my biggest takeaways: 1. The architecture behind live streaming systems is surprisingly logical. In the episode, Ashutosh explains how the live streaming system works, starting from the physical cameras on-site, through the production control room (PCR), streams being sliced-and-diced, and the HLS protocol (HTTP Live Streaming) used. 2. There are a LOT of tradeoffs you can play with when live streaming! The tradeoffs between server load, latency, server resources vs client caching are hard decisions to make. Want to reduce the server load? Serve longer chunks to clients, resulting in fewer requests per minute, per client… at the expense of clients potentially lagging more behind. This is just one of many possible decisions to make. 3. “Game day” is such a neat load testing concept. The team at Jio would simulate “game day” load months before the event. They did tell teams when the load test will start: but did not share anything else! Preparing for a “Game day” test is a lot of work, but it can pay off to find parts of the system that shutter under extreme load. See more takeaways and a summary here: Thanks Ashutosh for all these behind-the-scene details!

Gergely Orosz

50,597 views • 1 year ago