EquiRectangularCubeTexture Bug?

Bugs
1

image
image1086×53 4.75 KB

the EquiRectangularCubeTexture when loading the texture is referencing a property that does not exist?

Shouldnt it be texture.textureFormat?

2

Can you share a repro ??? I can not find it in the code

3

its not dropping an error in the PG for some reason but here is the offending line of code:

texture.format does not exist so I’m not sure why this is not giving more problems?

All I know is in our production code its freaking out about this and keeps giving us problems as we try to use the class.

Here is the error we are getting.

image
image1366×99 6.4 KB

image
image1481×543 36.5 KB

4

texture is an internalTexture in this context so it is fine, textureFormat does not exists on it:

image

I think it has been fixed ultra recently so might not be on npm so far.

I ll queue a new package.

1 Like
5

Hmm you are right, because its this._texture. Interesting.

I can for sure console log out (eqTexture as any)._texture.format; So I wonder why its yelling at me at all?

Is this something to do with the projects webpack?

Also I did ensure that the texture was loading, it just cant be turned into the cube texture.

6

Also to add to the information, it works when I roll the all the dependencies back to 6.21.1

7

Can you share a repro please ? it looks like a regression from recent changes and I d like to fix it

8

I don’t know how to reproduce it, its only on the webpack project that we are running.

When we do it in the playground everything seems fine so its got to be something with our webpack I’m assuming?

9

can you try with 6.21.3

10

Yes sir I can! Give me a few mins.

11

6.21.3 does not drop the error but the behavior of the sky sphere texture is super borked.

The 6.21.1 looks like this:

image
image1920×971 166 KB

And this is what 6.21.3 does:

12

It looks impossible to fix without a repro unfortunately :frowning:

The version is identical to the one in the playground and webpack would not do that.

13

Weird, let me ensure that the error was not dropping with the 6.21.3 again then because that makes no sense that they would behave differently.

Hmm yeah its not creating the error. I’m stumped.

14

This might be a cache issue I am fixing here: Texture cache fix by sebavan · Pull Request #14360 · BabylonJS/Babylon.js · GitHub

Lets try back once this is merged

1 Like