After rebooting the mac, the error in Chrome was still there
I then tried firefox and that was OK.
I then retried Chrome and then that was OK!
So the error seems to have cleared itself now. Strange.
As a matter of interest, before the webgl errors in the image above, what are those draco wasm errors?
I spoke too soon. The chrome editor webgl context lost error returned. The launched app however is fine.
It is odd that this error manifested suddenly today. I haven’t knowingly changed anything. The launched app is ok but the editor has the error even in a blank new project with no edits.
Is there a possibility that some changes have been made to the editor/engine in the past week or so, that would cause this issue to manifest on my mac/gpu combo?
Last year we has a lot discussion here and here about Macs and issues with with certain gpus ( all my 3 macs fall into this category ).
If its completely white, try going to the project settings and under the editor section, disable ‘grab depth pass’ or something named similar to that and see if that helps. It has to be done per project.
Great thanks for the info. That makes sense. The last time I spent much time moving the editor camera view in the editor viewport was in January. I’ve been opening the project a lot since then but only for editing scripts, not editing the 3d scene. The error in chrome is triggered it seems when I move the editor camera view. Not immediately triggered but soon and consistently. I don’t see the error at all if I don’t touch the editor view and only edit scripts.