ZaltysZ

The first thing you should do is learning how Ka-50 flight controls and autopilot (stabilisation system) work. If you don't do that, trial and error approach will likely leave you puzzled. Once you understand the system, it will be just a matter of practice for getting better at flying.

Once you take off, speed should appear in HUD and be there the whole flight. If you take off and there is no speed in HUD, it will appear there once nav system is ready. If it disappears in the middle of flight, something is wrong: battle damage or pilot error (i.e. too much collective -> low rotor RPM -> not enough electrical power generated -> nav system off/reset; or engaged hover mode at very low altitude -> AP auto disengage -> nav system reset). Reseting Shkval does not affect this. P.S. this is about HUD in nav mode.

As far as I remember, it should show after take off.

If you engage hover mode, you will see small square inside circle on the HUD. That little square means position over which you told AP to hover. If that square moves, you are not hovering. There is a technique which heps with nailing aircraft down. Just try your best stopping and trimming aircraft for hover, and once you engage hover mode, repeatedly press trim button until aircaft stops moving. After every press of trim, that little square will move less and less. If you are flying with crosswind, it will push you off the track, and if you want to stay on the track, you will have to fly at angle, or other words crab/slide a bit. AP is no different. Minute or few.

Release of trim button updates longitudinal and latitudinal position intended for hovering, but it won't update altitude. Altitude is updated on release of collective brake.

Hover mode is like parking brake, and it is not magic button which does the parking. Slow down, trim for hover, then engage hover mode. Hover mode will remove small deviations, but it won't win over the large ones caused by out of trim attitude. Route is a bunch of lines between waypoints. Route following involves flying over those lines. If you deviate from the route, AP will try to get on the line instead of just flying to the next waypoint. Check autopilot panel, there is a switch, which changes this behavior. No speed in HUD means: a) you have just taken off and nav system is still not ready b) your rotor RPM dropped too much and you lost power required for nav system

What does tacview show? It might be just a graphical bug.

The problem is that track doesn't record object states at discrete time intervals. It records initial state and deltas (like player input) only, and then game resimulates everything on track playback. Such playback relies on determinism of calculations. Once different enough result is calculated, track playback begins to deviate. The scary thing is that there is not so much guarantee in determinism of floating point calculations once you begin comparing results even on CPUs of the same platform. There are instructions which gives different results depending on manufacturer of CPU or even model. Basically, program runs on different CPUs, but it can give tiny bit different result in same cases, and if you rely on getting exactly the same results independent of CPU, things begin to break.

Be wary of too long lase time with Paveway II series bombs as they use bang-bang guidance. Such guidance relies on two state switching (i.e. min and max deflection of control surfaces without nothing in between) and causes high drag. Basically, the earlier you begin the lasing, the more energy will be bled. If your planned time of fall is something like 35s, and autolase is 30s, you risk getting a miss.

What OS do you have? Which language? Does unhandled exception have some sort of code or stack trace?

Ka-50 has trim for cyclic and pedals (rudder). Trim nails controls where they are at the moment of trim button release. If your aircraft turns by itself, it means that autopilot is doing something (like executing turn to target) or you have released trim button while controls were not in position for stable attitude (i.e. kick rudder and release trim, aircraft will turn and turn endlessly, because pedals will be stuck in position, which causes turning). Some people prefer having trim removed from pedals, because it is easier for them to hold their feet in desired position than constantly recenter pedals with every trim button release. Even with this, they still have to put aircraft in stable attitude and hold it there. :)

"Turn to target" is supposed to turn your aircraft nose into the target. Target means the point where Shkval is looking. It won't align you for Vikhr launch, because you need your aircraft nose be slightly offset from target at the launch. Use "turn to target" and push rudder in opposite side to Vikhr reticle, then press fire button and allow aircraft nose to return to previous position.

You need curvilinear projection for such distortion, however screenshot looks like it is using ordinary rectilinear projection. Rectilinear always keeps straight lines straight even if they are off center (look at the rivets in screenshot).

Which speed? HUD and ABRIS show ground speed, Shkval and ASI show IAS. If its 150km/h IAS and there is a wind, flying upwind and flying downwind will result in different ground speed. If you user Hover mode, you get AP altitude channel turned on automatically. If you exit hover by increasing collective and pushing cyclic forward, there might be a bit of altitude increase due too much collective. If AP altitude channel is on, AP will try to prevent that altitude increase by "decreasing" collective, and this in turn will affect acceleration too for brief period of time.

