Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

here's a nicer live-mapping method on Quest. Sampling depth texture and writing greatest y position per x,z world heightmap pixel. It's rough but semi-functional Bad performance is from the debug mesh rather than the world mapper itself. Runs fine with the mesh off.

10,374 görüntüleme • 1 yıl önce •via X (Twitter)

9 Yorum

Thomas Van Bouwel profil fotoğrafı
Thomas Van Bouwel1 yıl önce

Inaccuracy in the mesh is a huge problem right now, especially if you want to do things like player pathfinding safely without accidentally sending players down a staircase or through a wall - something like this would be a great solution for that. Great work!

sneeth profil fotoğrafı
sneeth1 yıl önce

love all this stuff you’re doing with the quest, looks like fun to tinker around with it

jt profil fotoğrafı
jt1 yıl önce

This particular project just becomes a hyperfixation every once in a while and it isn't fun at all. It's awful. It obliterates my sleep schedule every time I get into it.

mikolaj power profil fotoğrafı
mikolaj power1 yıl önce

looks awesome. how do you access the depth data? and what framework are you using if any?

jt profil fotoğrafı
jt1 yıl önce

@andrzejthefirst Meta provides depth frame access in their Quest SDKs

Maebbie profil fotoğrafı
Maebbie1 yıl önce

wow this is so fast, looks to be in a very usable state now

jt profil fotoğrafı
jt1 yıl önce

There is still a lot to do. Notably some sort of noise filtering i.e. only write to the heightmap if a height reading is consistent for some number of frames. This would probably solve issues with doorways filling in.

Gikis profil fotoğrafı
Gikis1 yıl önce

So now you're able to scan a large area? I tried disabling guardian in dev options a half year ago, but it would still only allow scanning a pretty small space.

jt profil fotoğrafı
jt1 yıl önce

This is my own Unity project, not the system space scanner

Benzer Videolar

Ferris State HC Tony Annese - Mesh (QB/Ball Carrier) & Motion Fundamentals QB Mesh Fundamentals - Regardless of play, the first thing the QB needs to do to make sure he has a good mesh is stab the ball back off his hip towards the ball carrier as far as he can. - His arms should be straightened with his eyes at the HOK. - The ball should move with the back through his track. - If the ball is pulled the decision must be made by the time the ball gets to the QB's front hip. Ball Carrier Mesh Fundamentals - The potential ball carrier is the one that is responsible for his track. He needs to make sure his is at the mesh point that the QB is creating. - He must maintain a pocket that is firm enough to secure the ball but loose enough that the QB can pull the ball if the read is a pull read. - Do not deviate from the track until you fully clear the mesh. - If you do not get the ball then track away from the HOK and make him chase you. Motion Fundamentals - All of our motions start up at FULL SPEED! It is incredibly important to make every motion at full speed so the QB has a consistent timing. - The QB is responsible for sending the motion back on every play except for the triple option. - This allows us to control each motion easier. - Every Jet motion should be timed as if the jet back was getting the ball regardless of play. - The motion back will change his depth based on play. - This allows us to use motion with a multitude of schemes. - The motion stops at different spots on different plays and each perimeter player must understand where he should stop for each play.

James Light

19,145 görüntüleme • 8 ay önce

Everything far away in a game engine can feel small, flat, and washed out. That is correct perspective, but it can make for some poor scenery sometimes. Two features I've added to my engine try to fight against that: Spatial Recession magnifies the distance. After a vertex is projected I push its screen position outward from center. Near geometry is untouched. It only moves x and y, never depth, so nothing sorts differently and nothing z-fights. The result is a long lens bolted onto the far half of a wide one: the tower and the ridgeline loom instead of receding, while I keep the wide field of view I actually play in (FOV is identical in both of these examples). Dimensional Falloff is four distance ramps on the surface itself. Lighting contrast flattens so distant hills stop having a hard lit side and a hard dark side, which is what haze does in real life. Color then desaturates toward its own brightness to fake more distance. Then that desaturated color is pushed, and that is the one doing most of the visible work here. Last is texture detail, with a custom MIP value based on distances. All of it keys off real radial distance from the camera rather than depth This is so it stays put when you turn your head. Performance cost is next to nothing. The recession is two lines in the vertex shader. The falloff is a few lerps at the end of the pixel shader, which was already computing that distance for the mip bias anyway. Quite happy with the results, what do you think? #gamedev

Analog Dream Dev

84,807 görüntüleme • 13 gün önce