IvanK

That doesn't achieve the aim of spawning for a Cold start with a Long Alignment underway or complete initiated by the ground crew before you get to the aircraft. A Special option to enable this would be nice. If you had this you would spawn into the cockpit and see: Ground Power on, Batt On,Recorder switch on,ACFT SYS switch On, Navigation switch On,Main gyro switch On,STBY gyro Switch On,WP/AD Button on 1, Operate/Prepare switch OPER, NAV READY light out. (Ground crew would have done the Course Cmptr zero and Mag slave routine.) See Pg 2-25 of the German manual ..." Long Alignment before eng start"

I am presuming your source is this Document: I have used Google translate on pages 306-310 that describe the Air to Air Gun modes. I accept that some of the Google translation is awkward but I see no references to this 6 deg and 12 deg lead difference. If you have another reference that talks about this 6 deg versus 12 degrees I would be interested to read it. I did find some discussion about 6 Deg and 12 deg in this document on Pg70: However again using Google translate I don't think this is referring to Lead angles but rather something to do with scaling of the displayed solution in relation to the HUD FOV. Perhaps to increase accuracy by using a smaller (analogous to magnifying) area ?? A Russian speaker might give a clearer understanding. With both gun modes you can still achieve an IMC (not visible target) but in the secondary mode perhaps more accurate.

You only see this if you start with external power. It doesn't happen with a Battery start

I think its more a mode specifically set up to allow guns shots on targets in IMC (so not visible) rather than some sort of high lead tracking solution. In all the gun shots in your video you would have been able to achieve a guns tracking solution with the stock radar/Irst locked gunsight mode. Thats my take on it trying to figure it out in the Russian manuals.

Can you specify Long Alignment ???

Guidance given in the Russian manuals is that SOP for short range operations within range of RSBN beacons used for updating use Short Alignment. For Long range operations with few or no means to update by RSBN beacons use Long Alignment. Long Alignment can be done pre start with ground power available. Conceptually this would/could be done by the ground crew before the pilot gets to the jet. Be nice if this was a DCS spawn option.

Pressed for both short and long alignments

Its reported. The lower position a sort of Standby position. Over the canopy rail when someone actually wants to get in.

Or after selecting outboard ?

Nice vid. Convention and the Manuals say you should also manually set the Course arrow for manual ILS approaches. Kind of weird why it drops off the 070 setting you set up for the RSBN. Ideally you would also have the ADF's setup as outer (870) and inner (490) as well. Then together with the course arrow the yellow pointer would reference the ADF's as well. In a manual ILS you also need to manually switch the ADFS over on approach using the inner outer switch on the front panel. If the transition to ILS is brought up in AUTO (like when using the Return mode) the ADF switching is done for you.

Tried the same Syria sortie but this time used External power for the start. I got the reset and stutter as soon as I taxied. So its related to external power imo.

Google: The common Cyrillic abbreviation for "South" is the letter Ю, which is pronounced like the "you" in "you". It is used as the initial letter for words related to the south, such as юг (yug) for "south" and южный (yuzhnyy) for "southern". Ю: This Cyrillic letter, which stands for "юг" (yug), is the most common abbreviation for South. Example: In Russian, you might see "Ю" used to abbreviate "South America" (Южная Америка). ------------------------ North on the Standby compass is Marked C

Its the Cyrillic abbreviation for South. I-O

Be nice if you could load the presets via the DTC. You can access and edit the DCS before start. Best solution would be to have the current option with presets in the ME and via DTC. Before start you would bring up the DTC check the presets if not as desired then change right there.

Delta H is in metres hardwired as far as I am aware. In my notes I have converted to feet for the calcs. also another calc if down in the weeds and want the bottom of the beam on the horizon (i.e. at ground level) you need 5 deg ant elev you can get that 5 deg by: TDC 24nm Delta H +4 TDC 37nm Delta H +6

I have done it on the Germany map as well. Its weird as there is nothing definite as far as I can make out that causes or stops it happening.

Here is a TRK. Startup Syria. I change the AD/WYPT switch to WYPT, I change the the Navigation and Landing channels. Start up and taxi ... no stutter and no changes on the NAV panel. Then TO still no changes. So to me its a random event or caused by something we don't know. Mig29start3.zip

Safety wired the wrong way.

I have heard of the term rivet counter before , this is a new variant.... but I admit IRL I have done exactly this

