One thing that has always bothered me about reported bugs on this forum (at least from what I've seen); Stardock staff is often quick to respond specifically to suggest uploading/pasting a debug.err so they can identify possible problems.  But once somebody does, nobody from Stardock says or does anything in response.

If there are no problems in the debug.err, it would be nice to see somebody from Stardock admit this, along with seeing how many others have reported this same exact mouse cursor problem over the past 3 years, and own up to fixing this huge bug once and for all.  And if you've been trying to fix it, at least fill us in to tell us your progress.  Because right now, aside from asking people to post a debug.err, it doesn't look like you're doing anything about it.

I apologize if I have a demanding tone, but it's such a massive UI problem.  I've reported this bug myself back in 2010 and posted my debug.err with no response, only to see it handled in the exact same manner 3 years later.  So many have reported this bug (along with the infamous DX error bug/crash) and after all this time its still unfixed and nothing has changed.  Even if it's something that can't be fixed given problems with the engine, or isn't "worth fixing" in Stardock's eyes for some apparent reason, please be honest and forthcoming about this.

The current version of 1.4 still does not fix this problem, and still no comment from Stardock.  Has anyone found a fix yet?

It is difficult for me to swallow the fact that I will be required to Photoshop image files of a cursor in a game I paid 40 dollars for.

Bad Stardock.  Bad.