Thomas Fabini

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!

Mikhail Luzyanin wrote:

Works fine for me. You need just set for all cubes Pass Index 1 or more and for some cubes set the checkbox Depth Write, it’s unchecked on some of them.

Thanks for looking into this Mikhail,
you are right – with Depth Write I’m able to control which objects are rendered above or below other objects.

Thing is, I’ve got some mesh geometry which doesn’t work well without Depth Write, can’t uncheck it for this mesh. The cause might be geometry with a large number of zero faces, which I have been unable to repair. The object is highly complex, rigged, rebuilding it from scratch would take quite some time.

That’s why I was looking for a solution that *might* work without Depth Write.

Plan B is disabling Depth Test through API in situations where Icons need to overlay and setting Depth Test back on when they don’t – which works fairly well.

Hi Yuri,
copy and paste between projects is such a life-saver… thank you for this feature.

I have a question though, regarding the “Render Order” setting: I’ve got the feeling this setting is ignored when using 4.7.1 with a pre 4.x blender-version (3.6.x LTS, in this case).
Might have something to do with the newly introduced transparency hacks in 4.2?

It seems only values like zero and bigger than zero are taken into account. Transparency stacking with multiple different values (like i used with 4.6) doesn’t seem to work.