I have x16 AF forced for everything since 2007. Performance drop is too insignificant, and quality increase is very noticeable. It makes sure textures do not become too messy when looked at from shallow angles. So, it helps with keeping clarity of ground textures while sitting on runway, it also helps with checking aircraft markings on wings from various angles, however it should not help much with spotting contacts, because dark blob with clear or messy textures is still just a dark blob. Some variations of AA (antialiasing) can have way greater effect on contacts.

I don't like the ones that do BnZ with Spits. They are the real pain :) Fortunately they are a minority, and this use case for Spit is like a secret technique, which is still unknown for most commoners. :smartass:

About CoD: 1) Spitfire, BF109 and etc. have higher critical AoA than P-51 2) There is somewhat exaggerated inertia of controls in CoD: you can throw stick around a lot, but aircraft will lag behind way more than in other sims. 3) Some planes like BF109 are realistically control heavy at high speeds: you can pull your joystick fully, but the same won't happen in aircraft as virtual pilot isn't supposed to have enough strength to overcome stick forces at high speed. 4) Accelerated stalls:

It does.

If they are firing at you, you have made a mistake and should retreat. Basically, if targets can fire at you, you are too close; if you can't fire at them without them returning the fire, you are engaging wrong targets. You need to understand that this is mistake from your side, and you should worry more about how to avoid repeating it than worry about how to get out of it alive.

Did you take the signs (+ and -) into account. If Shkval looks at target, which is above your altitude, Shkval angle will have opposite sign than when it looks at target, which is below your altitude. Let's consider these examples: a) helicopter is at 500m, target is at 100m on the slope of hill: moving Shkval up should overestimate the range, moving down - underestimate. b) helicoper is at 500m, target is at 600m on the slope of hill: moving Shkval up should underestimate the range, moving down - overestimate.

Let's say your aircraft has tendency to dip right wing and you want means to fly level with hands off. You might implement trim in 2 ways: a) put trim tab on aileron b) put trim tab somewhere on non movable part of wing. Trim tab will have to move up in case (a), and it will have to move down in case (b) to cancel right wing dip. The difference arises because of trim tab location. Case (b) is straight forward: trim tab creates force which directly affects the wing, or in other words: trim tab is like mini aileron. Case (a) is a bit more complicated, because trim tab is like mini elevator of aileron in it. Small trim tab creates lesser force than a force required to deflect aileron, however trim tab does that at distance from the rotation axis of aileron, and so that small force is amplified by lever effect. P-51 trim tabs fall into the case (a).

In my experience, errors in range calculation are related to altitude change. I have suspicion, that system only uses target altitude and Shkval angle for passive range estimation. Something like this: laser is used for precise measurement of slant range, then it is used together with Shkval angle for calculating target altitude; further range updates are done by calculating altitude delta between target altitude and helicopter altitude, and then using it together with Shkval angle. This works fine, unless altitude delta is calculated incorrectly, and this can happen in 2 ways: a) Shkval is slewed to location, which has different elevation than the lased location b) helicopter altitude changes without system understanding that - i.e. if radar altimeter is used as source, and helicopter flies at constant AGL over terrain of various elevation.

Which parts of map? I guess, it is when you are flying (not hovering) over rough (not flat) terrain. Am I right?

Correct one is frequent depressing of trim button. It is like a safety measure. Analogy would be a mounter climber which reattaches his ropes every meter or so. If he did that lets say every 15 meters, mistakes could become very painful. However, such trimming is very uncomfortable with non FFB stick as frequent depressing of trim requires frequent recentering.

No. I didn't say not to put lift vector, I said not to put it blindly, or in other words: not to use it as rule of thumb action for defense. Blind application of rules of thumb can quickly cur your thumbs off :smilewink: My advice: put yourself in attacker's shoes and try imagining what attacker sees. If you manage that, then you will be able to choose something very uncomfortable for him, what is the point of your defense. If it is too hard, then switch to analysis after every fight: watch the track or tacview, and look from attackers perspective, i.e. use external camera on attacker and so on.