JG14_Smil

Thanks so much, guys, I've tried it all before. I'll just close the thread as nothing is going to change.

World volume is only for externals. Turning up cockpit sounds makes the booms louder. Thanks for replying, MAX.

Hello, The DCS sound system is not very enjoyable for me. In every plane, in order to hear my own engine, I have to raise the volume. I am now at the mercy of every pilot that wants to make a sonic boom, so I have to turn the volume back down until I can't hear my engine again. Same thing with wind noise, it becomes deafening if I set volume so I can hear my engine. I've tried every volume slider setting possible and I cannot make it right. In settings, we are given an option to 'opt out' of loud afterburner sounds. Can we do the same for sonic booms? I don't need them at all. In fact, I would invite the Dev or Devs that created that sound to just sit in a public server and listen to it for a while, just so they know the joys they brought to DCS (sarcasm, yes). Thanks for consideration.

Thank you DrPhibes, that is great to learn. I found that frequency on an incorrect chart then. Actual sectionals are hard to find. I wanted to note that the F10 field data still lists the ILS in reverse to the runways. F10 data lists 111.1 as 13, but I had to use 111.1 to land runway 31.

Hello, I recently found an online server running the Persian Gulf with weather. I learned the Al Dhafra ILS were not working correctly and I took a look at the beacons.lua. There were some frequency mix-ups that took a while to pin down, but I sorted them out and have the ILS pointing the right directions to the correct runways. I could not find reliable morse code ID information, so I cannot confirm them as correct after the changes. I did try replacing the extra 108.7 frequency with the correct frequency of 114.9 for 31L that I found online, but while I received an I.D. signal, it did not work correctly as an ILS (maybe a conflict with a VOR somewhere?). I was hoping it would help you get things working correctly, so I added it to a zip file. I added comments of the lines I edited. Nothing fishy, I just moved numbers to the proper locations. Just wonderful flying the map at night with working IFR. Before my edits, the plane would just start to circle instead of entering the ILS (at Al Dhafra). smil Persian_Gulf_Beacons_fix.zip

Hello, I wanted to report that update 2.9.1.48111 has fixed the mirror issue with the F1 EE for me. I note the F1 BE still has no working formation beacon. Is this a known issue? I did try looking. Thanks.

Great job. Inspiration for me to get building again. -smil-

2.947168 Update has stopped the Kutaisi marker beacon lamp while on runway issue for me, Vlad. Give it a test and hopefully you can mark this issue as solved.

2.9.47168 Update has resolved the issue with RSBN reception.

Just wanted to note that I could make the Marker beacon work correctly again after subtracting a bit of altitude from the beacon position in the Beacons.lua. After doing so, the marker detection range is decreased and the lamp and buzzer only activate while flying over the beacon, and not while on the runway at Kutaisi, as it did in 2.8. The marker bug is both online and offline and probably a new terrain mesh thing.

Since 2.9, while flying online, RSBN detection range is limited to under 25km, usually closer to 20km. This happens with the default Beacons.lua file, as well as with added beacons from a modified beacons.lua. Offline L-39 RSBN use is not affected and works as it always has. I have not tested PRMG as the RSBN is needed to get into the right position to use the PRMG. To reproduce bug, simply join an online dedicated server and fly the L-39 using RSBN navigation. You must be 20-25km (instead of over 100+km) from the beacon for reception. You can make the signal go in and out by flying in and out of that distance. This worked correctly in 2.8 and still works fine in 2.9 offline mode. There is no sense in my having a L-39 simpit if it will no longer work correctly online. Please look into it. I am probably one of the very few people in the world that still actually uses RSBN/PRMG in the L-39.

Hi, I have a L-39 simpit and I searched hard for that font with no luck. Hope you find it.

Hello, I too am seeing anomalies from Marker beacons and RSBN beacons since the 2.9 update. I note the activation range of the marker beacon for Kutaisi is about 1.25 KM per radius, and it triggers the lamp and buzzer while on the runway. I believe that is similar to the OP report. After 2.9 update, while flying online, my maximum range for RSBN reception is only 20-25KM. That did not happen in 2.8x. My offline 2.9 testing shows no trouble with RSBN reception, either, only while online.

Hi, have you tried deleting your metashaders and FXO files? They are located in the saved games folders. DCS will rebuild them (after a longer than normal wait) and this has sometimes helped fix issues like you described.

Thanks very much for this.

