JG14_Smil

Hello, I have a L-39 simpit and pretty much only fly that plane. I edit my beacons.lua files so I can fly my plane anywhere and I am working on adding RSBN and PRMG to the Syria map now.

Thanks. I am starting to agree on the PG map, and I will edit my earlier posts. After testing I learned the map is different than the Caucuses map that uses similar frequencies for opposing PRMG. I could also test each direction in the ME and I cannot do that in the PG map. I did find it confusing that 13R and 31L both use 108.70 and the others do not. So, in summary, I will just say that they do not all work correctly and good luck.

After further testing, Post is edited.

I do love the ambient lighting in the pit when around the lights. I did note that the white runway centerline lights shine right through the bottom of the L-39 and I can see flashes in the pit.

Yes, a very simple fix... 13L frequency should be 109.1, chan 28. It is 111.1, chan 48 Line # 513 of the Mods\Terrain\Persian Gulf\ Beacons.lua file is incorrect frequency = 111100000.000000; - should be 109100000.000000 channel = 48; - should be 28 I also note all localizer headings are +2 degrees for my L-39.

Hello, I do a lot of editing to create RSBN and PRMG beacons for my L-39. I note the ME map shows the ILS Glide and Locators at that field starting on the runway threshold, not at the start of the runway (you don't land on thresholds), for this reason, it brings you down a bit too soon. The PRMG I created at Al Dhafra was flyable to just above 100m before the glideslope plunges into the ground. While I have affected slope angles at other fields, I had no luck doing it there. Frequencies aren't too hard to check. I'll have a look to see if they are correct.

Last two updates have killed the engine vibrations in the Mig-21 in my Jetseat. Has the export changed for this aircraft? Other aircraft are not affected and all other vibrations work in my Mig-21 profile.

All due respects Dan, but you are wrong about the flag working correctly. In either Stable or Open Beta (clean install or modified beacons do not matter): Fly L-39 and tune to a RSBN channel. Both green lights are on, you are receiving localizer and glideslope information. - In Navigation mode, RMI is receiving localizer data only; "k" flag should be off. - In Penetration mode, you are still receiving that data and "K" flag is still on. Both instances are bugs as "K" flag should be off and not on. In PRMG/Landing mode, "K" flag is working correctly; Flag is off. If you have the Mig-21, you can see how this should properly work. Just repeat above step by tuning to a RSBN channel. ---- You were quite correct that I should have used better wording. Thank you for that. ---- Please note: I have a L-39 simpit. Radio Navigation in the L-39 or Mig-21 is the only reason I fly in DCS and I use it on every single flight. I may be the only person in the world that does this, so I notice things. :) Not surprised by all of this as it is just more of the same old, same old. People go out of their way to prevent bug fixes instead of helping to get them fixed. I rest my case.

I don't watch video's. When I get more time, I will look into this more. Thanks very much for the feedback.

Latest version of Open Beta L-39 has the following repeatable bug: "K" flag should be turning off whenever the RMI receives a localizer signal. It stays turned on during both Navigation mode (when receiving a signal) and Glidepath/Pentration mode. The SDU follows this also (though I do not use it). To repeat the bug, just fly the $#@ plane. ;) Please fix this.

I've had both setups and they can be similar in performance. I just use one 4k HDTV and a 1080 monitor for my gauges now. Three landscaped monitors is not a good setup, as you found with the distortion. I ran a PLP monitor setup for my Ka-50 pit. Actually ran pretty good, but I'll never do more than a single DCS display again (plus a gauge monitor).

You can do this in DCS or TIR software. Not in this forum. In DCS, click escape, adjust controls/axis commands and look at it. The answer is there. Just edit the curves.

Clear all the mapping to the control.

You can write it from scratch, like the pit builder pioneer's, or you can just plug and play with Arduinos and DCS_BIOS. Like Hans said, Helios work's too. If you are using a glass cockpit, you don't need any hardware, just Helios or Ikarus.

My theory: Spawning above ground is caused by QFE setting. Experiment with it when building a mission and you will see how it happens. Do not hold your breath for a fix.

For the record, depending on your hardware, Windows limit does not matter. HID controllers can have 128 buttons in DCS. I've seen them all in Helios also in the past. I've owned Epic cards for twenty five years. No, you don't want to pay for one.

Didn't take long... In your export script.. ...\DCS.openbeta\Scripts\DCS-ExportScript\ExportsModules\Mig-21Bis.lua You have commented out the line for RPM1 DCS_ID 50. Un-commenting it out allows both needles to work, but they then become inaccurate. Commenting it out again makes RPM needle 2 accurate again. Any chance you can learn more by looking at your data? Thanks very much. Hope it helps.

Thanks H-J-P, I'll see if I can learn anything about it. I know there are several other issue's with the exports of the M-21.

My first thought is "so what" :) Try seeing if that view is not enabled in preferences. If you have TRackIR make sure it is not blocking the keypress.

I've seen pneumatic function loss with a full tank of air. Is it tied to running engine below a minimum RPM? I was experimenting with going below 80% when it happened.

I forgot to add.. you must make sure the KPP gyro is in sync. Push the button for it on front panel.

I will probably start making a simpit for this great module... The Mig-21bis Ikarus file has only two bug's I can see for now. RPM needle 1 as noted above, And... "Mig21_ALT30", "DCS_ID" "655" baro pressure. Set's at the mission start, then does not operate after that. I think it may be set incorrect on the scale also, though the gauge altitude is correct. Thanks for everything.

Starting a mission in flight set's this function to on. Start from the ramp does not turn this function one (Mental note made). Seemingly, if landing gear are extended, low altitude lamp is disabled. I think this might be a bug as that lamp is quite helpful on an instrument approach. You set your decision height with it. Auto recovery mode is disabled when gear is down, but I don't think that should disable that lamp. If that is the way it is in real life... never mind.

Sorry for mix up's. If you are are departing from Lochini airfield (using user manual switch panels locations): 1. Set RH37 to "3-I" 2. On RH8, push channel 5 button. On RH8, push "Switch Channel" button. If you look at the left hand side of canopy rail, it will show you the map grid of the radio you are tuned to. "3-I-5" is the first NDB NW of Lochini. 3. Make sure the RSBN/ARC switch is down (default) position. Fly. Go up. Radio will start playing a morse code and KPP needle will point to station. To stop the Morse code, switch the RH10 switch to radio to stop it. Read the manual to learn more.

As a Pit-Builder I try to avoid this sort of thing, but I have fallen hard for the Mig-21 module after the latest update. I am getting a solid 60 fps in flight in the AO server and that is in 4k. The latest optimizations you made helped me a lot. It is very satisfying to be able to land PRMG and do it as well or even better then I could in the L-39. It took practice! The Mig-21bis is just a great module. I will probably start making cockpit parts for it and I'll need some issue's fix with data export. I will join the other bug-reporting forum when I do that. Thanks and Good Day,