ZaltysZ

Downloaded already :)

A2A refueling is unnecessary difficult because of how boom operator behaves now. Pilot is supposed to get into position within boom operational limits and be there while boom operator steers the boom. In DCS it feels like there are boom operation limits and separate limits for AI operator. :) You know those moments when boom moves but kinda looks numb despite you are within good range and altitude.

It is even more complicated if we add altitude factor. P-51 has 2 stage supercharger and this gives it "saw-toothed" power vs altitude curve. Depending on other aircraft power curve, relative difference in P/W can be lessened or exaggerated at certain altitudes. If I recall correctly, the best case scenario for P-51 fighting Dora is at 2000m (with not too great advantage for Dora) and above 7000m (the difference becomes insignificant there). The worst case is at 4000-5000m (Dora is scary at this altitude).

There is a catch here. It is important when diving starts and when ends. P-51 has low drag, but does not shine at low speed acceleration. If diving starts after low speed roll over, Dora, BF109, Spitfire and so on will have advantage over P-51 for a while. P-51 will begin oudiving these planes only at higher speeds. If P-51 does not keep speed high enough and does not begin diving early enough, other planes on its six might even gain on it too much (despite initial co-E) and not give it enough time for outdiving them. :)

Make crude approach, slow down, put velocity vector on the beginning of runway, then check your AoA. If it is below 20 units (HUD still shows in degrees), throttle down and rise the nose. AoA will increase, but velocity vector will stay on the beginning of runway. You don't need precision here, because you will have enough time to correct. If AoA is correct and velocity vector is more or less on the beginning of runway - you are set. Further you only need to keep the AoA (basically you will be just holding the stick) and operate the throttle: throttle up if velocity vector creeps down; throttle down, if velocity vector creeps up. This will eventually end with you flying at correct AoA and speed over the beginning of runway. However, you still need to flare (rise AoA briefly to lower vertical speed) just before the touchdown if you are heavy.

Wind in real life dimishes rapidly near the ground, because terrain, trees, buildings and etc. obstruct air flow. In ME you enter that dimished wind as wind at 10m (AGL). 500m or so higher it doubles and then transits into next wind layer.

I have done more vigorous testing and everything is fine. I was seeing 24kts in CDU when wind was 6m/s in ME and I was flying at 30-50ft ASL/AGL. The reason why it was showing higher wind was probably due to not stable enough flying. CDU lags a bit and steep wind gradient does not help it too.

Yes, but this is not the issue :) The issue is: if you set wind to 12kts (6m/s) at 10m layer and you fly your A10C exactly 10m above sea level, its NAV system will show 24kts (12m/s) wind. I have tested and wind at 10m altitude is 6m/s if ME shows 6m/s at 10m, however A10C thinks wind is double than that.

Things are complex for bombing solution and etc. However, the "glitch" is far simpler here. In fact, we can simply forget bombing for now, and concentrate just on calculation of wind near the ground. Most aircraft with advanced NAV systems can calculate wind by itself while using data from INS, GPS and so on. A10C does the same. The "glitch" is that it doubles the wind speed near the ground.

Units are not the issue. 6 m/s = 12kts. However, A10C shows 24 kts near the ground, when wind is just 12kts there. If you go higher, it shows the wind correctly. I have done a simple test: created a mission with Ka-50 near the water with 2 waypoints, then flew the mission with different winds at 10m altitude. ABRIS shows cross-track error and flight time, so I divided the former by the later and evaluated the wind. Every time it was like in mission editor. Wind isn't doubled near the ground in game world. I don't think this is a game world bug as OP suggested. I think it is just A10C problem.

Is it possible to have aircraft specific subfolder? If not, it is good candidate for wishlist. :)

I think "взаимодействие" translated as "interaction" sounds a bit unnatural. "Mutual operation", "cooperation", "coordination" are better. "Mutual operation" is safer until precise meaning of light is known. That light is yellow, and yellow means a warning for a pilot (i.e. he needs to do something). In contrast green lights work as indicators (i.e. something is in some normal state) and red ones signal an emergency. Judging by label, there seems to be relation to datalink. However, Su27 not only has an intraflight datalink, but also an ability to receive interception-steering commands from GCI. This lamp can simply mean that there is a new received command, or something along these lines, but this is just a speculation.

TrackIR Z axis can be assigned to head movement (default for 6DOF cockpits like F15, A10 and etc) or to zoom control (used to be default for all FC planes, because there wasn't possible to lean in non 6DOF cockpit). If you want zooming in while leaning, reassign TrackIR Z axis in control configuration window.

It acts the same way as Russian HUDs. They all have collimator and focus image at infinity. It means that reading the HUD is not like reading a poster 30cm away from you, it is like reading a large banner many meters away. If you move your head 30cm or even a meter towards the banner, it won't look larger, because it is still relatively far. In summary: HUD is not like a gauge, you can't lean to it and get smaller details appear larger. If text is too small while leaned back, it will be small even if you glue your nose to combiner glass. If you want things to be larger (easier to read), you have to change Field of View (zoom in), and not the head position.

FoV for F15 defaults to 140 degrees. Most Russian aircraft default to 120 degrees. Basically, you are flying a little bit more "zoomed in" in Russian planes than in F15 by default. It not only makes it harder to read the HUD in F15, but also screws your ability to judge distance and speeds when you hop from Russian planes to F15 and vice versa. You can create consistency by tweaking zoom axis for each aircraft separately (if you use joystick axis for zoom) or by editing lua file for snap views. TrackIR is better to be left for controlling head movement and not zoom.

I had opportunity to "teach" people both by using tracks and by standing behind them and giving remarks in real time. Later method was way more effective with lots of people. If you have ability to affect controls, training is even more effective, because it allows student to concentrate on particular stage of complex situation, while instructor helps on others. This is very important thing for virtual squadrons, which do the training even for very greenish pilots.

Try running Prime95 alone. Does CPU temp get much higher? It might be counterintuitive, but running Prime95 while stress testing VGA might not be stressful enough. This is because CPU is tortured the most while running Prime95 with small FFTs or In-Place Large FFTs, what heavily relies on CPU cache for "tight" computations. Running something else alongside might mess with the cache and give load more close to Prime95 Blend type stress test.

Sounds like a power issue: UPS/PSU/motherboard (faulty caps). If you are comfortable, try doing a stress test. Such tests usually reveal major power issues quickly.

No user space application like DCS running unprivileged should be able to directly cause BSOD/reboot/similar fatal event. If it does, there is OS (design), drivers or hardware problem.

I am not a RL pilot and can share only what I have gathered from various people and documents. Let's say we don't use purely military base, which can have "mind" of its own, but some airfield which operates accordingly to international civil aviation practices (they are not written in stone and varies a bit from country to country and even from company to company). So: 1) If aircraft is operational (power/engines on) on the ground and it has anti-collision lights, they should be turned on. Anti-collision lights include beacon and strobe lights. 2) Strobe lights can be turned off, if they affect other pilots, ground personnel and so on. If this is the case, strobes are turned on just after entering the runway or crossing active runway. 3) Positional lights should be turned on and steady the whole flight. Strobes should be on, unless they are a distraction (reflections from cloud and etc.) 4) It recommended to switch from taxi to landing lights only when cleared for takeoff. It is supposed to signal others the intent for taking off. Going back to our A10. DCS flight manual and A10 checklists hint such lights usage: On ramp while operational: flashing positional and strobes off Taxi: flashing positional and strobes off Runway/Flight: steady positional and strobes on A10 has anti-collision lights, but they come only as strobes. A10 lack the beacon, which would be more eye friendly. I think flashing positional lights are supposed to be a substitute for anti-collision lights while on the ground and when strobes can't be used. If this is true, then having flashing positional lights while powering up and taxing makes sense in conjunction with previously mentioned civil aviation practices. Further, turning strobes only after lineup before takeoff also makes sense.

It should be possible to stop tracking of "imaginary" moving target the same way as tracking of normal target can be stopped: press and hold lock, then slew Shkval. This is what my muscle memory tells me when I try to imagine the situation.

P51 pilot thinks that BF109 is more agile, when he is prop hanging, stall fighting or just normally dogfighting at up to 400km/h or so. BF109 pilot thinks that P51 is more agile when he has to follow P51 into high speed steep dive, but struggles keeping up with all the banking and pulling because of too heavy controls.

And if NAV system is not ready, turning hover mode on will also turn all AP channels off.

I hope I won't be given enough time to see that :smilewink:

And to be more precise, there can be 2 indications of speed on the HUD. Digital readout at left top corner is ground speed. It will be shown if NAV system is ready and HUD is in NAV mode (no weapon active/Shkval is off). One should remember that ground speed is used for navigation and not for flying (you can't decide if you are within permitted flight envelope by using ground speed), so it makes sense if that readout is removed while in weapons mode. The second readout is a speed tape on the left side of the HUD. It shows IAS and appears once speed reaches 50 km/h. This readout is present even in weapon mode.