First off let me lay the ground work.
I have both programs (TS3 and MWO) set to Windows 7 Compatible and both run as Admin
Now if i have the game open and running and I start Teamspeak3 it MWO goes "Not Responding"
If I try and launch with TS3 already open i get a black window after hitting play at patcher and I have end program.
Not sure if there are already work arounds or an "easy fix" for this just wanted to fish for any answers.
Thanks in advance
A.V.


Ts3 Makes Mwo Go Non-Responsive
Started by Antillus Valerian, Feb 27 2013 07:26 PM
7 replies to this topic
#1
Posted 27 February 2013 - 07:26 PM
#2
Posted 27 February 2013 - 07:33 PM
I use both without an issue. I'm no expert on TS3, only just started using it, but I've heard people mention something about an overlay that causes problems when used with MWO, never used it myself. Sorry, thats all I can suggest.
EDIT: Welcome to the forums by the way. I'm sure someone who knows more will be along soon.
EDIT: Welcome to the forums by the way. I'm sure someone who knows more will be along soon.
Edited by Mounty, 27 February 2013 - 07:34 PM.
#3
Posted 27 February 2013 - 07:37 PM
Start Teamspeak 3, Click on Setting, Than Plugins Uncheck All plugin than Click "Reload All" at the bottem there. Close Plugin window connect team speak server.
Now Start MWO.
Do you still have the problem?
Now Start MWO.
Do you still have the problem?
#4
Posted 27 February 2013 - 07:45 PM
Try updating TS3 or disabling "TeamSpeak 3 Overlay plugin" in the plugins.
#5
Posted 27 February 2013 - 08:27 PM
Wolf74's solution has fixed 3 of my lancemates issues tonight - applications should not fight like that. Unbelievable - can't wait for the next list of broken items patch.
#6
Posted 28 February 2013 - 09:10 AM
I had this problem. I tried Wolfs suggestion but while connected to the Teamspeak server. Nothing happened. I disabled Overlay and MWO loaded properly. I have had Overlay issues before so this issue deserves more investigation but disabling Overlay seems to be the quick fix
#7
Posted 28 February 2013 - 11:16 AM
Fixed it, Thanks wolf. Just strange that I never had this issue until yesterday.
#8
Posted 02 March 2013 - 05:49 AM
Uninstall KB2670838 to fix
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users