It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
When I run Caesar 3 i do not have a mouse cursor at all.
I also get no cursor when running its sister game Pharaoh Gold.

I can move the mouse around and the menu items will highlight and clicking works just no visible cursor.

I've looked around on the internet and have tried various solutions but nothing has worked.
Nvidia drivers, windows and all other drivers/software is up to date.
Completely disabled Aero, set mouse scheme to None, disabled all mouse visuals, set theme to Windows Classic.
Tried various combinations of compatibility modes and settings.
It seems no matter what I do I can't get a cursor on this one machine.

I've installed Caesar 3 on two other win7 64 bit machines and the games worked no problem.

Windows 7 Professional 64-bit
Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz (4 CPUs), ~3.3GHz
Memory: 16384MB RAM
DirectX 11
NVIDIA GeForce GTX 660 Ti (x2 - Not running SLI)


UPDATE: I think this might be a 16bit display issue and not specific to any game.
After I posted this question I found out that this happens with any game in full screen if it uses a 16bit display mode. I have GOG's Heretic Kingdoms and the cursor shows up fine. Heretic has a Force 16bit option and when I set that the cursor disappears. So as an experiment I opened the nvidia control panel and set my color depth to 16bit and wouldn't you know it the cursor disappeared. So it looks like my mouse doesn't like being in 16bit mode. Now the question is what is causing it? The nvidia drivers, display drivers, directx, win 7 aero, logitect g700 mouse driver and/or gaming software. The investigation continues...
Post edited April 17, 2014 by Polomease
No posts in this topic were marked as the solution yet. If you can help, add your reply
I had the same problem, but found that running the CaesarIV.exe executable under Windows XP (Service Pack 3) compatibility mode did the trick for me!

I've attached a screenshot of the window with compatibility mode enabled, hope this helps.
Attachments:
Post edited June 11, 2016 by czarevilsam
avatar
czarevilsam: I had the same problem, but found that running the CaesarIV.exe executable under Windows XP (Service Pack 3) compatibility mode did the trick for me!

I've attached a screenshot of the window with compatibility mode enabled, hope this helps.
Thanks! I've spent ages looking for this and it's worked a treat.