STP Dragon

I don't use easy comms! But maybe some of our guests.

No no. The guys used it correctly, we checked it step by step. The problem was: I (in A-10) switched OFF AM and UHF. Only the FM was ON. A other guy in the Ka-50 switched OFF FM and talked by using AM. The other Ka-50 guys on AM can't hear him but I did. But nevermind! If you guys don't have problems with TARS, the problem surely was by the guy. Maybe because of easy comms.

@ Eddie & Fire: Hm.. I don't know what was going wrong for our flight. Maybe some of our guests which had this problems still had activated "Easy communications"? What's your experiance with this setting and TARS?

The missions are technically compatible. I'm not sure if you are able to just load it and play it but you can open it in the editor, save it and play it. BUT!!! There are a loooooot of changes for the A.I., the holdingtimes, the triggers etc. I'm sure that 90% of the missions will not work as they did before. All the creators have to test the missions and rework them if something is going wrong. E.g. an A.I. helo have a complete new behaviour now and needs readjustments. Convoy's will act a other way if they get attacked. There are new triggers and maybe you can do something a better way than before...

You need a installed and activated V1.0 (no patches). Then install the update to V2.0 The setup will check if V1.0 is installed and install the V2.0 in a separate directory. In the end you will have a V1.0 (untouched) and V2.0 installed. You have to activate V2.0 with the new key you got after you bought it. The two applications are able to run parallel on one machine.

@ Eddie: Do you guys fly A-10 together with Ka-50?

We tested it some days ago with a Ka-50 flight, a A-10 flight and one A-10 AFAC. The Ka-50's where on AM, the A-10's where on UHF and the AFAC-A-10 was on FM. It was lots of fun but it worked not 100%. Sometimes some guys can't hear other guys they should hear them and guy's who should not hear them, heared them. It was a bit confusing and we want to wait for the next version of TARS.

Add a really big triggerzone over client Ka-50 spawn point and the whole target area so the Ka-50 can not fly outside. Then add a second, small triggerzone on the end of the runway the Client A-10s will start from. Add the A.I. Helo and check the hook "Uncontrolled". Add the triggeraction (button beside waypoint button) "Start". Add the Client Ka-50 and the Client A-10c. Open the Triggerlist and add: Trigger: ONCE Condition: Unit inside zone - Client A-10c - Zone behind Runway Unit outside zone - Client Ka-50 - Zone at Ka-50 spawnpoint Action: AI Task - "Start" Result: Once the A-10 are taken off and no Ka-50 is in the area, the A.I. Helo will start. It doesn't matter who is first on the server.

Hi Fire, First: I released some tigger logics in our forum: http://spare-time-pilots.de/viewtopic.php?f=48&t=739 Take a look. Maybe there is something interesting for you. Second: I used this function you described in one of my missions. I activated RED A.I. Fighters, once BLUE Client Fighters are active and no RED Client Fighters. I added a huge trigger zone and worked with "Unit inside zone" to know when a Client is active. Maybe your "Unit alive" version is the problem? Third: Radio-Items are not working in MP. Fourth: Sadly Blindspot's Coallition-mod is not working with BS2/WH anymore. But a other STP-guy is working on the mod.

Every day I can to learn something. Thanks for the information paulrkiii

You don't need modman for this. Just unzip it to a separate folder. Then open the DCS Options > Controls. Empty all entries for your stick, throttle and pedals Load the profiles (.lua files) by clicking the [Load Configuration] button in the up right corner. After that you can delete the unziped files. Edit: But yes, there is a update for modman: http://www.lockonfiles.com/index.php/files/category/373-modman/

Hi paulrkiii, In Spangdahlem Airbase (open house) I asked the pilots where to plug in the ground power. They didn't know because they never used it. They always uses the APU to power the systems. And by the way: I asked if they use the ENG OPER switch to MOTOR to turn the engine before they fire it up. They sad NO, only the "old guys" from Nevada are doing this because of the hot surrounding air. In Spangdahlem the air is cold enough to start the engines directly by pulling the throttle from OFF to IDLE. What's your experience? :pilotfly:

Thank you, I'll try to. :)

Yes, problem Nr.2 http://forums.eagle.ru/showthread.php?t=82078 Workarround: If your JTAC is moving, add some more waypoints and add the FAC-Engage Group task them. Do not add all FAC-Engage Group task to one waypoint.

Hi BeachAV8R, Is it your mission? Can't remember that I add a HMMWV in front of a A-10. And you let the A-10 explode if the client is missing a switch? -despiteful-

Little surprise for the next version. New mission: Red Cross Massacre

V 2.2 released Change Log: - Changed Ground Crew and Airport defense units

Buy a second license for a second computer and host a 24/7 puplic server.

I'm using this also. It's the best freeware you can get.

It's in the GUI Manual. You can find it in "Doc" in the installation directory.

It's the original

Das ist unser Kaufi! :D

THX elchacal. Guy's I'm sorry.... it's the fault of my girlfriend! :music_whistling: She stressed me out and I did a misstake in my missions. :doh: The JTACs in Operation Bigfoot and Thunderstruck get killed before they get active! Why? In the last minute before I released the missionpack, I changed the way the JTACs will get active. I removed the holdingtime and set the A.I. to OFF at missionstart. I did't know that the "invisible" and "immortal" option will get deactivated also with A.I. OFF and the JTACs get killed. I will fix this in the next version. I'm already working on v6.4 Also I want to optimize the triggers in all the missions. ... and I have a surprise for you guys... :smartass:

Version 2.1 released

Version 6.3 released Change log: Toooooo many things to specify... ca. 30h editor work since the last version.