Mouse cursor vanishes after about 20 minutes of gameplay (Unity 4.3.1)

Hello again.

Unity 4.3.1 solved our problem with duplicate mouse pointers - and now we’ve got a new one: After about 20 minutes of gameplay the mouse pointer vanishes completely and there seems to be no way to get it back. Seems to be an issue with 4.3.1. Any idea?

Thanks a lot!
Tassilo

Just to make sure - you’re using custom cursor, right?
What happens if you don’t override the cursor and use the default (system) one. Does it work well or cursor vanishes too?

Yes, custom cursors (contextrelated). Wish I could tell you about the system cursor. Our coder, who’s crafting the builds for W8A, is unreachable now and for the upcoming weekend. We’ll try to build it without him and find out.

I’m running now a project with custom cursor for about 30 minutes and the cursor is still there. This is not yet released 4.3 with some extra bug fixes you don’t have yet though, not that I’m claiming something.
If I understand correctly, you change cursor depending on context? That is, it’s not the same all the time.

It actually seems to be worse - mouseovers are not responding to moving the invisible mousecursor over the screen. It seems I lost mouse input completely. Moving the mouse to the upper border makes the system cursor reappear, moving it back down it vanishes again. No control of our game possible. Restarting the game does not help either.
Only happening in the Windows 8 Store build, all other builds unaffected.

Are you targeting SDK 8.0 or SDK 8.1 ?

We’re targeting 8.1 (because of using SQLite)

It looks like a cursor has been destroyed.
When you set the defualt cursor, system cursor is hidden and Unity draws cursor itself (and coordinates are updated according mouse movement).
The destruction of cursor is not necessairly Unity bug, it can be a bug in a game itself, especially if you change the cursor in game depending on context.

I suggest to examine game code where you change cursor.
BTW, I don’t thing this is specific to Win 8.0 or 8.1.

It even happens in the start screen, way before any context related mouse cursor changes take place (though it is a custom cursor). The problem occurs since building with 4.3.1 and only on Windows 8 AppStore. We did not touch any cursor code for a very long time and all other versions run fine. The problem occurs mostly after a while of playing, but sometimes even directly at game startup.

Could you make a simple scene with custom cursor, where this issue could be reproduced? You could then submit a bug, this would help a lot. Thanks.