You can bypass the "Out of bound" message by setting a Javascript breakpoint after
`let t = JSON.parse(d[e].config_str)`
and then run
`Object.values(t.camera.presets).map(o=>o.max_distance=50&&o)`
in the console.
It breaks down pretty quickly once you get outside the default bounds, as expected, though.
I wonder how much of the remaining work boils down to generating a new scene based on the camera's POV when the player hits one of the bounds, and keeping these generated scenes in a tree structure, joining scenes at boundaries.
Yes, and you wouldn't even need to do it in realtime as a user walks around.
Generate incrementally using a pathfinding system for a bot to move around and "create the world" as it goes, as if a Google street view car followed the philosophy of George Berkeley.
Or pair something like this with SLAM to track the motion and constrain its generation - feed it the localisation/particle/Kalman filter (or whatever map representation) as additional context, and it should be able to form consensus fairly quickly?
(Half-baked thoughts)
jfactorial|1 year ago
lukev|1 year ago
Generate incrementally using a pathfinding system for a bot to move around and "create the world" as it goes, as if a Google street view car followed the philosophy of George Berkeley.
tayistay|1 year ago
ulonglongman|1 year ago
dmarcos|1 year ago
blendaddict|1 year ago
creativenolo|1 year ago