Sorry for reopening this old post. "The frequency of the AFN-2 can be adjusted in the Mission Editor to any desired ILS beacon. By default it is set to 38 MHz." Is this feature like the Mig-15 gun camera, which only works in offline mode? (Please confirm this, yes or no). As I only fly online, I did some experimenting with changing the frequency of an ILS in my beacons.lua: Any attempt to set an ILS or PRMG localizer to 38 or 380 produced no results from the AFN-2. After looking into the Mission Editor frequency defaults, I see it uses "124.0" instead. Setting an ILS to "124000000.000000" again produces no results but setting a PRMG to "124000000.000000" makes the AFN-2 range needle work properly. The vertical AFN-2 needle only twitches and is not usable for navigation in any way. Again, is this an offline only feature, and if so, does it actually work? I can't be the only one to have done these tests. Thanks, and best wishes,

Allow me... "direction = 161.568576;" it should be: "direction = 75.800005;" You seem to offset ILS Localizer's 2 degrees to match your approach plates, which is just wrong. Based on other DCS maps, Approach plates should give magnetic headings, not true headings, and if your Approach plates are correct, then every one of your field runways if off by 2 degrees. You can prove this with the F10 map and ruler feature, which give magnetic/true heading readouts. ILS Localizers are supposed to be lined up with true runway heading (as seen in Mission Editor).

Hi Bailey and thanks for your help. If you don't update profiles here, just use the L-39C.lua file. I am attaching "L39IkarusScripts.zip". It contains the updated export script in the "DCS-Export Script" folder. Updates to this file include addition of one rear gauge export call for the L39 rear seat EGT gauge and a change to math for the rear seat Command Course needle, which would work in reverse, and now works correctly. All other fixes to gauges are profile related and I have included these profiles in their respective folders. There are quite a few gauge fixes here. Unzip these to the main Ikarus folder structure. Ikarus has a drawback in that you cannot rename profiles. To switch between profiles for the same module, you have to copy/paste the version you want from their folder to the main "Ikarus-master/Ikarus/L-39C.ikarus" file and choose "over-write". You can Alt-Tab out of DCS at any time to do this if you switch seats in the L-39. Choose the version you want from the folder, right click and select copy. You then paste this into the "Ikarus-master/Ikarus/L-39C.Ikarus" file. Be sure to back this file up first if you have a saved profile. These profiles will display a L-39 gauge set on at 1920x1200 secondary monitor (multi-monitor setup) with a 4K monitor as primary DCS display. My Ikarus profiles start at "X-3840, Y-0" starting point. You may have to edit these numbers to match your multi-monitor setup. Profile can be edited for 1920x1080. The gauges are in their normal position, nominally life-sized, and there are additional gauges located from the right, left and center panels and radio frequencies/channels around the edges. No lights or annunciators are included, only gauges. Everything works expept rear seat gauges that are inoperable within DCS. I am probably the only person around using these profiles, but I thought I would share them just in case. Cary - smil L39IkarusScripts.zip

Thanks very much George, Sorry I missed your question Coupon4Coffin. I have beacon files for all the present-day maps. I have kneeboards for the Caucuses (Kneeboard Builder app required). Send a PM if I can help with anything. Please note: Beacon files don't fail the IC check, don't add scenery objects, or anything bad other than hard to read numbers within the Mision Editor. They make flying the L-39 very fun if you like radio navigation. Cary - smil

Hello, I have been doing a lot of work on the L-39 Ikarus profiles and also updated the export script to include a missing item or two. I have almost all gauge outputs working for Metric, Imperial and rear seat gauges. If you have a minute and can tell me what I should do to get it shared, I'll do it ASAP when all is ready. Thank you and best wishes, Cary -smil-

Hello, I use Ikarus to run my pit gauges and I was having a terrible time with the gauges stopping while in flight. Alt-tabbing out of DCS to restart them could be tricky at times. I tried everything I could think of for a fix with no luck before finally finding the answer and I thought I would share it here in case any others were having the same problem. In my Nvidia Control Panel, there is a setting for "Background Application Max Framerate". I simply set it to match my DCS Max FPS, both are set to 30 FPS, and I have never had my gauges stop working since. DCS is also much smoother than before with a lot of lags removed as a bonus. It made my day fixing this and I hope it helps. Cary - smil

Ahh Thank you, I did take a quick look to see if it was posted already but missed it.

Thank you, Minsky. Good to know.

Hello, In the beacons.lua file for Syria map, BeaconID 41_1, BEACON_TYPE_DME, has a frequency of "0.000000". The airfield is also missing the lines for an ILS Glideslope in the beacons.lua, just like the Arcan airfield. Just reporting some errors that I come across,

Hello, Ercan airfield is missing the ILS glideslope. BeaconID "49_2" is missing and should contain lines for the glideslope (in the beacons.lua).