TASClient 64bit windows error

TASClient 64bit windows error

Discuss your problems with the latest release of the engine here. Problems with games, maps or other utilities belong in their respective forums.

Moderator: Moderators

Post Reply
User avatar
AF
AI Developer
Posts: 20687
Joined: 14 Sep 2004, 11:32

TASClient 64bit windows error

Post by AF »

Image

The task bar is drawn on the desktop when its minimized. Only affects tasclient, all other programs work as expected.
User avatar
Agon
Posts: 527
Joined: 16 May 2007, 18:33

Post by Agon »

If you use vista, then everything is clear.
What can help. CMD->format C:\. Ups has vista a cmd?

This was a must! :evil: !
User avatar
AF
AI Developer
Posts: 20687
Joined: 14 Sep 2004, 11:32

Post by AF »

Theres nothing wrong with Vista. TASClient has been the only program to give this kind of error since I uninstalled windows 98 and put XP on.

I uninstalled Vista 32bit and installed 64bit this morning. It seems the nvidia driver devs are all prioritizing 64bit drivers. The only issue with my new 64bit OS is TASClients drawing glitches. And theyre not the same glitches that show up in 32bit Vista either.

These are all glitches that show up under all Operating systems, but different glitches become glaringly obvious under certain circumstances. This just appears to be one especially obvious under Vista x64.

Look at the linux screenshots of tasclient under wine, you can see the over drawing glitches only the window borders overdraw the controls not the other way round.
User avatar
Agon
Posts: 527
Joined: 16 May 2007, 18:33

Post by Agon »

Why do you not use your client?
Or SpringLobby?

Or maybe do you want to say there is something wrong with TASClient?
User avatar
AF
AI Developer
Posts: 20687
Joined: 14 Sep 2004, 11:32

Post by AF »

If I used my own client I'd be driven mad noticing things and constantly exiting opening the IDE changing things then opening it again.

Its also nice to be able to tll apart the dev build your testing and the normal build your using.

It also serves as a failsafe ensuring that if theres an AFLobby<-> TASClient incompatability I immediatly know about it.
Post Reply

Return to “Help & Bugs”