random touchups

Author: stevenctl

content/art/kopitiam/index.md

@@ -1,10 +1,15 @@
 ---
-title: Kopitiam
+title: Restaurant
 type: art
 showTableOfContents: false
 layout: "simple"
 ---
 
+Inspired by [B K Corner](https://maps.app.goo.gl/kdEVvqGHJaNEt9EFA) in Kuching.
+Didn't have time to texture this one very well, or build the surrounding
+scenery. Maybe it will fit somewhere in a game. It would be cool to have the
+buliding be a little hub where different shops open back up as you progress.
+
 {{< gallery >}}
 
   <img src="kopitiam_ext.png" class="rounded-2xl grid-w100" />

content/tech/terrain/index.md

@@ -116,3 +116,12 @@ for splatmap generation as well. Using these primitive shapes is pretty
 unwieldy , so in the future I'd like to be able to use the `Path3D` node to
 create paths and roads on the splatmap, as well as a free form drawing brush.
 Maybe noise texture overlays as well with masking.
+
+
+## Optimization
+
+Currently, this recalculates the terrain using every input shape, every time.
+There is a simple optimization that would cache the result of every shape but
+the actively selected one and then just re-apply that one shape. I haven't done
+measurements to see whether this is worth it. If this editor was being shipped
+in game, rather than being just an editor tool, it needs some tuning.

content/tech/triplanar/index.md

@@ -3,41 +3,36 @@ title: Triplanar with Deep Parallax in Godot
 type: tech
 ---
 
-I don't think this is going to be that useful in most games. Triplanar mapping
-is already expensive, and multiplying that by the samples for paralax occlusion
-mapping is probably a bad idea.
+Triplanar mapping is already expensive, and multiplying that by the samples for
+paralax occlusion mapping is probably a bad idea. It was fun to implement this
+anyway, even if I don't use it in a game.
 
 In my current WFC prototypes, I'm re-using models and rotating them. At some
 point I'll need to handle also transforming the UVs based on the rotation of
-the tiles' models, but for now triplanar can help me with look development.
+the tiles' models, but for now triplanar mapping is a quick way to get an idea
+of how things might look.
 
-I want to use heightmaps to add details without extra geometry. While modern
-game engines and hardware can handle an insane number of triangles, my workflow
-for creating models that tile perfectly cannot.
+I want to use heightmaps to add details without extra geometry. The concern is
+mostly on my workflow, not on performance. I'm simply too lazy to model that into
+my modules in a tileable way.
 
 The effect is turned up a bit to make it extra apparent int he sample. The floor
-shouldn't be offset so strongly if you want to have a character walk on it.
+shouldn't be offset so strongly if you want to have a character walk on it without
+them appearing to levitate.
 
 ## Heightmap with Deep Parallax
 
 {{<video "pom.webm">}}
 
-There is a ton of detail in the floor and walls. Some bricks/stones occlude
-others. It's really awesome.
-
 ## Normal Map Only
 
 {{<video "norm.webm">}}
 
-If performance does become and issue, using the normal map textures seems to be
-good enough. This is using the simplest "swizzle" approach from Ben Golus's
+Using Ben Golus's basic "swizzle" from his
 [Normal Mapping for a Triplanar
 Shader](https://bgolus.medium.com/normal-mapping-for-a-triplanar-shader-10bf39dca05a)
 tutorial, and I think the results are just fine.
 
-Without this fix, you get very wrong normals. It's subtle in this sample scene
-but areas in negative directions start looking dark in a confusing way.
-
 ## The Shader
 
 Here's the code for those who are interested. It's mostly me gluing code from