Headspace

I recommend EVGA due to their competitive warranty. I have used them for the last two card purchases I've made.

Tucano_uy: I wouldn't expect you to have to buy a 500USD joystick to use the mod. Something else is going on. Since you're the second person who claimed POV hat issues I'm forced to assume that something is up. Stay tuned on this one.

I would learn how sockets work and start making test programs by downloading Lua and running it outside of DCS. I wouldn't rely on talker and listener exclusively--your needs might be different.

I don't think there is a safe zone for a gun pass on such a target--you wouldn't be engaging something like a Shilka with guns. It presents the Shilka with a clear shot at an unmoving (relative to its sight picture) aircraft, which is very bad. Even though you can kill a Shilka with your gun, why would you want to risk your entire aircraft? Ideally stuff like that should be avoided, or engaged with maverick or PGM from high altitude.

No installation needed--it is packaged with DCS.

I use Luasocket for TARS, in all iterations of the DCS series. So it definitely works.

No problem, the R828 is really bizarre in how it works, but it is what it is.

You have to hold down the tuner button until the light goes off.

To answer your questions 1) The Teamspeak 3 status display doesn't update unless you unhighlight it in TS3 and then re-highlight it. That's why it isn't updating for you. Nothing we can do about that unfortunately--it's a feature of Teamspeak. 2) I see what you mean about ADF now. Unfortunately TARS cannot induce the radio to "transmit" in the game like the menu commands do. That is why the ADF feature doesn't work. It would be nice if it could, and I am exploring it further. Currently transmission logic is seperate from the game's own transmission logic (the latter which governs menu radio commands).

Thank you for your support. SPU-9 was modeled as close as possible to what the manual says. The KA-50 guard channel is hardwired to a set frequency and doesn't change. How do you know it isn't changing? Also ADF has nothing to do with TARS.

Talker and listener IIRC were just socket implementation examples. I recommend learning about sockets from a technical standpoint in order to properly understand what is going on. That way, you can select a protocol for your mod to use. Most socket implementations (ex: http://www.linuxhowtos.org/C_C++/socket.htm) follow the same design, whether you are using winsock, or unix, or something else. Luasocket is a little simpler.

That's exactly what I did. To answer the other question, spectator frequency will be set up in a future release, I know it's in the CP but it doesn't work yet. It would have required a big delay in getting the current one out and tested.

You have access to Luasocket in current releases of DCS. You do not need to supply your own. Look in the directory structure for it.

paulrkii: Where/what are you developing the SOP for the deliveries off of? Is it publicly available material?

Because you get one free every 100 purchased.

The same code is used for setting all three buttons, so something else is going on.

How? It's really not hard to coexist with it. What were you doing?

If you use only one button to transmit, then UHF will be active by default. If you key another radio, that will then cause the default mic button in Teamspeak to transmit on that radio. It will not happen instantly--you will need to key it for a minimum of 10ms, 20 to be safe.

If your logs are indicating fractionally different radio frequencies, don't worry about that necessarily. Floating point math being what it is, if it's within the sensitivity range (in this case 0.025Mhz for the three ARCs in the A-10) you will be fine. So, if you are having issues, something else is causing it.

The tracks will contain radio frequency changes in the sim. When a track is being played, data fed to TARS is no different than in MP (except it won't be getting updates from your friends). It's a good diagnostic tool.

Were you using the buttons as switches or push-to-talk buttons?

Bizarre. Do you have a track of that handy? And were you getting the lockup or just the frequency glitching?

Plan on re-learning everything you learned in IL-2. I'm always impressed when people do the really tight formation flying in these games where you have no depth perception and sensory input overall. I really think it's one of the few things that it's more difficult to do than for real as a result of that.

Thanks guys. I've identified what could be causing the hangup issue (no guarantee until it's tested more extensively), fixed the issue with the joystick unplug = crash problem, and 7.1 surround sound should work as well. I'll keep updating until these issues are fixed. The updated TARS (now at version 1.0.1.15) is on the site.

The latter case could only be investigated with logs...so far I've received them from two people and that's it.