When adding a check for pPointer == NULL in miPointerWarpCursor, the behavior simply moves to somewhere else that MIPOINTER might return null. I was able to eliminate the behavior entirely by adding null checks everywhere in mipointer.c that pPointer is set from MIPOINTER. Once I learn how to create a proper patch for X, I'll attach it.
When adding a check for pPointer == NULL in miPointerWarpCu rsor, the behavior simply moves to somewhere else that MIPOINTER might return null. I was able to eliminate the behavior entirely by adding null checks everywhere in mipointer.c that pPointer is set from MIPOINTER. Once I learn how to create a proper patch for X, I'll attach it.