Headspace

It's like one of those planets of the solar system pictures.

Amusing considering that there are 'communities' out there who consider TG to be not hardcore enough. Just goes to show that when it comes to mil-sim stuff, there really isn't a "too hardcore," there will always be people who fancy themselves even more hardcore.

Note to TARS users: Teamspeak has recently released version RC1. This will not work with the current version of TARS. I'll be updating you guys shortly on when the port to the new sound system is completed. In the meantime you will need to continue using beta 36 with TARS.

It's going pretty well. The new sound engine is just about done; I need to hook it into the same places that the old one was hooked into now. Then we'll do some internal testing and turn it loose. Teamspeak is taking its sweet time getting the new one released, so I am less concerned than I was. I had to move out to the midwest recently, so there wasn't much time to work on it. I'm just now getting back into full production mode.

I think what may be happening is you may not be running the control panel as admin and you have Teamspeak 3 installed to a folder that needs admin control. There's a file called tars.ini that sits in the Teamspeak 3 folder, it gets edited with the current keybinds by the control panel. Make sure that you either 1) Run the panel as admin or 2) Give yourself write access to the Teamspeak 3 installation folder.

That's the first time I've heard of that happening, it seems to work fine for everyone else. Are you using the correct mic switch keys (default ctrl-2, ctrl-3) to talk on the other radios? UHF being off should not affect the other radios.

Anywhere in TS3. i.e. it would be a way to do exactly what you are suggesting; selectively turn off the muting feature by tuning a radio to the agreed upon "public" channel. No. Nothing in my post remotely suggested that you should do that. What I was suggesting is that you might have taken the 60 seconds or so to send the logs to the bug report on the TARS site so that if there really was a problem, I could have figured it out, and if there wasn't, someone could have at least told you what was going on. Also, it may have been possible he was running one of the new TS3 builds.

What will probably happen is I will add an option to talk with spectators in an agreed-upon channel. However your first paragraph raises a good point. Given the level of complexity that this mod has, it is inevitable that this scenario should occur. But for every single bug report or logfile submission to the TARS site (which is linked in my post, which is where people go to download TARS--so I know you guys know it exists) I see roughly ten or so instances of 1) People asking for TARS support in their own virtual squad forums, as if a closed-source piece of middleware can be reliably supported by people who do not know how it works "under the hood". 2) People going to the forum and starting another thread to ask for TARS support. The above two are unlikely to help solve real issues with the software particularly since it does not involve logfile analysis. A great many times, it's a case of a person downloading the wrong version of TARS. The new Teamspeak 3 RCs are out, which don't work with the current TARS and I'm sure people are ignoring, or forgetting to read, the compatibility list and trying it there. These are all very easily solved, easily vetted issues that could be solved much more effectively by reading the instructions that go with TARS. My intention is not to come down on anyone but rather point out again that you have resources to follow in solving these issues.

The standard barometric pressure (at least in civilian aviation) is 29.92 at sea level. The altimeter is set to 29.92 by default for that reason most likely. Very carefully I'd imagine. Ah come on, beaten by hassata :(

I just assume everyone has a trackIR already given that it's reasonably cheap. Good point.

I doubt you'd want that card for this specifically unless you play other games and want to keep the same card for years. I am on a GTX 275 and it's more than enough for this. I could buy a 5xx card but the price to framerate for DCS and ArmA (the two games I find myself playing the most of these days) doesn't wash. DCS is a relic of a bygone age: The CPU-heavy game. Your CPU (and to a lesser extent, any bus-specific stuff relating to that) is going to be the bottleneck with this one in most of the cases I've observed since I started playing it. While you might see some performance gains with a better GPU, if you are undergunned in the CPU arena it won't matter nearly as much. But the ultimate boost for DCS, if you have a midrange system and can play it reasonably well already, would be the TM Warthog.

I would guess that's a keying issue--TARS for whatever reason thinks you're talking into a different radio. Even if the TS3 lamp glows that doesn't necessarily mean TARS will allow transmission. The best way to deal with this issue is to check the logs that the TARS TS3 plugin leaves on your computer in C:\Users\YourName\Application Data\Local\TARS.

New videos will be forthcoming now that I've got more time on my hands.

That was my point from before. Not everyone stays clueless. People will learn if they aren't driven away by Sgt. Milsim McHardcore before having a chance to learn. We have a few people playing A-10 with us on Friday who, prior to getting the game, had never played a flight sim before. And they are really good at it now.

Please read what I wrote. The gist of my post was an admonishment of people who attack newer players, not any sort of endorsement of any given style of game. I am clueless as to how you got that quoted bit from what I wrote. And if you think that I somehow dislike DCS you are obviously unfamiliar with the sheer amount of effort I have put into modding the game.

It's not just a bit unfair...it's seriously unfair. That's the numero uno thing that gets me about the flight sim community and why in many ways it has itself to thank for the lack of mainstream interest in flight sims. The average person can get into this but not if they're being discouraged every step of the way for not being hardcore enough. People spend mad money on things like the Kinect and other heavily marketed consumer schwag which is fine, but you put that money into a trackIR and a decent stick and you could be playing A-10 just fine. The barrier for entry isn't as high as people think. Just plan on investing the amount of time you would spend finishing a normal game to learn this one and you will do fine.

hog_driver: As with everything else, please post logs to the bug report form on the site. Also note any other addons that may be running that could be conflicting....as I understand it your TARS isn't responding in DCS but the control panel says it's installed, right? I have posted the TARS Roadmap which details the upcoming features of TARS. Because the project has gotten much larger and is in wider use than anyone could have hoped, you now have the opportunity to deliver much needed donations to the development effort if you're so inclined.

IRL it is very easy to determine what the active runway is, by either listening to ATIS, or asking the tower or GC directly. I would think that in the military environment it is similarly easy. When you have a situation where there are bugs preventing interaction with the ATC script or it gets "stuck" (which frequently happens) it's difficult to find that information out. I haven't yet tested if it sets the active runway to the direction the wind is coming from or not. I have often times been in the situation of not knowing what the game wants the active runway to be, and making the decision on my own. When people want to play "hardcore" and pretend that they're doing it the way one would for real, that whole thing falls apart when you factor in the game elements mentioned above.

Are the avionics ever started on ground power first? That's what I've been doing lately so that the INS can begin aligning almost immediately. Voltage drops during engine start (supposedly a bug according to the forum) which prevents everything from staying on while that happens...it's the best solution I've been able to come up with to save time during the startup sequence.

Yeah the elevator trim tab is practically in the same place.

In your Config\Export.lua file there is a ream of comments that will get you started with the available commands. Most of them are from LockOn but will work with A-10.

Well, distiler, you and others have brought up these points (others have in the past). I made a poll for us to hash it out in the FC2 area.

I am working on TARS roadmap stuff--to see what direction the TARS project is going to take after the conversion to the new Teamspeak 3 and custom sound system. Individuals have expressed interest in having a radio system for FC2, perhaps using different hotkeys for specific frequencies (since FC2 has no radio panel). This poll is set up to gauge interest.

TARS doesn't support FC2 because there are no radio panels. I would be open to supporting some sort of thing where FC2 players appear on some common channel, though.