Cheetah7798

I've been flying the Ka-50 for quite some time now and I'm willing to say that there's only a short list of things left in the shark that can surprise me. That said, there is something I've always wondered. The PVI-800 is a great nav system. Flip the INU switch up, pan the shkval to something, lase it, hit "un-cage"; bam! got yourself a set of pin-point coordinates for later reference. Now, what about manual entry? Question No. 1: How accurate is the PVI-800's manual input? Something that's immediately apparent is that the PVI-800's display only shows coordinates down to a tenth of a minute. My question is, does it accept further input beyond what is displayed, or is all input beyond the tenths place just some overflow that gets wiped after you hit the next 0, 1 or 'enter'. I mean, considering the resolution you get from a Shkval based entry, I would hope greater coordinate accuracy was possible than to the nearest tenth of a minute. Question No. 2: During manual input, can you account for altitude? There is, seemingly, some hidden reference to altitude in the PVI-800, since a Shkval based entry gives accurate reference to a position, regardless of altitude (in my experience). However, when entering coordinates manually, I am almost always left with a target point that is either suspended above the target, or deep beneath them. Is there a way to adjust this? In closing, a scenario I see crop up often enough is one where I know of a [threatening] target beyond the 15km limit of the laser's range-finding potential, which also happens to be obstructed (by trees, hills or mountains). For an example, let's use a Buk emplacement. Being able to punch in a set of target coordinates, confident that when you fire up your Shkval, it'll put the target at least somewhere on the screen, would be an awesome capability to have. Sure, there are alternatives, but this appears to be the least taxing on the pilot, as most of the work is done prior.

Here I am, absolutely amazed at the huge influence torque has over the Bf 109's flight characteristics, and yet it never occurred to me that it was the reason I was having trouble turning right at low speeds :doh: Thank's guys. This has been really insightful.

Yea, I know the AI are hit or miss. Similar to any flight sims, really. Simultaneously both impossibly-difficult and unfathomably stupid. I never really attribute any feelings of satisfaction to beating the AI, I was merely using it as a comparison between the I-16 and Bf 109. Still a flawed comparison, but gave some perspective all the same.

Thanks for the answers. I am glad to hear that it's my employment of the aircraft that is the culprit. Since the post I've managed to get a handful of wins against the spitfire in a similar fashion to what is stated above. I.E. keeping my energy up and avoiding tight turns. Once again, thanks. :D

Thanks for the response. I'll be sure to give it a go.

Have not been using the MW-50. I suspected it would play a roll, I just figured, due to it's limited usage, and due to my oil temperature nestled against the upper limit indicator during the latter parts of a dog fight, that its use was probably best avoided. As for keeping my eye on the ball, yea. I got a decent amount of experience with that, primarily from Il-2. And, like I said, in the I-16, I have no issues, despite the obvious acceleration and aerodynamic drawbacks of a pre-war aircraft. Though, I'm willing to attribute those 'victories' to the AI not knowing how to deal with an agile, slow-flying aircraft. EDIT: Corrected 'post-war' to 'pre-war'.

Greetings, all. Was hoping to get a few flight tips for the 109, specifically for dogfighting. Below is a bit of an elaboration. Recently, I purchased the I-16, by OctopusG. It was my first WW2-ish module in DCS, and it's amazing. So much so that it jump-started my love for WW2 combat flight sims, like the good ol' Il-2 days. That said, I decided to buy they Bf 109 K-4. After some quick time spent learning the startup and typical flight parameters, as well as its trim peculiarities; I decided to give dogfighting a go and was shocked to find I was getting shredded every time, without exception. It felt like the opponent (Spitfire AI on 'good') turned faster, had significantly lower stall speeds, and on a whole, managed to get behind me within the first two dogfight turns. It seemed, whenever I tried to match the AI's turn rate, I spun out with a right roll, and had to return the stick back to neutral to gain any response from the elevator controls, thus loosing the edge. Playing it gentle almost always put me so far behind that the AI was on my tail in no time. Contrast that to my experience in the I-16. It was a dream to fly from the get-go, despite the lack of any trim. With it, I've managed to beat 'Excellent' AI in all WW2 aircraft; and consistently, at that. Sure, sometimes the conflict would drag out 10 or even 20 minutes (*cough* Bf 109 AI *cough*), but ultimately things slowly turned my way. So, simply put, what am I getting wrong in the Bf 109? How do I maintain responsiveness in tight, medium/low-energy turns? Any tips are welcome.

