McVittees

I read the book and didn't think it was enough of a story to warrent a whole book. The main thing I took from this program (and the book), was how totally screwed we would have been if the Iraqs' had managed to put up decent resistance. They were flying against a full division but only one tank was trying to shoot them down and that was almost too much! The Lynx doesn't seem much of a tank hunter - the TOW missile takes ~24 seconds to reach its full range! Thank god we have Apaches + Longbow + hellfire now!

Fair point!:thumbup: It seems then that things in the world of BS are as they are supposed to be - I should've known ED had got it right! :D

to: ericinexile I feel your pain. I've been bumping my head against the wall trying to develop tactics to defeat Apaches. They really spoil my day. I haven't resorted to editing them out of missions, but I have edited win conditions so that even if they decimate my forces, I win so long as I avoid them and destroy my objective.:smartass: One thing that makes them so deadly is the relative ease and speed with which it seems they can lock you up and get a round off. Maybe it's much easier in the Apache than the Ka-50, but it seems the AI can be doing all kinds of rolling and diving and then seconds later swing round to face you and instantly loose off a Hellfire. There doesn't seem to be much re-acquisition / 'button mashing' time modeled once the AI know where you are.:cry:

I'm assuming everyone in this thread is using Track IR, because I find I only use it to lock up air-to-air targets i've padlocked. Looking around using the hat and pointing the Shkval with the HMS doesn't really work for me. Shame that.:cry:

If only someone would make a study sim of the harrier. I can't understand it - I'm sure it would be such a popular aircraft. The mission possibilities are fantastic - play it like a traditional jet from a runway or do it all dispersed like a helicopter [sigh]. I can only hope I live long enough to see it! :)

'Bizarre in so many ways' as in replying to a post made in April...in June! :huh:

Glad to hear that - now feel the wrath of the Helfire!!! (and btw it ain't no use running!:smartass:)

I'm suprised at these problems. I'm flying the second phase of Wag's campaign (flown ~16 missions and had 8 deaths on this my second run at it), and the biggest butt f**k is the bloody Apache! They seem to have the unnering ability to hunt me down and shoot me out the sky. They certainly don't have any problems spotting and engaging me! Maybe you should open up one of the missions in the campaign and see how Wags has set the Apaches to target?

Wow, Customising the menus! If this is possible it would be fantastic! However, I suspect that if it were straight forward then ED would have already incorporated the functionality. I look forward (and hope) i am proven wrong though!:)

What grade did you get for your presentation?

Now that's a bit more like it!:thumbup:

Hmm, that doesn't sound right.

Vista here too - no OS related problems.

I think you have answered your own question Esac - prepare mission is for creating and saving ABRIS information. PVI info is created in the editor when you set waypoint info, target points, nav updates and so forth.

As anyone with a history of reading avaition forums here and at other sites such as SIM HQ will know, an anti collision beacon is the 2nd most lethal weapon developed by man after the photon torpedoe. (A man named '20mm' explained much about the collision beacons importance in the early days of Lock On). Black Shark is the most realistic simulation of this device yet. Its sheer power is the reason it eats frames. Use with caution.:P

Hmm, not sure if this is what you mean but on a number of occasions I've had weird behaviour (namely crazy spinning) when turn to target is engaged, I'm in a hover (not autohover - don't use it much anymore) and rudder is trimmed centered. Basically what i think happens is the Shvkal lock drops and then I start spinning like a top. Very weird. Happened about three times to me I think. Once it was because the AP channels had started flashing so stabisation was off, but why they had started flashing and needed resetting I have no idea. As mentioned in a post above, remember that, currently, trimming also sets a new heading for the AP to try and steer to. Trim should (according to the manual) just hold the aircrafts attitude via the current control positions. I belive this behaviour is being corrected in the patch.

I didn't use the FD much before, but I have found that in situations where rapid heading changes are required it's use is essential. These times are for me: 1) when I'm doing a rockets run or close in guns run, 2) when taking evasive action and 3) when engaging AA targets and need point-and-shoot capability. In the patch I think the yaw trim won't try to hold heading anymore, so I may not need to use the FD in some of these situations.

In the last few weeks I've started getting random 'unusual terminations of c++ runtime' (or similar message - haven't remembered to take a picture of this message yet). I haven't updated any system drivers or changed anything, so its odd these crashes seem to coming more often. Anyway, I have attached all crash logs I found in my ka-50/temp in case this may help (the number in the temp file is less than the number that I have had). DSC crash logs.rar

Try taking on Apaches - now they eat you up! Hinds aren't so scarey... ;)

I don't think it would be that hard to implement, afterall we've already got animated soldiers. Ground crews could spawn from a tent or truck, run over and then mill around the helo. ;) I guess, it's just a matter of time and priorites. I'd love it though - even if they didn't do much.

I guess Kamov wanted to de-clutter the HUD when employing weapons. You can still read your airspeed off of the Shkval display anyway. Agreed though, odd design choice.

Just as a point of interest, if a 30mm HE round penetrates the crew compartment of a BMP, one round could easily be enough to light up the fuel and ammo stored there. It's not a well armoured or layed out IFV. (Of course I'm not saying that this should happen every time.)

Bizare (in so many ways)! :noexpression:

I'd be curious to know the answer to this too.

:)