Perpective behavior incoherence

Teczer · January 4, 2023, 5:27pm

Hello,

I’m having an issue trying to build a gameobject with some kind of perspective.

From the front it looks like this (it’s a kind of room):

The background is at z=0, the walls are rotated around the y axis, the floor and ceiling around the x axis.
Theses 4 sprites are closer on the z axis (z=50).

If I move the view the walls start to overlap:

But if I start to rotate the viewport (ctrl+lclick) the perspective gets fine instantly:

The issue is that in-game I get the overlapping sprites, when using default camera with perspective or rendercam.

Have I done something wrong ?
Thanks in advance

Teczer · January 4, 2023, 5:30pm

You can try and reproduce with these assets:

room.zip (3.5 KB)

britzl · January 5, 2023, 6:59am

Have you tried recreating this with model components and the quad from builtins?

I also think perhaps @Dragosha has some experience with sprites and perspective cameras?

Dragosha · January 5, 2023, 8:17am

That’s because sprites don’t use z-buffer depth test in common render pipeline. They sort by their pivots. If one sprite’s pivot in the camera view is closer to the camera pivot than other sprite’s pivot then sprite one render above other one. When you rotate the camera you are changing this ordering.

github.com/defold/defold

Pivot for sprites (DEF-651)

opened 10:46AM - 23 May 19 UTC

britzl

feature request engine editor sprite

* Current workaround is to create an intermediary child game object and use that… as a pivot * Local vec3 translation * Offsets scaling and rotation * Dynamic property, get/set/animate * Should not affect vertex data generation as batched sprite vertex data is still highly dynamic * Design how the pivot should be edited in the editor needs to be done, things to consider: * Manipulator support * Visuals in scene view/outline * Selectable in the scene view * Selectable in the outline Take in to consideration doing #4350 as a sub-task as automatic sprite cropping will need to modify the pivot (invisible to the user).

Well, for correct sorting you need to use a mesh or model components as @britzl said. They using z-buffer by default. In render_script it looks like

render.enable_state(render.STATE_DEPTH_TEST) -- check z-buffer
render.set_depth_mask(true) -- write to z-buffer

or enable this feature to sprite predicate too. But notice that z-buffer depth test may broke render-order of self-transparent sprites.

Teczer · January 5, 2023, 2:03pm

Thanks for your answers, I’ve recreated a test project from this sample:

https://github.com/defold/template-basic-3d

It looks like it’s working for this gameobject alone, but if I continue this way I think I’ll have to rethink a lot of the stuff around.

Also, I’m playing with tints and lights, and it looks like depending on the camera position, if have a kind of light reflection effect on quads:

britzl · January 5, 2023, 2:17pm

If you open up the model material you will see that there is a lightsource. In the basic 3d project template it gets updated based on mouse position:

github.com/defold/template-basic-3d

main/main.script

master


      
          function on_input(self, action_id, action)
          	-- move directional light based on input
          	self.light.x = 2 * ((action.x - 480) / 480)
          	self.light.y = 2 * ((action.y - 320) / 320)
          	go.set("#cube", "light", self.light)
          	go.set("#quad", "light", self.light)
          	go.set("#sphere", "light", self.light)
          end

If you skip the light update based on mouse position and instead copy and modify the material and position the light far from the camera (0 0 1000 0) everything should be equally affected by the light I think.