nemises

Make sure when you specify the customised setup lua that you EXCLUDE the .LUA extension.

there is no benefit to using multiple cores on XP...only Vista and win7

Hi Spinter, I tried version 1.01, however it will not allow me to select "Black Shark" .... How can I get 1.02 to try ?

su33?

Looks great spinter, I'll gladly try this out. Are there any instructions as to how to set this up for Blackshark ? ..... ....does the program automatically change teamspeak channels by reading the in game frequency ?

jeebers... anf man, the time delay on when the rounds hit, and when you hear the gun actually firing....that shiz is freaky.. ..I thought it were a cluster bomb at first...

Sure thing ... it is available to all in the form of a post by Wags last year Here is the thread from Wags with "the list" in it ... http://forums.eagle.ru/showthread.php?t=27694

Have you tried uninstalling DCS (no need to deactivate / reactivate, as you are not changing computers!). Then do a full re-install, and then install the patch , should be fine?

all it takes is slewing over the chopper next to you though and ranging them to give off an "under attack" warning... Nevil Noob doesn't necessarily realise this.. Cut them some slack, and use it as a chance to help a guy out. ...of course if he keeps on doing it over and over without aknowledging your messages...well, thats another story

Accuracy with Rockets is extremely hard (well...for me it is)... Guns and ATGM are fine to do from a stable hover, as you know, but on the move, it can be very difficult to get the piper over the target consistantly.. My advise to you.... -Start from 10+ KM's out -Line up and TRIM for a path that takes you through the target zone (though you must never overfly it...you will break left or right after deploying rockets) - Once trimed on course and speed, turn on Flight Director mode ... this will temprarily disable the heading and roll a/p channels, which will make minor adjustments to pointing the nose much more intuitive - Rockets are "area effect" weapons, which means they are not necesarily meant to be pinpoint accurate ... set your launch mode to "Medium" or "long" , and start launching at mac "C" range...hopefully the dispersion and frag damage will do the job!

...dude...you are in luck ;) ... All 3 of those are on the list!! ...along with F16c, Mi24, AH64a, A10a/c

I agree, I'd love to know more about the correct procedures for pattern flying and approach .. I understand (?) that the ATC portion of the game / messges to tower / traffic and landing pattern etc might be beeing looked at in later iterations of the DCS series though...

(sorry havent read rest of thread) ... If it is the Confrontation 8 X 8 map, then , since the patch, you seem to take damage while rolling, presuambly due to an increase in teh damage radius of the arty strikes? ... Unsubstantiated, however, myself and 3 wingmen all took damage whilst rolling to the runway on that map prior to takeoff.

...nice!

sign me up for helping with the Marine Dropship and LV421 Map :)

an easier solution (I think) than having concentric zones is to setup a single zone, have it set a Flag, then use "time since flag" actions, to shoot a flare every x amount of seconds.. I've used this in a test mission, and it works pretty well, though I agree, I would be nice to get a bit more life outta them flares... I usually launch to 300 feet, and set a trigger action to shoot one every 15 seconds for about 5 or 6 times (new trigger for each, "time since flag")

There are 2 seperate control setups... 1 for "Game" mode, 1 for "Simulation" mode ...

So, When playing on a server with more than 4 people, invariably there is a conflict with datalink ID's, with everyone staying with the default 127.500. Now that ED have introduced "Message to Country" trigger actions, I thought that MP mission designers could help the situation in the following way: - diferentiate friendly groups of KA50's by country (ie. a group of 4 from Russia, 4 from Ukraine etc...) - create a "front condition" "Unit is alive" trigger for each KA50 - action each trigger to "Message to country" for that specific groups country with the message "Use Datalink Frequency xxx.xx" In this way, each time someone spawns, the choppers in that group get a message as to what DL frequency they should be using, and hopefully this will keep things a bit cleaner. Cheers, Nem

Make sure to use the correct fire button.. man... this should be in the FAQ...there is a different button to fire cannon and weapons on external hardpoints.. Unsure of default key setups sorry, but look under keys "INS Cyclic" , you should find it...

netgear DG834 seems fine... I've not really left it to see if it shows up on the master server list, but people have had no issue connecting to IP and port 10308

I guess you could use Target points as substitute waypoints?..I think you can store about 10 of those? but yeah, the PVI can only store 6 nav waypoints and 2 airfields...just the way it is...

hmmm..poxy...is that in the english dictionary? ;)

No, If the rotor RPM is dropping due to the increased resistance caused by raising the collective, then you need to lower the collective in order to reduce drag, and allow the rotors to get upto speed again. It is very very dangerous to decay rotor RPM when close to the ground for this reason! Rotor decay can happen when you emergency stop (ie. pull the nose up), or if you add to much collective too quickly, or (if you are Frazier) are in teh middle of some high G manuever like a loop. If RPM gets too low, as well as dropping from the sky, you will also stop generating AC power (DC power thankfully comes from the batteries)...so any gear that runs on AC (ie a lot of stuff!) will drop off...... Most of the super vital stuff is DC thanksfully, but still, can be a bit of a shock. *edit* As someone above has also said, the Other yellow lights that go on (above your head) are the LH and RH max power lights, which mean (again) that you are pulling too much collective...In this case though, rather than rotor RPM decay beeing the issue, it is engine temeprature (or to be precise engine exhaust gas temperature)......these yellow lights come on to warn you that the EEG's (electronic engine governors) are reducing horsepower to the enigines to cool them down....if you fly "in the yellow" for too long, you can get engine failure. In both cases, you need to lower collective a bit untill teh yelklow lights go off ... this might mean you also have to nose up a bit to keep level flight (and therefore slow down a bit)....these things usually happen when you are trying to fly too high or too fast!

I find manual quicker that Auto (well...if theres ground power any way), and allways use manual as a result. ....+ I'm a 9th degree switchologist fanboy, lol

Hiya Fing, The only part you are missing about the PVI is the fact that it drives the heading and distance info on the HSI (round compass like guage on the lower left side next to the TV screen)...the numbers, while looking pretty, are only lat/long info, and only usefull for a select few hardcore ;) ... Use the HSI to see where the PVI waypoint is. the HSI is your primary navigation display, and gives you heading and range (and track angle) to the Selected PVI waypoint. The PVI also gives the same info to your HUD display, so will show a heading carrot on your HUD, and it also instructs the autopilot. What can (often) happen in combat, is for the AC power to drop out for various reasons (emergency stops degrading rotor RPM, or damage to the generators), in which case you will not have the ABRIS to navigate with.... the Abris is a great "quick look" SA tool, but your navigation will be much more accurate if you use the HSI and PVI .. The PVI stores up to 6 waypoints, and 2 airfields (all done automatically in the mission editor by the mission designer)..to access the waypoints, press the "waypoint" button, then press the number of the waypoint you want (1 .. 6), be aware!!!!... the PVI waypoints can be differnt names / numbers to the Abris waypoints! ... PVI Nav waypoint 1 is the first NON Takeoff waypoint... Takeoff and Landing airfields are stored seperately, and access by pressing the "Air Field" button, then either 1 (for takeoff field) or 2 (for landing field IF it is different from takeoff) so in short, the ABRIS is great, and usefull, but is only a navigation guide....accuracy and integration into the shark's AP and sterring systems is only via the PVI.