Microsoft Surface Pro 9 – Windows 11 WebGL – super slow?

The WebGL cube rotates fine. Attached is the screenshot of the output requested.

Please note this is not an issue with Verge3D its a problem with WebGL in general for the Surface. Doesnt really matter if it’s threejs, unity, V3D or anything else…its just bad.

To qualify what I mean by bad:

The demos/projects all work. They have decent frame rates BUT it’s as if it skip frames and is jerky regardless of the project size or complexity. Slow to respond to input and extremely slow to respond to changes in orientation (but this is a device thing) but when building responsive WebGL interfaces….this causes problems.

The simple cube seems to run fine without skips…but there is no interactivity so…cant say for sure if its a problem. Once you start moving a camera around….it seems fine until you realize the camera is not keeping up with your request and /or interactions are delayed.

To Qualify this is not a V3D thing…its on all Webgl implementations we have tested….further…its a lag thing in fractions of seconds. What makes this bad, in our current project in V3D, is when you have animation puzzles with a “when done” process that depends on screen orientation to determine what gets rendered. Because there is a lag and because there is a major delay in screen orientation change things can get bad fast. The “window” reports a change in orientation…but the surface doesnt change for several seconds…in some cases…we had it not change up to 20 seconds. Again this is on multiple Surface Pros and varioius configurations….all with new installs of OS and all updates applied. We have contacted Microsoft and the screen rotation delay is how the Surface works….its intended apparently.

We switched from using Chrome and started using Bing and things improved….slightly but significant enough that we don’t recommend Chrome on the Surface. Since they are all bit on Webkit you would think the performance would be the same.

WebGL performance on MS Surfaces has been reported over the past few years but we have not had issues with them until now.

I wish that solved the problem…but even dropping it down to .2 the problems still persist, not to mention the models just look ugly.

Just an FYI…. the feature available puzzle: mobile or touch screen are not recognized on the MS Surface…it does detect Windows and Edge but given the users base for Surface is smaller than than desktop/laptop. I am stuck with just letting MS Surface users suffer whatever issues the MS Surface has.

I think its up to MS to fix this one.