PDA

View Full Version : Can anyone at TS please tell me when the bugs will be fixed?

Alsone
11-09-2004, 11:20
Hi,

Can anyone please tell me when the bugs with the windows in TS are going to be fixed as they've been driving me (and everyone else who uses Battlefield 1942) crazy ever since this latest release was released.

Basically the problems I'm talking about are as follows:

1. When alt tabbing between Windows (Battlefield 1942 game, Team Speak, Blackbagops Remote Manager) or when bringing up other windows (usually Internet Explorer Windows to view web pages when chatting in Team Speak) often a "This Window does not have Scroll Bars" error message appear in TS.

When this happens the message box can be closed but not TS which then hogs between 97-99% of the CPU power, effectively crashing the system as no other application will work due to lack of CPU cycles. :eek:

The only way out of this is to start the Task Manager go into "processes" and then click to end the process.

TS then has to be restarted and logged into from scratch.

2. There is also a "Press to Talk" problem whereby there is a key pinging transmitted over the microphone when using press to talk. It's usually when exiting to TS you notice the "Scroll Bar" error message. However the above can occur sometimes without the key ping although the key pinging is usually the indication that it has occurred.

These problems are not unique to me:

I don't know anyone using BF 1942 who is not experiencing them.

Please tell me when are they going to be fixed?

Al.
Brain
11-09-2004, 11:24
I've played BF1942 myself and never experienced #1
About #2: It's not a bug, it's a feature. TS2 doesn't "swallow" keypresses, so if you bind a PTT key that generates a character (like e.g. the "A" key) it will pass on the keypress to the active application. If your active application is the windoze desktop and the mapped key is a character that is not the first character of anything that's on the desktop you get a "ping".
Alsone
11-09-2004, 11:29
Hi Brain,

If you've not experienced #1 you're lucky!

I think its related mostly to opening Internet Explorer (IE6) Windows when in TS but I'm not totally sure.

As for #2, I suffer no key pinging in normal use, only when the "scroll bar" error message appears. That is usually my cue to restart TS.

Al.
Brain
11-09-2004, 12:06
Are you even running the most current client, 2.0.32.60? I remember there were some problems with visual components in older versions.
Alsone
15-09-2004, 17:39
Hi Brain,

Yes I'm running the most recent version - the one you posted.

I attach a screenshot of the error message.

I forgot to mention another way it occurs, is if having alt-tabbed to another window you forget to re-alt tab and instead switch windows with a mouse click on a minimised window on the task bar instead, then sometimes this causes this error message.

It doesn't actually CPU hog until you close the error message box, although you may start to get key pings with other windows open, but once you've closed the error message box, the main TS window fails to respond (it can't be closed) and CPU usuage goes up to between 97-99% effectively freezing out all other applications, including the game.

Al.
Peter
15-09-2004, 18:45
about the "key pinging", that would be windows sounds that come up when you hit keys that don't have any effect currently. Use keys like shift, ctrl, alt etc. as talk keys to prevent such behavior.
About the error message - there have been a few workarounds posted on this forum (I recall resizing the teamspeak window to a very small size, but you'd better use the search function to find out).
The next version of teamspeak will be TS3, and I would be supprised if a bug like that would be present in a complete rewrite + coding language change.
Javana
15-09-2004, 22:23
got that error box to sometime's but no cpu problems then
i got the newest 1 of teamspeak
Alsone
17-09-2004, 02:42
about the "key pinging", that would be windows sounds that come up when you hit keys that don't have any effect currently. Use keys like shift, ctrl, alt etc. as talk keys to prevent such behavior.
About the error message - there have been a few workarounds posted on this forum (I recall resizing the teamspeak window to a very small size, but you'd better use the search function to find out).
The next version of teamspeak will be TS3, and I would be supprised if a bug like that would be present in a complete rewrite + coding language change.

Hey,

That will be great PWK.

I don't want to sound like I'm moaning, after all TS is free, but I'm sure you can appreciate how frustrating it gets when TS crashes and you have to leave a game to restart.

Al.

PS in the meantime I'll search and try to find out those work arounds you suggested.

Thanks. :)