react-dom.production.min.js:216 TypeError: Cannot read properties of undefined (reading 'IsAvailable')
at m (performanceViewerComponent.tsx:154:13)
at performanceViewerComponent.tsx:165:9
at Bl (react-dom.production.min.js:262:359)
at t.unstable_runWithPriority (scheduler.production.min.js:18:343)
at Vo (react-dom.production.min.js:122:325)
at Pl (react-dom.production.min.js:261:308)
at ml (react-dom.production.min.js:243:50)
at react-dom.production.min.js:123:115
at t.unstable_runWithPriority (scheduler.production.min.js:18:343)
at Vo (react-dom.production.min.js:122:325)
ii @ react-dom.production.min.js:216
react-dom.production.min.js:123 Uncaught TypeError: Cannot read properties of undefined (reading 'IsAvailable')
at m (performanceViewerComponent.tsx:154:13)
at performanceViewerComponent.tsx:165:9
at Bl (react-dom.production.min.js:262:359)
at t.unstable_runWithPriority (scheduler.production.min.js:18:343)
at Vo (react-dom.production.min.js:122:325)
at Pl (react-dom.production.min.js:261:308)
at ml (react-dom.production.min.js:243:50)
at react-dom.production.min.js:123:115
at t.unstable_runWithPriority (scheduler.production.min.js:18:343)
at Vo (react-dom.production.min.js:122:325)
Any not backward compatible Inspector change has been implemented today?
Could you share the versions you are using for Babylon and Inspector ??? I have the feeling it is using a new version of core with an older inspector cause IsAvailable is a static on the PressureObserver class so it should always be available except here I am seeing ComputePressureObserverWrapper which is the old name of the observer used in previous inspector versions.
That has always worked for me, until yesterday in the morning (Central European Time).
Anyway, how can I know the versions you’re asking for? Note that I can’t even show the Inspector, so I can’t access to any version info tab in it or something.
Sadly this is a private project, but I thought any other of our projects using BJS would be showing the same problem, as it is, so please take a look at this other one.
Of course, script files have been minified there!
Note that console shows the same aforementioned error…
Indeed, it seems to be a very easy error to reproduce, isn’t it? I mean, is only loading the BJS from server and trying to use the Inspector functionality from code.
Anyway, It’s very strange to me that anybody else hasn’t warned about this issue, cause It seems like a lot of people is using this engine nowadays.
However, if you remove the initialTab: 2 from the config it works.
You can crush the inspector with the same error by clicking statistics icon (the one in the middle)
Looks like we were posting about the same time
I just wanted to check if I will have the same error as I haven’t used the inspector myself before.
Hope that will help the Babylon team to figure it out