IrLED

I experience the same thing. What was noticed - in mission editor hot start Mi8 has working altitude hold channel When cold started - channel doesn't turn on. Double checked the procedure with cold start tutorial, after the start declared COMPLETE the altitude hold channel doesn't engage still. it is on current open beta 43704

Reported similar problem ~1 year ago. GBU-12 + wind on AV8B (i assume there is no wind correction for the laser spot on harrier targeting pod) Tracks replays were unreliable back then. General observation - zero wind and moving T-90 (50kmh ~=25kt) receives significant damage (but not direct hit) stationary T-90 in 20kt(36kmh) wind doesn't get any damage because the miss is much greater. I assume the tracking of stationary target + X kmh wind should be equivalent as X kmh moving target with zero wind for the GBU going through the airmass. But still air conditions give much better results. Edge case for target moving directly downwind with the speed of wind should be equivalent to stationary target in still air (airmass moves with the target)

Maybe because they were traveling downwind. Attached another track with stationary targets, should be easy to hit statics in 10m/s wind (36 kmh). Almost like hitting moving target (36kmh) in still air. But not the case. It was easier to hit 50kmh moving tank in still air then stationary tank in 36kmh wind. wind_gbu_static.trk

Open beta 2.7.15.25026 Track doesn't replay reliably. If on first strafe the last tank in column is not tracked, the whole chain of events becomes senseless. better to replay the track again -------------- Will record another track with stationary tanks

This bug currently makes LGBs marginally useful useless in something stronger then calm winds. Bombing stationary target in 20kts winds(36kmh) is effectively like bombing moving target going at 36kmh speed in still weather. Track of AV8B attacking column of T-90s on the move. Wind is 20kts. After the column stopped, 2 stationary bombing runs hit the same ground point. Caucasus wind_gbu_column.trk

Today 09DEC2015 DCS_Updater was updated to 2.6.9.43 (digisign from ‎8 ‎dec ‎2015 ‎ 21:30:41) and it looks like functionality to switch between release/openbeta is broken (http://forums.eagle.ru/showthread.php?t=114030) Command like DCS_Updater.exe update release:1.2.16 gives [Wrong update command syntax] dialog Using recommended syntax gives error in log (eg. "DCS_Updater.exe update 1.5" -> ERROR: Version 1.5 is not available.)

From the standpoint of the customer (A10C BFTQ, AATQ, TTQ) No argument that NTTR is more natural setting for US aircrafts. On the other hand, raising requirements towards NTTR(50$) to run already sold campaigns and dropping Caucasus theater support is a bit discouraging. If background color matters, then it does. Anyway it's up to author to consider

After some investigation - looks like a bug Pressing UFC ENT key should give true MSL in XXXXG section according to Flight Manual, section Delta Radar/EGI GPS Altitude Numerics (p. 395) http://forums.eagle.ru/showthread.php?t=126257

That "probing" pass might have worked if i had HUD turned on (or maybe there are other ways to read radar alt value from CDU/MFCD). Still most precise would be POSINFO G ALT value with suppressed vertical offset.

Hi Is there the way to determine true (MSL) altitude of my plane? not F10 map way. Possible sources of such information are 1.Barometric: Altimeter (DCS A10C Flight Manual EN.pdf, p.124)- reading depends on pressure level set 2. CDU SYSTEM/CADC page (p.216) Pressure Altitude (P ALT), L4 - MSL altitude for uniform pressure 29.92 inHg Barometric Altitude (B ALT), L5 - digital value of the altimeter (see #1) 3.CDU POSINFO page (p.178) GPS Altitude (G ALT), L9 - might be reliable source but the value is somehow offsetted (it is zeroed to airfield you start at, i didn't check its value if you spawn airborne) The only reliable source of the altitude i see is G ALT (if corresponding subsystems function). But that G ALT offset IS the problem. Can i affect it? Or can i get my MSL altitude the other way? Thanks P.S. What it's all for you might ask. I'm testing myself with navigational challenges. The next one in mind is landing in difficult weather conditions (HUD turned off, night, fog, uneven pressure) at one of the abandoned airfields (GPS 3D-NAV glideslope) - i.e. masochistic fun :joystick:. There is no ILS, PAPI, ACT/QFE value for that field to set the altimeter with. Resulting barometric altitude and waypoint elevation (CDU) affect ADI horisontal needle and if values don't correspond - fail.