Witnessed some rather strange British tactics today, seeing a Spitfire start flying backwards after I landed a couple shots on it during a stall. I have no idea if anyone has experienced this before. Interested to know. Also, loving the I-16 module. Moments before impact. The track. I-16_Dogfight_02.trk

flankerOne, you sir, are an absolute legend. I knew I was missing something simple. Many thanks, mate.

True, as current I am flying with those inverted lights, though I would argue that they just don't turn on at all. There is a minor graphical change between on and off, but It's hard to call either of them a light. In any event, it is far from impossible to adjust to.

Thanks for the answers, and in hind sight, I do recall this difference. but, in spite of this, it does little to answer the original issue. The PVI-800 is taking the coordinates from the Shkval, as well as a number of parameters from the aircraft. The ABRIS is independent and would only have affected my cross referencing. It is worth mentioning that when I put the PVI-800 into "NAV Targets" mode, the HSI initially points to the Shkval target. However, as soon as I try to input the Shkval's target as a coordinate, by pressing "1" on the pad (To assign it to the first of ten potential target nav points), followed by the "uncage Shkval" button (To transfer the Shkval target position to the PVI-800) and the "Enter" button on the pad (To confirm the process), the HSI (And input coordinates) are no longer aimed at the target.

Hey, Faman The Ka-50 takes a bit of getting used to, since its trim system is a bit more computerized than older birds, like the Mi-8 and UH-1. It may not seem like it at first, but the Ka-50's autopilot and trim system are quite a bit more user friendly than those aforementioned two. some things to keep in mind. The Ka-50 is obviously supposed to use pitch and bank autopilot 24/7, like other helicopters. the yaw AP is more for route following, target alignment and flying in straight lines without a care in the would. the altitude hold is also quite useful in a similar fashion. Though, unlike other helis, with the Ka-50, you are supposed to hold the trim button for the duration of a maneuver, then release it when in stable flight again. for instance, you are flying at 250km/h and want to slow to a hover. So, you hold in the trim button, tilt back, reduce collective, bring it to a stop, level it out, then and only then, you release the trim button. Helicopters are a hell of a lot more complex in terms of keeping stable than your conventional fixed wing aircraft. and games like battlefield really do not do them any justice with the ridiculously simplified flight modeling. My advice? lots of practice and patience. it may seem like the helicopter is ordering you around and sucking the fun out of everything at first, but in due course there will be some mutual relation within which you can co-exist.

Hey, all. I've recently been getting to know the Ka-50 quite well and thus far I have gotten my head around every thing mentioned in the manual or online... that is until today. I am trying to send the PVI-800 a target NAV via the Shkval, yet despite my best efforts, the coordinates are always entered incorrectly, and the NAV point is more often than not some distance behind me, off to one side. Here's the process I go through: I start by locking a target with the Shkval I then switch the PVI-800 into edit mode, press the NAV targets button, press 1, then press "Uncage Shkval", then Enter on the PVI-800 Then, I switch the PVI-800 back into operations mode, press on the NAV targets button and on the number 1. After this process, the HSI is pointing nowhere near the target, and after cross referencing the PVI-800's target nav coordinates with an ABRIS map marker on the actual target, I find it to be ~2 minutes off. My question: What am I doing wrong? What steps should I be taking to make this work properly?