Kaiza

Flew a training mission last night with A-10s/Hokums/Hueys and the odd su27 using TARS with a tower and ground controller. Had an absolute blast. Keep up the great work Headspace, TARS is very much appreciated.

Did you chop the throttles back quickly? I think it is more likely that it was a compressor stall. If you pull the throttles back quickly at high airspeeds the compressor will stall and your engines will flame out. Be nice and gentle. I dont know if this happens in RL, I thought the fuel control would be able to handle things like that, however perhaps not?

Or this:

Yes it does. Just a reminder for people (we had a few squadies with installation probs, including me) -Make sure you uninstall your existing version prior to installing the new one -Make sure you exit teamspeak prior to installation -Ensure you are running both teamspeak and TARS as admin

So as I understand it there is no CA support as of yet?

Legend! Thanks mate.

Just a bit of maths. Best bet is to work out a bingo before you go. To see if you can make it home, once you are in the cruise just get your time to destination from the data block at the bottom right of the HUD. Work out what fraction of an hour that is and time it by your fuel flow. That will roughly be your enroute gas. If you are really low on fuel you can use your AoA to work out best range speed (angle of attack).

That doesn't sound right. Did you check the temperature? I've played some missions with crazy hot temps which the a-10 really struggles in.

Roger that! I heard otherwise, must have been an old wifes tale. Thanks!

That installation looks fine. TARS only displays the A-10 icon now, since we have moved to DCS World. From what I have seen the DCS World version displayed seems to be the one that the client installed using the full installer. If you use DCS:World autoupdate, it doesnt seem to change this number, but that is fine, that is how it is for everyone else also and does not affect TARS. I have the unknown version message also, but my TARS is OK. One thing you have to make sure is that if you have a 32bit operating system, is that you use 32bit TS. TARS uses your operating system to decide which version of TARS to install, so your OS has to match your TS. Other than that I have no idea, it looks like it is all installed correctly.

I've seen a few people ask for this but i personally dont understand how would it be useful? It would definately be cool to have the distinctive cypher 'beep' for immersion, but apart from that I don't really see the point?

lol How to single ski on your pave penny!

Me too! Would be cool to have the extended freq band of the ARC-210 with TARS, but other than that I can't see much entertainment value. I assume that when the ARC-210 was fitted the ability to control comms from the UFC was also added as well. That would also be handy.

When you say "windowed only mode" do you mean we have to run DCS:World in windowed mode or that this program is run in windowed mode? Many thanks, the application looks fantastic.

RIP JimMack. Great words Wags.

Have seen it once, middle of last year, but have not seen it since DCS world has been about. No idea what caused it, but all clients could see it.

No worries, welcome to the forum.

I am a little confused by your post but I think you are saying using the joystick (which normally controls bank with aileron in the air) turns the aircraft when taking off. If this is what you are saying then I think this is your issue: When you use aileron with some airspeed you can actually turn the aircraft when on the ground as you are changing the friction on the landing gear. When you put the stick right the aircraft try's to bank to the right. This puts pressure on the right main landing gear, increasing the friction on the right and decreasing the pressure on the left. This will turn your aircaft towards the side of most friction, but you are not using NWS to do it. The reason this doesn't work when you taxi is you do not have enough airspeed to create the effect.

Not strictly a-10c related, but how about a radio stack GUI that is integrated with FC3 and combined arms for TARS. That would be ultimate.

I think your proposal isn't really the right solution to your problem. We are trying to simulate a real battlefield in DCS world, and putting IFF interrogators on KA50s is widly unrealistic and spoils the game. 95% of the challenge of this game, just like a real battlefield, is posturing and using tactics to gain information and develop battlespace situational awareness. Employing weapons is just the final step. Giving someone an IFF interrogator is solving half the "problem" for them when the "problem" is part of the game. Just like trying to ID ground targets. It's like a machine gunner saying "hey its not fair that I can't see as far as that sniper. I can't tell if the targets are enemy or not. Everyone should have a sniper scope" If your issue is that on some missions there are same arcraft types on both blue and red sides, and it is therefore sometimes unrealisticly difficult to identify whether aircraft are enemy, then I can see your problem. However I think the answer is in mission design rather than putting unrealistic capability on aircraft.

You mean you testers don't do an "inverted flight fuel starvation, double engine failure, flight essential bus power only, emergency APU and engine restart, inflight EGI alignment" test prior to each build being released? Sheesh. :noexpression:

Its not a limitation of the software really. ED are quite capable of implementing it, there is just no point. Basically IFF has two components. An interrogator and a transponder. Most military aircraft (including the KA50 and A-10) have a transponder only. i.e. The real aircraft only have a transponder. Think of it like this: The interrogator is the "asker". It asks the question: "Are you friendly?" The transponder answers either "Yes" or doesn't respond at all. A transponder can answer the question, but it can't ask it. So IFF (despite its confusing name) can only determine whether something is friendly if you have an interrogator, and it cannot determine if something is enemy (this is an important concept). So if your aircraft has an interrogator you can "ask" other aircraft whether they are friendly. If you only have a transponder you cannot, you can only "answer" questions. As you can see, there is no point in ED modelling the transponder to "answer the question" if their currently exists not human controlled aircraft to ever "ask it". Make sense?

IFF interogators are fancy pieces of specialist hardware normally combined with a RADAR system. If the aircraft doesnt have a RADAR it wont normally have an IFF interrogator. You will generally only find the system on aircraft designed for airborne early warning or beyond visual range air to air engagements. The A-10 doesnt have one either. It seems to be a pretty common misconception on these forums. You aren't missing anything by not having a Mode 4 transponder modeled (at least until we get an aircraft (or ship etc) with an IFF interrogator).

Can you provide a track file?

Is it the same mission? It may be triggered as part of the design?