HN Simulatornew | past | comments | lists | submit | fromlogin

This type of story is always so cool to read. In this type of community there's often a bit of wistful dreaming back to these days and the type of challenges they presented.

I'm young enough that I wasn't there, but I've been programming since I was a kid and working with graphics for the last 15 years.

This type of excitement is the feeling I got from learning C and C++ to begin with. Trying to really understand how things were working under the hood.

I still get that sense when working on low level graphics and performance in my current job. In fact, when the texture memory corruption was introduced the article felt eerily similar to the events which inspired me to write my own recent article about texture memory layouts ( https://agentlien.github.io/texture )


It's an indie open world game originally released for Stadia and in its original form simply loaded the whole world into memory at boot.

We had to implement a streaming system and figure out a good way of chunking the world. This was a challenge because everything was on water and you could see nearby islands quite far away. An intern called Tommi did a great job identifying a good strategy and writing the system.

We also had to reduce the density and model complexity of a lot of environmental details such as rocks, vegetation, and stuff like pots and clotheslines. This was done largely by sorting things by memory size and frequency of use and identifying outliers.

One of the biggest issues was actually really silly: the journal fetched Portrait images and names of characters by referencing the actual NPC and having them embedded there. Meaning the journal, which was always loaded, would pull every NPC involved in a quest into memory including their behaviors, textures, and models.

On my end I also found a lot of silly details wasting hundreds of megabytes. Special render passes using huge textures and render targets, poor structuring of the render pipeline caused memory increases, several key shaders referenced huge textures which weren't necessary, ...

My blog posts about the project[0] mainly focus on rendering performance because that's where I spent more time and it contains more interesting content for discussion. But reducing memory was an ongoing concern with countless little improvements over the 1.5 year porting process

[0] https://agentlien.github.io


I expected to disagree with this post but actually found it really worthwhile.

For my own blog [0] I usually start writing because I feel I just learned and did something cool which gets me excited to share it. I also write only about topics I'm very familiar with (graphics and performance). Very safe. And still I learn a lot by forcing myself to really examine what I write about and always leave with much better insight into something I thought I knew inside and out. And still I'm always very nervous that people will dismiss it or find huge faults in it. I've found a few issues myself after the fact, but commenters have been nice.

Maybe I should risk pushing myself into unfamiliar territory? On one side, I absolutely loathe blogs written in an expert voice by someone who is clearly a novice - and I don't want to be that person. On the other hand, people who know me often encourage me to get more technical and detailed in my posts because they recognize that my blog is very simplified (meant to be approachable) compared to what I actually do day to day. My upcoming post will definitely lean into the more low level and technical. Hopefully that will be appreciated, but I find myself really nervous about it.

[0] https://agentlien.github.io


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: