lmp

Happy New Years, guys! Thanks for the amazing MiG-21bis and looking forward to your next project, whatever it may be. (Even if it's not the Su-22)

In case you were ramp starting the MiG, did you turn the trimming system on at all (RV16 switch)?

Approach wasn't bad. A tad too slow. Don't be afraid to add a bit more thrust too. As you crossed the threshold you were descenting at 2 - 3 m/s. Fine and dandy at this point. But then, instead of flaring, you pushed the stick forward (why? to get better visibility?) and you hit the runway at 5 m/s. That's way too fast. Try instead to flare just before touchdown and bring the vertical velocity to almost nothing. So: - Aim for 340 - 360km/h on short final. - That'll require about 85% of RPM, that's more than what I've seen in your vid. - Cross the runway threshold at 320 - 340km/h. - After this point pay less attention to speed and focus on slowing down your descent rate to 1 m/s juuust before touchdown. That last part requires some practice, it's easy to level out too high or start slowing down too late. But you'll get the hang of it. If you can land a helicopter (which as we all know, flies on witchcraft and secretly wants to kill you ;) ) you can fly the MiG.

Read the chapter "Operational limitations" in the manual, particularly pages 33 and 34 dealing with the landing limitations. Maximum landing weights are listed there as well as payload/fuel combinations that'll keep you within them.

Two most common errors I've noticed people commiting (and commited myself): - Being overweight. A little bit overweight is fine, full tanks and combat load not so much. I try to have no more than 1000l of fuel left when I'm landing. Less if I have anything significant under the wings. - Pulling thrust to idle in the flare. If you do that, the SPS system will turn off and immediately you'll get a few extra m/s of descent rate. Only pull throttle to idle when you're firmly on the ground. Keep these two things in mind and follow the procedure from the manual and you should be fine. EDIT: Ah, ninja'd ;).

Actually, it's pretty impossible to tell what everybody (or rather, the majority of customers, since there's not a single thing that everybody would like) wants based solely on wishlists and threads like this one. People who are most likely to post may not be the ones who are most likely to buy or to play on MP servers. Where I work we of course listen to the community requests and complaints but if what the community says goes against what our business statistics show us... guess what wins? My intuition tells me planes like the upcoming F/A-18C and Mirage will be very popular (not a difficult guess frankly), but whether they will be more popular than WW2 planes, especially if you factor in the production costs? I don't think that's clear based on just the community input. This.

Depends. Both are good planes. What do you want to do with it?

How is any of the fighters in DCS (and I mean those made by ED as well as other developers) not well known?

I sure hope so! There's already enough planes used by those countries to make them very viable additions.

My $0.02: I don't mind there being unrealistic features as long as I don't have to use them. So gunpods, Grom missiles, RS-2US, fixed beam locking to the ground are ok as far as I'm concerned. I'll just ignore them. But I would really, really love the ASP to work as it should. You can turn off the radar and the radar altimeter and you'll still get proper range to target even if it's on top of the Elbrus. Come on, if the Su-25's gunsight can be inaccurate without the laser rangefinder, so can the MiG's.

Control the ground?

And a teaser theme:

I don't think adding a curve to your slider will help. Do experiment with curves on the X and Y axes - different people have different preferences here, so you'll just have to find what's best for you - but in case of the collective you probably want a uniform response across the whole range. You can always try though, who knows? Anyway, some promised tips. Start with hover taxiing: - As you already noticed, the helicopter has a tendency to pitch down, roll left and yaw left at take-off power. For that reason, you can try trimming your controls to counter that before you start adding power. Set the wheel brakes on, pull the stick about, say, 1/8th of the way back and right, apply the same amount of right pedal, press T and center the controls. You can confirm against the control indicator (RCTRL + ENTER toggles it on and off if I'm right). I don't think you would take off with wheel brakes applied in real life, but considering you're using a twist grip, it might be easier this way. - Increase the power gradually until the aircraft begins to feel "light" on wheels. It may start accelerating forward or backward a little bit, pay attention to it and try to counter it with the controls. The key is not to overdo it - and it'll come with practice. - Increase power just a little bit more, so that the aircraft climbs to a few feet, but no more. Once the aircraft is stable at that altitude, you can leave the collective there for now. - Try to prevent the helicopter from yawing or accelerating in either direction. Once you can keep it more or less stationary, try moving forward and backward (but keep the airspeed below 25km/h), turning with the pedals and landing by lowering the power gently. Get comfortable doing this (don't worry if it takes you a good few hours, it's normal) and only then move on to the more difficult maneuvers like landing from a proper cruise or hovering at high altitudes. You'll have the basics down and you'll feel much better about yourself :).

