tamte

heightfields encode just height
so having something you can't represent as heightmap is also not possible to represent as a heightfield

you can always convert heightfields to volumes and go from there, but at that point they'll stop being heightfields

notice that you are adding your point to geometry referenced by handle 0
so you can also set it as 0 will contain that point, well, maybe not exactly what is happening, but you can think of it that way, obviously it will not work with anything else than 0 at this point

you've put “primN” in there instead of primN

so it will make your N string attribute and set value of “primN” everywhere
but ig you put primN, which is vector variable, it would create vector attribute N with value contained in primN variable per point

notice that you are adding your point to geometry referenced by handle 0
so you can also set it as 0 will contain that point, well, maybe not exactly what is happening, but you can think of it that way, obviously it will not work with anything else than 0 at this point

you've put “primN” in there instead of primN

so it will make your N string attribute and set value of “primN” everywhere
but ig you put primN, which is vector variable, it would create vector attribute N with value contained in primN variable per point