Vicinity, or why one distance was never ...

Vicinity, or why one distance was never enough

Aug 24, 2026

imageLast week Vicinity shipped with one number: how close you had to be before a model loaded. The same number for a pebble and for a cathedral, which is obviously wrong.

It now has a node graph. You write the rule once — load at fifteen times the object's size, anything heavier than 20 MB loads later, landmarks load from the horizon — and every object works out its own distance. The graph is compiled once into a flat program that runs inside a Burst job, so no nodes are walked while your game plays.

The smaller change is probably the more useful one day to day: drag a model from the Project window straight into your scene and it streams. No conversion step, no new habit for an artist to learn.

There is a manual now too: nekuzaky.com/docs/vicinity

Still v0.1, still free for noncommercial use. Feedback very welcome.

github.com/Nekuzaky/Vicinity

Ti piace questo post?

Offri un burger a Nekuzaky

Altro da Nekuzaky