Some shaking when slowing down is normal. If you haven't flown a DCS helicopter before, you will need quite a few hours to get somewhat proficient at it. Don't get discouraged. And focus on one thing at a time - get the take offs down before you move on to landings. I'll try to write some tips when I'm out of work.

Cluttering the forum with redundant threads is against the forum rules (see point 1.4 and what iFoxRomeo posted) and also goes against common netiquette. But you're right about one thing. Instead of pointing it out in perhaps not the most classy way (my bad), I should have just reported your post. I'll do a mental note to do that next time.

Here you go: http://forums.eagle.ru/showthread.php?t=132701 Barely a month old thread. But why look for one, when you can post your own bazillionth "please make the plane I want" thread instead?

Try hovering near tall buildings or towers first. This way you'll have to deal with being out of ground effect, having to use more power and control your rate of climb more etc., but at the same time you'll still have a good visual reference outside the cockpit.

You can't "tune" the ADF to the waypoints set in the editor. The frequencies in the briefings are for radio comms, not navigation. The ADF can only point you at NDBs (non directional beacons), which are mostly placed near airfields. At any rate, there are none in South Ossetia and you won't be using them in the campaign much. You have a doppler navigation system, where you can input a course and it'll tell you how far you've traveled along it and what your deviation from it is. It can be very useful, but you'll have to remember (or note down) all the distances and courses between waypoints yourself and input them when needed. Other than that, you'll have to learn to follow the terrain (rivers, valleys, roads, towns...).

If I'm right, the units on the bar should depend on what you have set in the options. You can choose to have it display imperial or metric units.

None of what you said is true for FC3 aircraft. You only need to set frequencies and press RALT + / instead of just / in some of the other modules. Is it a problem only with getting take off clearance? If yes, I have two ideas: - If you start on the runway, I think you already have take off clearance and the ATC won't respond. - If you're taxiing from the ramp/parking area, you need to be fairly close to the runway to receive a reply from ATC.

Those are MiG-21PF, not F-13. :)

I think S stands for Suicide. ;)

UHFs (e.g. 260 MHz) are used by the very module you just purchased - the F-86F. In the editor, if you look in the frequency tab of your F-86 settings, you'll see the default list of frequencies configured for each channel of the radio set - they're all UHFs. HFs are used by the WW2 modules and the VHFs by pretty much everything else, as you pointed out.

If a programmer is outright stuck, or has an important decision to make, he consults his colleagues. That's how it works in every healthy company and that's how it's been everywhere I worked. But if a team is not understaffed, permanently assigning more programmers to it just causes a big mess. And stalls other projects where the reassigned programmers would actually be useful. I've seen this sort of mistakes made and generally everybody in the industry learns quickly that certain tasks take longer and there's only so much you can do about it. More hands on board means better in some occupations but not in other. Do you ask for ten dentists to work on your teeth when you're in a hurry? ;)

Software development doesn't work like factory production of goods. You can't always just throw more people at the problem and solve it faster that way. Every new programmer on the team needs to communicate and coordinate with the rest. If there are too many of them, work cannot be divided efficiently. Also, moving programmers between projects is a long and therefore costly process. The new guy on the team will need to learn the ropes and will take up a lot of his senior colleagues' time as he does so. Most of the time that means that for a few days, weeks or even months he'll be slowing the work down rather than accelerating it.