Headspace

Mine has no interest in simulators. But wants Mass Effect 3 for a valentine's gift.

I think I've found the source of this problem. I'll know this weekend at some point if it can be replicated.

Almost nothing can be done without logs or repro instructions unfortunately. However, let's be clear. Is TS3 crashing by: 1) Locking up; it seems to not respond, and you have to force close it and then restart OR 2) Crashing with the "quit unexpectedly" message, and you get prompted to send the error report, blah blah blah. The distinction between 1 and 2 is a big one. My money, after spending about an hour buried in assembly code, is on #1. Am I right?

Logs are going to be critical then, and from the more people the better...especially the TS3 crash log in the My Documents folder. EDIT... And to illustrate the point, I've determined what was going on with Disablez by analyzing his crash dump--thanks Disablez. For now you're going to need to keep your devices plugged in while TS3 is running but I am including the fix in the next batch of fixes. I want to spend a bit of time gathering more data.

For you or for everyone? I hate releasing right after TS3 has also updated to a new version, but sometimes it is necessary.

Thanks for those, I will analyze them this weekend and see what I can come up with. I think I know what the issue is, but this will help.

Find your crash logs in my documents from TS3 and send them to me.

Turk for some reason it didnt come through, although you can attach it to a forum post as well (in an archived file).

If you are reading TARS status in Teamspeak 3 but DCS isn't connecting, then it's an export or firewall issue. You might also have other export mods installed that do not play nice with other mods.

Thanks Turk. I'd like anyone else who has a 7.1 surround sound device to see if the channels work with that as well.

Turk10mm: Could you send your logs to the bug report on the TARS website? I'll look at them.

You'd need to tie into DirectX, almost certainly.

Looks like you've identified a small bug. I've already fixed it. The download on the site will be updated tonight or tomorrow night. It seems to be limited to people who want to run 32 bit teamspeak on their 64 bit OS.

I think what may be going on here, at least partly, is directory security on the Teamspeak 3 and Eagle Dynamics folders in Windows 7. It can't be helped; TARS Control Panel has to be able to get to those folders. So either run the TARS Control Panel as admin, or give your user access to those directories. I prefer the former.

TZeer what's your architecture? 64 bit or 32 bit? Second, what version of Teamspeak 3 are you using? 64 or 32? I just verified that both versions of the correct DLL are packed into the installer, so that isn't the issue. Something else is going on. Occasionally I get reports from people who say that they're on the correct version of Teamspeak 3 but are saying there's an API version mismatch. It's really bizarre. Make sure the TARS dll inside your Teamspeak 3\plugins folder is the same one of the two in your C:\Program Files (x86)\TARS\deploy folder.

Yes but not implemented yet. Also, Tyger, make sure you get the very latest TARS. It works with 3.0.3 and only 3.0.3.

TARS 1.0.1b14 Released With Added Joystick Support Enjoy. I know that I sound like a broken record saying this, but please send me your logs if you encounter an issue with this release. It is the only way I will have any chance of solving your issue.

Cross-posting from the TARS website:

Tyger I can look into the KA-50 problem if you provide both TARS logs from each client. As for the multiple-PTT issue, it works both ways all of the time. It is set up that way so that people can use a single PTT button if they want.

In the land/infantry universe "break break" seems to be used in order to clear the channel so that important info can be transmitted. In the air universe, a single "break" would indicate an immediate, max performance turn. I suppose here it's meant to refer to a break to go to the next line in the briefing.

The VBS2 thing sort of validates this; a relative handful of users bought it privately, even after the "personal edition" came out. The market is used to a ~$50-60 USD price point on games.

If this is the case and people Fraps it then I will gladly link the material from the TARS website.

Yeah, it was definitely sorely missed from the first set of versions. I have it set up so you can make up to six different key combos across all of the devices you have plugged in. After the 10th I'll be able to run it through testing with a TM WH. I'll see if I can make it auto config to the WH throttle upon detection, if possible.

Now I'm working on the selectable channels for headphones feature people have been asking for. All of this will require some testing so I don't anticipate a public release until sometime after the week of January 9th.

The API version error has absolutely nothing to do with the 32/64 bit assembly. Your version of Teamspeak 3 is quite likely older and incompatible with the current TARS. Upgrade to the latest version and try then.