b37 Cursor Issues

Moderator: Moderator

Post Reply
Message
Author
Kaitol
Posts: 1
Joined: Wed Jan 04, 2012 7:19 pm

b37 Cursor Issues

#1 Post by Kaitol »

While playing in fullscreen, mouse cursor is invisible, unless I disable the custom game cursor in options, then it occasionally shows up as a large black box. Also, it always asks me if I want to revert my screen resolution whenever I run the game.

I'm playing on Vista 32-bit with an Nvidia 6100 card.

andrewdoull
Low Yeek
Posts: 5
Joined: Wed Dec 21, 2011 9:05 pm

Re: b37 Cursor Issues

#2 Post by andrewdoull »

Something similar is affecting me as well on a Vista 64 bit system.

Whenever I play ToME4 I'm getting some pretty painful technical issues with screen resolution.

Using the default resolution, I get some weird 'fixed window' mode which isn't full screen, and has the bottom of the display obscured by the Windows task bar.

As soon as I attempt to change the resolution, I end up with either a display with a weird aspect ratio (horizontally squashed), full screen without the pointer, or the point without anything visible in the ToME 4 window.

shaf
Wayist
Posts: 24
Joined: Mon Jun 06, 2011 1:23 pm

Re: b37 Cursor Issues

#3 Post by shaf »

The same thing happens with Windows 7 64 Bit version, I've seen it happening since around b33.

Oreillius
Posts: 1
Joined: Mon Feb 13, 2012 9:04 pm

Re: b37 Cursor Issues

#4 Post by Oreillius »

I'm having these exact same problems! I'm glad I'm not the only one. But I use 64-bit Windows Vista as well, and it's pretty irritating.

When I played this on Windows 7, I had no problem at all, but now that I'm playing it on my desktop with Vista it's just kind or grating on my nerves.

Hopefully we can get this fixed as soon as possible!

Greendogo
Posts: 1
Joined: Tue Sep 04, 2012 12:09 am

still present in b42

#5 Post by Greendogo »

This bug is still present in b42.
I'm on Vista 32bit with a Nvidia 8600m running b42. It happens only in fullscreen on any resolution. Disabling the custom in-game cursor does not fix it, like it did partially for the OP.

What can I do to help the dev team fix this problem? I'm going to subscribe to this thread, so whenever a dev needs me to reproduce this problem or give them any kind of information to fix this in the code, I'll be here.

Post Reply