Thomas Fabini

kdv wrote:

this code (as is) will work correctly only with 4.9.0pre1. and yes, it’s working.

Hi kdv,

thanks for confirming.
Hope I’ll be able to test it soon…

Alexander Kovelenov wrote:

Here is how we do it. You can use this snippet as a basis for your own puzzle or with “exec script”

Hi Alexander,

Thank you so much for the snippet!
After reading through it, as far as I understand, bounding trees is where the magic happens, and then performing closestPointToPoint to find the closest point on the edge of the collision mesh relative to the current position. That’s awesome, being able to query against the outer bounds of the mesh…

Are bounding trees completely supported already in 4.8.0?
I was afraid they would not be available in 4.8.0 (which we’re currently using as a stable production version) but after testing I was able to see the data on my collision mesh and even performing closestPointToPoint() on it. I guess I still have to figure out the correct parameters and the details, but if this works it would really mean a huge improvement for non-physics collisions.

I might try to just exec a short part of code with the collision mesh and current position as parameters and feeding the returned vector to the navigation loop.

Thanks for pointing this out and good luck with 4.9!

Hi Yuri,

Yuri Kovelenov wrote:

We decided to not ship the directional cone feature so that to not over-complicate the puzzle.

That makes sense, would be quite a bunch of settings…

Yuri Kovelenov wrote:

Yes, the latest optimizations will across the shader code, not just Principled BDSF.

That. is. awesome. Can’t wait to test it on the Headsets – shaders seem to have by far the biggest impact on performance on those. Far more than geometry or heavy coding in any case.

Thanks!

Hi Yuri,
thanks for the latest additions and improvements in 4.8!

Two things I’m curious about:
Does positional audio support only the omnidirectional spatial sound or the directional sound, too? (setDirectionalCone from the API with inner angle, outer angle and gain).

Do the latest shader optimizations affect only the Principled BDSF or the older shader nodes, too (Diffuse, Transparent etc.)?

Regarding positional audio, some of our (VR) projects specifically require directional audio-sources, not only omnidirectional ones, that’s why I’m asking. Now, I’m aware, what makes Verge3D powerful are not lots of very specific features, but the features which benefit most Verge3d users. Even in our projects omnidirectional sound is a constant requirement, while directional sound isn’t… If directional sound isn’t planned for now I will use the available API to implement it.

Also true… :)

Yeah, I haven’t actually tested bones – it’s about the meshed rope / cable / hose and physics I asked once about – I opted for a simplified approach, shape keys instead of physics.
It’s less fancy than physics but much more stable an controllable. (It’s still madness to set them up, but they work).

With bones… I read bendy bones aren’t supported, that would be an awful long IK chain so that the cable bends without seeing the segments or bones. But you are right – if it works, it would solve my problems regarding parenting in an instant! I guess I’ll try that.

See? Your answer was longer than two letters it already helped. :D

Mikhail Luzyanin wrote:

I’ve checked the mesh, it’s all ok with it. The problem not in depth write and zero faces but because of not sorted faces in trancperency mode.

Thank you very much for testing this, Mikhail.
I’ve tried this now, too, with a similar but clean mesh with no zero faces and the problems with depth sorting are just the same.

I’ll try alpha hashed, too – I tried to avoid it, mainly too prevent Quest 2 / 3 performance drops on heavier scenes.

Yuri Kovelenov wrote:

Those will be available in the first preview of Verge3D 4.8. Stay tuned!

Great news Yuri, thank you very much!