Hi!
In this example, after clicking on the sphere, hoverCursor becomes default. This is not correct behavior. The cursor must remain “wait”.
If you remove adv from the code, everything will work.
Apparently, there is something with the layers. How to solve this problem without resorting to crutches?
Don’t know. Haven’t used this so far but I’d say that you did set this parameter in your actionManager but didn’t ask to change this parameter ‘on pick’. So I’d say this behavior is what I would expect. As I said, I’m not an expert on this thing (far from it). Though if it was me, I would simply solve it like this:
Edit: Oops! Just did read your post again and you are saying that your cursor changes. Didn’t realize because it doesn’t do it for me. From your PG, the cursor remains on wait after pick (chrome on mac).
Just an update, I don’t believe that this is a regression or at least the behavior described goes as far back as 4.0, with respect to the provided PG. I have found the lines that are changing the cursor (lines 795-797 of advancedDynamicTexture.ts):
if (!this._cursorChanged && !scene.doNotHandleCursors) {
this._changeCursor("");
}
The only area where this._cursorChanged is true is after the changeCursor function has been executed. As far as fixing or providing a workaround, I’ll have to ask around to see if I’m missing something. @RaananW and @carolhmj, if you think I’m missing something or have any ideas, please let me know.
I can’t see a reason why this behavior was in, so I say go for the fix 
The only thing to be aware of is pointerBlocker behavior - i.e, if a Control is pointerBlocker, then it should block the cursor changing on hover for the ActionManager. This works as expected right now ActionManager hover conflict with adv texture | Babylon.js Playground (babylonjs.com) (you can test with the red square which is pointerBlocker), so the fix should keep this behavior.
Just an update, I’m currently testing a fix for this. I’ll update when I have a PR up.
Sorry about how long it’s taken to reply back to this but my previous fix wasn’t actually the correct fix. I’ve been digging more into this and I’ve noticed that the cursor is changing multiple times during an action so and if I put a cursor change to happen AFTER the default event occurs, it tends to stay without updating, even if the style says cursor="wait". I suspect that there may be some disconnect with when the style is updated and when the cursor is changed. My current thought is to try work around this. I’ll let you know what I find.
When the model material is PBR, the model is added with actionManager. When the mouse is clicked, the hoverCursor is pointer.
When the model material is GUI, the model is added with actionManager and hoverCursor is default when the mouse is clicked