Here is my take on making Antenna elevation control in the MIG29 in a Free search (no GCI) environment manageable. I fly in Imperial so I have used nm and feet for the discussion. The Target Manual range throttle wheel was not operational in this version of the MIG29 Situation: TDC position in range coupled with Delta H selection controls Antenna elevation and therefore the altitude coverage. With a Fixed Delta H changing the TDC position in range causes the Antenna elevation to change. So as you move the TDC over the target Antenna elevation will change, at close ranges this antenna elevation can be large. Radar Information In search the 4 Bar scan covers on average 10 degrees. The coverage does in fact vary depending on function and TDC range position but 10 degrees is a good calculation compromise. Each click of Delta H varies the beam centre Altitude coverage by 1000m or 3280' for the +- 1 Delta H click. For the remainder Delta H clicks 2, 4, 6, 8 each click raises the antenna 2 degrees or 2000m or 6400’. Proposed solution: To minimise pilot workload and keep elevation control workable I suggest placing the TDC at 30nm range. This is a typical contact range in the Mig29. It also means that small TDC changes in TDC range to place it over the target will not result in large changes in Antenna elevation. As can be seen in the diagram below 10 degrees covers a fair bit of sky 32,000' at 30nm and 64,000' at 60nm. With the TDC at 30nm the AH value effectively equates to antenna elevation in degrees. (The old Elevation formula: Ant Elev = Alt Diff in 100s ft/Range in nm might be handy) If running at sea level then to get the bottom of the beam close to parallel to the ground then set TDC at 30nm and delta H at +4. (2 clicks of Delta H = 4degrees in elevation). Which means at 30nm you are covering Ground level to 29,000’ and at 60nm ground level to 58,000’. Once you have the search process done then consider going into TWS as Antenna elevation will be controlled by the FCS. With Good GCI then the TDC can be placed at the called target range and Delta H value.

I have tried it for myself Real world in another platform ... Basic Range and Endurance control theory. Altitude is included on the Chart A4-2

Lufwaffe Manual GAF T.O. 1F-MIG29-1 Figure A4-2 specifically states 4.5deg AOA for range and 6 deg AOA for Endurance. On a side note FA18 figures are 4.2 Alpha for Range and 5.6 alpha for Endurance

Here is my take on making Antenna elevation control in the MIG29 in a Free search (no GCI) situation manageable. I fly in Imperial so I have used nm and feet for the discussion. Situation: TDC position in range coupled with Delta H selection controls Antenna elevation and therefore the altitude coverage. With a Fixed Delta H changing the TDC position in range causes the Antenna elevation to change. So as you move the TDC over the target Antenna elevation will change, at close ranges this antenna elevation can be large. Radar Specs In search the 4 Bar scan covers on average 10 degrees. The coverage does in fact vary depending on function and TDC range position but 10 degrees is a good calculation compromise. Each click of Delta H varies the beam centre Altitude coverage by 1000m or 3280' Proposed solution: To minimize pilot workload and keep elevation control workable I suggest placing the TDC at 30nm range. This is a typical contact range in the Mig29. It also means that small TDC changes in TDC range to place it over the target will not result in large changes in Antenna elevation. As can be seen in the diagram below the 10 degrees covers a fair bit of sky 32,000' at 30nm and 64,000' at 60nm. In addition its worth pointing out with the TDC at 30nm each click of Delta AH means a 1 degree change in Antenna elevation. If running at sea level then to get the bottom of the beam at and parallel to the ground then set TDC at 30nm and delta H at +5. (5 clicks of Delta H = 5degrees in elevation) Once you have the search process done then consider going into TWS as Antenna elevation will be controlled by the FCS.

Rule of thumb when hurting on gas and trying to get home: Max range at any Altitude set 4 deg Alpha power as required to maintain level flight (nil wind) Max endurance at any Altitude set 5-6 deg Alpha power as required to maintain level flight. For Max performance in both be at Optimum altitude/ Which will vary as a function of Drag Index and weight but be in the 30,000's roughly.

So if it wasn't fitted to "this version" then at what range is the delta H value referenced to ? is as has been suggested (and in game evidence supports this) it is referenced to the Acquisition cursor range ? Is this a yet to be implemented feature ? or what we are stuck with ? The "correct as is" label and the quote above from Matt in the post above to this thread implies its not going to be incorporated. .... a definitive statement here would help. Elevation changing as you try to position the acquisition cursor over the target makes it almost unmanageable in free search type operation. Probably OK in the guidance mode with DL doing the work for you. I guess TWS is the go as then I presume elevation will be controlled by the TWS mode itself ?