JG14_Smil

dobri dahn, (pardon my poor language. Mother's family was from Croatia and I wish I learned to speak more of it.) That stinks it is not running well! It is probably the best NTTR update in some time. The usual performance killer is the Deferred Shadows setting. If we want to run this, we need to upgrade. Sad, but true. I find DCS to be just fine without it. Also, I note "lowered Nvidia settings". Set everyone of those settings to default and let application control do it all. They pretty much only hurt performance in DCS. Best thread about optimizing I've ever seen is here: https://forums.eagle.ru/showthread.php?t=68060 Best of luck to you, I just noticed what forum I am in... hope whatever version you are referring to runs better. :)

I want to apologize for going OT. My comment about the what the manual says is not about the real L-39. What I would like to know: It seems like these secondary scales are a readout of MSL altitude when QFE is set to 0 to match an airfield. Is this correct in the actual VD-20? If it is true, and the numbers are off, it might be something fixable and that will be addressed in another post.

Yes, I understand that and can see it work at Groom Lake as it goes off the scale there. I'll point out why it is wrong in the future. My friend, for the record, you just paraphrased the manual. ;)

Addmentum FLIGHT PLANS AND EXAPMLES OF AVIONICS USE ------------------------------------------------------------ Finding QFE at destination airfield/RSBN To find QFE of your destination airfield and RSBN beacon: 1. Note Current runway altitude and QFE. 2. Note destination runway altitude. Note difference between the two numbers. 3a. Destination is higher than departure - subtract difference from departure runway alt (using altimeter QFE setting knob). 3b. Destination is lower than departure - add difference to departure runway alt. 4. Note new QFE setting on altimeter. 5. New QFE setting is your destination runway altitude (very close) and this value can be entered into the ZDV-30 RSBN Pressure setting. EXAMPLE 1.5.7 AO server is currently at 76.00 QFE (from briefing), Sukuhmi altitude is 11m. Mozdok altitude is 155m. 144 is subtracted on the altimeter using QFE setting knob. New value is 74.7. Altimeter will now read at or near '0' at Mozdok. Entering 74.7 on the ZDV-30 means we get a 600m altitude when the End of Descent lamp comes on during our RSBN approach. I recommend rounding the number 'up'. ----------------------------------- Setting Off the Scale QFE ----------------------------------- Manual RSBN Use w.i.p.

Hello, I have a question regarding the VD-20 barometric altimeter. Indexes "1" and "2" appear to show MSL altitude when the QFE is set so runway altitude shows "0", but this value is affected by the QFE setting and then becomes inaccurate. Value shown is 810m and actual value is supposed to be 952m. Setting QFE to 75.99 gets this much closer to the proper number, but then the runway runway zero setting is off. This is what I never can understand about QFE in DCS. That scale for MSL should show the proper altitude number when runway is set to zero. The QFE knob should correctly adjust both of these indexes. It does not, or the outer indexes use improper math code. Here is what the manual says about this index (and I'm calling BS): 5. Pressure correction indexes, for landing at high altitude airfields, where pressure is less than 670 mmHg. The indexes are moved by the knob. I am guessing this is another fundamental bug of DCS(?)

Got it. Thanks, Bud. Pretty busy lately and might be a day or two before I get to it.

Using this in the NTTR Summary: I used to think this flying the L-39 PRMG/ILS was difficult, but I have found it a lot more simple if: You understand and can operate the avionics. You understand how the beacons work. You learn and practice a standardized landing procedure. You center the ILS crosshairs, matching the glideslope to the VVI. (yellow lines) Match the localizer to your heading, which is matched to your level Artificial Horizon. (red lines) Simple as that. With practice that is... T, K flags? I used these teasers to help me learn and remember "loKalizer" "gliTeslope" It works. Extra points for silly accents.

Standard Landing Procedure The L-39 Manual is quite confusing when it teaches operation of the RSBN/PRMG. Here is a quick run-down of what the manual says: ------- Sector A/B - you are either making a straight-in approach or must maneuver to get into position for approach and receive PRMG. Sector A is within the PRMG localizer and glideslope. Please note you don't have to set the Inner/Outer NDB beacons. It is a redundant back-up and can confuse you at first. The markers will work without these frequencies being used. The RSBN Glidepath mode is used when descending from cruise altitude, which is generally 5-8km MSL (mean sea level), and it is usable anytime within 132KM of your RSBN beacon. It is used to descend through a cloud deck to pattern altitude of 600m, 21KM from your selected RSBN beacon. The "End of Descent" lamp will light and you then fly level until you intercept the PRMG glideslope or make a visual landing. You are expected to fly at 400-500kmh. If you are in the before mentioned "sector A", you can bypass the glideslope mode and use landing mode instead. Landing procedures from the L-39 manual for RSBN/PRMG can be quite slow and a bit confusing. I've come up with this procedure that is based on the book numbers for a long PRMG landing after completing the RSBN descent. Metric - 600m alt, 400kmph, neutral trim. - Distance X, 80-85%, airbrake out, -6 VVI. - 340kmph, extend gear, -6 VVI. - 310kmph, flaps out, -4 VVI. - 260kmph, full flaps, airbrake in, let nose droop to prevent blooming, throttle 90-95%, -4 VVI. - 230kmph approach until flare. - Outer beacon marker = 200m, 260-300kmh. - Inner beacon marker = 80m, 230kmh. Imperial Units: Added soon. Note Distance X is your choice and the same procedure is always used. For doing PRMG/ILS, it is best to be in the landing configuration a long way out and fly the approach at 230 kmh. The L-39 needs to be flown all the way to the ground under power. When the L-39 decelerates, it can fly a bit crooked and it is easier to keep straight when under power. By changing Distance X, you can use this landing procedure all the time, VFR or IFR. When you do this landing procedure and time it perfectly, it is a very satisfying experience (and landing).

About RSBN/PRMG/ARK RSBN beacon The RSBN beacon is very much like a VOR/DME. It has 360 radial radio beacons that you can fly outbound or inbound. RMI pointer will always point at this beacon and distance in KMs will be displayed. By using your course heading selector that you can set as inbound or outbound, you can intercept these radial beacons, allowing you to fly to any location on a chart (with radio signal). Each RSBN beacon has a glideslope that, when pressure is set correctly, will display on your HSI/RMI: 21km and less - 600m altitude level. 132km-21km is a glidepath from 8km altitude to 600m. The RSBN has a steeper glidepath than a PRMG. It is meant for penetrating a cloud layer and coming in level at pattern altitude. At 21km or so, the End of Descent annunciator will light up. This will signal you to swith to PRMG landing mode. The PRMG glidepath will be high above you. You fly level until you intercept it again. The ZDV-30 RSBN pressure setting must match the landing airfield QFE pressure setting! If pressure is not set correctly, you have a high likelyhood of CFIT (controlled flight into terrain). Each beacon has a unique Morse code identifier. PRMG beacon These work like ILS beacons and extend out to 70km. You must have the channel selected and the RSBN mode switch set to landing. T and K flags will turn off when you are receiving these signals and KMs to the PRMG beacon are displayed. Each beacon has a unique Morse code identifier. You can choose to fly this from 70km out and ignore the RSBN glidepath. Runways that are sloped matter a lot to ILS. Uphill runways mean low angle approaches (as in North Las Vegas). Fly above the glidepath on these. NDB beacon Non-directional beacons are used for homing with RKL-41 avionics. They do not emit radials (no inbound or outbound) and there is no distance measuring equipment (DME). These transmit A.M radio station frequencies and can even play music instead of Morse code identifiers (no longer modeled in DCS). Often used as marker beacons for landing.

RKL-41 ARK-22 ADF/RMI The RKL-41 ARK-22 RMI/ADF (radio magnetic indicator/automatic direction finder) can allow you to cross check your position. The RMI will point at an A.M. band frequency it is tuned to. If you are flying north, and your RMI points 090* to your NDB, you are somewhere due west of this beacon. It can be used as a backup for the PRMG if there are inner/outer marker beacons at that airport. You would fly over the outer beacon, start a timer, then time yourself as you fly over the inner beacon and hopefully can then see the runway while under your altitude minimum. Each NDB has a unique Morse code identifier. The RMI/ADF is located on the front instrument panel, under the VVI gauge. 1,2,3 are tuners for the "Far", "Outer" or "O" NDB. The left non-numbered wheels control the "I", "near" or "Inner". 1. Right/left click here for hundreds and thousands of the frequency. 2. Right/left click here for tens of the frequency. 3. Mouse wheel here for the decimal of the frequency. 4. "Off / C Automatic" - on off switch. "Aut" or automatic means when you have inner and outer marker NDB beacons set and this will switch automatically when you fly over these beacons. "Man" or manual means you must switch the "O"/"I" switch yourself as you fly over these beacons. "Ant" or antenna mode "is used to adjust RKL ADF to NDB frequency" and does not show the direction to the NDB (from DCS manual). 'Loop' mode is for "finding radio stations be hearing" (from DCS manual). I am guessing you use L/R switch to rotate the antenna and listen for the loudest signal. 5. "TLF/TLG" - TLF is normal direction finder operation. TLG uses the meter "8" so you can tune for maximum reception. The exact listed tuning is not always the optimal setting. TLG stops the Morse code identifier from playing in the radio intercom. 6. Front / Rear seat control of ARK-22. Untested. 8. Meter - shows signal strength when in the TLG mode. No Morse code ID is played. 9. "O" / "I" switch. Switches between the two ARK-22 channels. 10. ADF switch slaves the ID signal to the intercom for identification.

L-39 Controls you will use 1. RSBN Channel Selector. 2. PRMG Channel Selector. 3. RSBN/PRMG Mode Switch After RSBN and PRMG channels are selected, the RSBN mode switch controls the following: PRMG Landing mode. This works like an ILS. RSBN callsign button is to PRMG beacon. Distance to the PRMG beacon is measured in KM (instead of RSBN beacon). RSBN Navigation mode. This works like a VOR/DME receiver. The RMI pointer will point towards the RSBN beacon and distance from the RSBN beacon will be measured in KM. RSBN callsign button is to RSBN beacon. RSBN Glidepath mode. Each RSBN beacon has a glideslope built in and distance from the RSBN beacon will be measured in KM. This switch allows you to follow it down to pattern altitude. 4. SDU Remote switch is used to slave the ILS crosshairs to the ADI. I remember this worked great in the Su-27, but the code for this in the L-39 is not as polished. It might be helpful to some. When slaved, the red T and K flags will match the white T and K flags of the HSI/RMI and you will have pointers to show where to move your controls to follow the selected path. 5. ZDV-30 RSBN pressure setting. This must be set to match the RSBN beacon you want to use a glidepath. PU-26E Control panel for GMK-1AE DG This panel will slave the HSI to the Magnetic compass (MC) or the Digital Gyro (DG). You can set the 6. DG/MC switch to DG, then use the switch below it (switch #7) to move the DG heading left/right as needed to match the magnetic heading. 8. RSBN Radio button Pushing and holding this button will allow the RSBN/PRMG Morse code identifier to be heard on the intercom. You may have to hold it until the repeated codes play completely.

Beacons.lua file The beacons.lua file. To fly radio navigation in the NTTR, the beacons.lua has to be modified to include RSBN and PRMG beacons. I forget who first modified the file to do this. I think I can remember 'Tarres' making a mod and I *think* this is where the attached file originally comes from. All due credit goes to the mod maker. I know others have fixed errors along the way to get to this final version, which is 100% tested as of 2.1.1.6837. It works online or offline, no difference. You may use any modified beacons.lua you wish, as long as you know the frequencies and they work (some don't from the original files). In the modified file, copies of original ILS and VORTAC beacons are re-created as PRMG and RSBN beacons. These beacons act just like the original RSBN/PRMG beacons are supposed to, they do not interfere with the original ILS and VORTAC beacons, they do not add objects to the map to affect performance, they do not generate any log file errors (the original N Las Vegas ILS does, though) and it does not affect any integrity checks. The zip file contains a readme.txt, beacons.lua file, RSBN PRMG 211 NTTR.txt file and ARK NDB 211 NTTR.txt file. File can easily be installed manually or with JGSME. Location of file is usually: C:\Program Files\Eagle Dynamics\DCS World 2 OpenAlpha\Mods\terrains\Nevada\beacons.lua. Copy or rename the original file before installing. Any bad points? Only known bad points of using the beacons.lua mod is when in the Mission Editor (ME), the blue modified beacons are inlayed across the tops of the original beacons when looking at the ME map. F10 map VORTAC beacons are also overlaid and can be difficult to read. -------------------- JGSME version is available here - Note this version does not contain txt files. I cannot edit this file to add txt files. This beacons.lua does not have added NDB markers. Zip file below contains beacons.lua with NDB Marker beacons and txt file contains all RSBN/PRMG info. No txt file for NDB's just yet, but all should work.

I see many L-39 pilots that do not know it is possible to fly radio navigation in the NTTR with the L-39. This thread will explain how to make it happen and what to expect. While I am not qualified to teach IFR, I can help with learning from the L-39 user manual, which can be pretty confusing. Most of this is applied to MP flight. This, in some ways, limits how you can fly the L-39 as some items are controlled only from the back seat. I know I had some trouble learning from the manual and I've talked with others that posed the same questions. I hope this can help get around that for some.

Wise words.

If all is well with DCS, you may have to edit your throttle axis. Use the Slider option and make sure the red dot that moves sits in either a Deadband or Saturation X flat spot when at full and idle. If it is not, you may try calibrating your controller in Windows. Win10 makes it hard to find!! settings / devices / Related Settings, Devices and Printers / find your hardware, drag and drop a shortcut to it on your desktop. Right click this, then Game Controller Settings.

Hello. Is you fuel gauge on empty? If so, there was an issue in the past that caused this. You may have to go through your control settings to make sure there are no double axis assignments.

Slider option makes zero go to the left side. (non-centering axis)

Oh BTW, Thanks for posting the video DigitalEngine!

Yes, RSBN and PRMG are blue fonts on the map. 1.5 has only 4 airports with PRMG, I believe. Most don't work well with the L-39.

Hello, I don't fly the Normandy map, but I recently did a clean install of Windows and DCS. Very different than what I had before and I learned that if I now have an active program in my taskbar, and not system tray, I get repeatable stutters. It is just something to look at in the long war against stutter.

Anyone know of any approach plates for the NTTR that could be edited for use with the L-39 and these beacons? I would love to know the proper flight paths to use.

Shaw's Fighter Combat and Maneuvering The bible about anything to do with air combat.

No problem msalama, Thank you for the kind words. If anyone knows how to make this mod JGSME capable, that might be helpful to some.

I've been trying everything I can think of to adjust both the RSBN glideslope and PRMG but no luck. Some approaches are very low, for example, North Las Vegas. RSBN glidepaths are not safe! Use PRMG. I had some poor weather, good focus and very good luck. Attached file is 100% tested. If it doesn't work and switches are correct, fly higher as you do not have radio line of sight (LOS). It contains two txt files that can be printed (use minimum margins). These list all available frequencies, ID's and Morse codes. lua file has all features from the original modder. I'm afraid I just don't know who it was. Many thanks to them. No bugs. See message 87 for file.

Yeah, I know.. I'm sorry about that. I guess I was hoping for some help testing. There is a lot to cover. I'll take the file down.