Water issue on phaser 3.25.beta0 about enable3d

[yandeu]

I don't know if it is related to v3.25-beta. Does it work well in v3.24?

[georgzoeller]

Yea, tested on 3.24 and it's fine. 3.25 has a bunch of batching changes that would sound like potential culprits

image

[yandeu]

I see. I suggest we wait for the next beta version or the stable 3.25 release. Maybe it will be fixed.

[georgzoeller]

In case it isn't, here's some more information

It only kicks in at certain angles - the text / icons render just find but when the camera has a certain perspective on the water, it looks like all game object textures get overwritten

[georgzoeller]

I think this is a broader issue - enable3d isn't entirely playing nice with phaser, even before 3.25.
it somehow interferes with rendering shape fills - I cannot do a graphics.fillStyle().fillEllipse() for example while I have enable3d loaded, it just renders the stroke of objects, but fill on any scene running on the same phaser instance will be blank.

[georgzoeller]

[georgzoeller]

I've narrowed it down to this:
it's this.accessThirdDimension() that causes the corruption
as long as I have a blank Scene3D in the project and that scene calls
this.accessThirdDimension() in it's create function, any graphics.fillX will not work anymore (no error) in any scene across the phaser instance

Since phaser has a bunch of global state in graphics object a (setTexture being the best example), I assume something is getting corrupted there on a global level and it's happening in accessThirdDimension.

[yandeu]

Scene3D extends from Phaser.Scene version ~3.23.0.

Maybe this causes some issues? Can you downgrade to ~3.23.0 to test it?

[georgzoeller]

Just Tried 3.22 / 3.23 / 3.24 / 3.25b0 , all the same.

It looks like .accessThirdDimension() on a separate scene is wiping the fill. Interestingly, If I destroy and recreate the shapes after that call, their fill is rendered properly.

[yandeu]

Hi @georgzoeller

I guess with the latest enable3d update, all these issues should be gone.

I have completely changed how 3d elements get implemented in a Phaser 3 game.

Check the readme file to upgrade to v20.

[yandeu]

I close this issue since from version 20, enable3d does not mix the three.js and phaser.js WebGLRenderingContext anymore and therefore all these issues should be gone.