-
Posts
3153 -
Joined
-
Last visited
-
Days Won
2
Content Type
Profiles
Forums
Events
Everything posted by IvanK
-
Workaround .... For the moment battery start don't use external power
-
investigating Bombing solution seems to use Barometric Altitude only
IvanK replied to ldnz's topic in Bugs and Problems
Ok thanks. found it too -
investigating Bombing solution seems to use Barometric Altitude only
IvanK replied to ldnz's topic in Bugs and Problems
Can you show us that in both English and the native ? Be great to see it. I have the L18 (VTU-01.VTUP.001/01.0) manual got a page reference for the statement. I struggle with the Yugoslav translation though. I do but struggling with the translation -
investigating Bombing solution seems to use Barometric Altitude only
IvanK replied to ldnz's topic in Bugs and Problems
Why are you talking about QFE ? The ME entry for atmospheric pressure is QNH that is Altitude Above Mean Sea Level (AMSL) QFE is Altitude above the airfield elevation ... setting QFE will have the altimeter reading zero. The DTC Altitude entry is AMSL so you need to be setting QNH on the aircraft Altimeter. The DTC in DCS is not interested in QFE ! IRL I believe standard Russian practice is indeed to use QFE rather than QNH certainly for airfield operations. However At present the DTC and therfore the MIG29 weapons calculation are only interested in QNH as the altitude datum. Our only reference we have found so far is the Alan R . Wise version of the MIG29 manual that talks about setting a Delta H value for target elevation into the system. Now if this is indeed correct then QFE would indeed be what the weapon system references. Here in lies the conundrum, DCS DTC is using QNH as the datum DEVS A clear description from the devs on how the MIG29 actually does its ranging (in DCS) would solve this argument once and for all. At present we are all groping in the dark just a little. -
investigating Bombing solution seems to use Barometric Altitude only
IvanK replied to ldnz's topic in Bugs and Problems
No yoyo. It means for non laser range deliveries only you need target area altitude for an accurate delivery. Since it would seem (in DCS anyway) that baro ranging is all you get if the laser is not available. if you want to ensure laser ranging is available get some decent dive angle going. Chances are this will also result in a CCIP delivery anyway. I dont think target altitude in the DTC is required ( or even used )if you have laser ranging. It would be good practice however to set it in case you dont get laser ranging. -
investigating Bombing solution seems to use Barometric Altitude only
IvanK replied to ldnz's topic in Bugs and Problems
When using the DTC to set a Target elevation and reading the Target Altitude from the MB map be aware that the altitude is AMSL so is QNH referenced. That means you aircraft needs to be using QNH as well not QFE. (This is different to the method implied in the R.Wise flight manual excepts which use a Delta H value and therefore would mean everything is QFE based) I have been testing on the Nevada map QNH760mm Take off Toonopah Test range elev 1687m AMSL. Target on a Mountain top elev 2780m AMSL derived from MB map. I set 2780m in the DTC on the target Waypoint. Then flew the sortie flying a level pass in CCRP no Laser ranging no pre designation , nil wind. Altimeter set to 760mm QNH. Target selected as the active waypoint. I am achieving consistent direct hits 500KG LD bombs. The available documentation on all of this ranging issue is next to non existent. It would be really nice to get some definitive documentation on just how the MIG29 does its ranging when the laser is not available. -
If we accept the process described in the Wise version of the Mig29 manual and that the SOP for altimetry use in the MIG29 is to use QFE then its sort of logical. Preflight the Ground crew set the Ballistics data (Weapon codes) and the Delta H value of the general target area compared with the departure airfield. Essentially this is in effect setting a Target Area QFE in the Fire control system.... as long as the pilot does not change his altimeter but keeps it set at Departure airfield QFE until at least weapons release. This means its not tied to a specific waypoint or anything. It is only going to be valid if the weapons are dropped in the Target area used to calculate the delta H value. However in DCS we enter the target altitude in the DTC in feet amsl (i.e.QNH not delta H) which implies we need to be using QNH at our departure airfield !! In most cases ranging via the Laser is going to be used. If however the Laser cant provide range then there is a reversionary method using Baro ranging and sight line data. I still think Radalt range would be more usable. so the ranging priority would be Laser ..... Radalt ...... Baro
-
So if we can track down a some source documentation on how and what ballistics data (codes) are entered in the "Weapon system) pre flight (similar to the methodology detailed to enter INS AD/WYPT data) we might get a better insight. I would find it most unusual if Radalt data wasn't used as a form of Ranging, when radalt info was available.
-
From a previous post of mine.
-
A thunk on weapon release is realistic.
- 1 reply
-
- 1
-
-
Danke
-
Just to be sure If using Coop mode the radar must be in Dummy ?
-
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.
-
investigating Consistent stutter as soon as taxi starts
IvanK replied to Nealius's topic in Bugs and Problems
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.
-
Starting from C&D mode and moving resets the navigation
IvanK replied to YoYo's topic in Bugs and Problems
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
