Date: 2015-11-01, Windows 10 x64
in exclusive full-screen mode, D3 produces a very mixed behaviour when dealing with its mouse
pointer. In some resolutions it uses a software mouse pointer (not overridable by any program). In some other
resolutions, it uses a native mouse pointer (overridable by Cursor Node). However, the native mouse pointer is
always scaled to a fixed size, and changing the cn cursor size has no effect on it.
Once D3 starts using a software mouse pointer, the pointer will remain a software pointer until the game shuts
down. Switching the game resolution or video mode does not change the pointer back to an overridable native
the game should be started, and then kept in windowed or windowed full-screen mode at all times.
In these modes, all cn cursor types and sizes should be usable. In case of the game using a software mouse
pointer for theses modes, the best thing to do is to restart the game, which should reset the game pointer
to an overridable native mouse pointer. Alternatively, the
cn synthetic cursors can be used with the D3 software mouse pointer.
It is possible to discern D3 using a software mouse pointer by observing the pointer lagging the cn synthetic
cursor by a noticeable amount. In contrast, the synthetic cursor would normally lag a native mouse pointer by
a small amount. The cn synthetic cursor is compatible with programs running in windowed or windowed
full-screen mode only.
On these platforms, cursors larger than 64 pixels in dimension may be rendered without hardware
acceleration. Consequently, the rendering performance of large cursors may be poor. Therefore,
it is recommended that 64 pixels or smaller cursors be used.
Rendering performance of large cursors is significantly improved from Windows 8, which opens up greater
choices for the user.
On Windows Vista, it is only possible to use Cursor Node after disabling User Account Control (UAC). This
is due to Vista's security system being different to later Windows.
If Cursor Node is to be used purely for normal applications on the Windows desktop, best results can be
obtained by selecting
a cursor size that is same or smaller than the standard size permitted by Windows. The standard
Windows cursor size is typically 32 x 32 pixels and is determined by the SM_CXCURSOR and SM_CYCURSOR system
metrics. On systems classified by Windows as high DPI, the standard cursor size is 64 x 64.
Currently, Cursor Node is incompatible with any of the "Modern UI" aka "Metro" aka "Universal Windows Apps"
applications. These applications run at a lower integrity/privilege level than Cursor Node and therefore are
unable to take advantage of the capability offered by Cursor Node. Typical Universal Apps include the Windows
Microsoft Edge, Windows 10 Start Menu, etc. For these applications, the cursor cannot exceed the
standard size or flickering may result.
Virtual machines do not have the performance to accurately reproduce the normal running characteristics
of Cursor Node in a real machine. On Windows 7 or later based VM's, a double cursor may be shown for
larger cursors. This is caused by limitations of VM's. To properly evaluate Cursor Node, the use of a real
machine is recommended.