Jump to content

JG14_Smil

Members
  • Posts

    2508
  • Joined

  • Last visited

Personal Information

  • Flight Simulators
    DCS
  • Location
    Indiana
  • Interests
    Sims, bicycles, golf
  • Website
    http://forums.eagle.ru/album.php?albumid=254

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks so much, guys, I've tried it all before. I'll just close the thread as nothing is going to change.
  2. World volume is only for externals. Turning up cockpit sounds makes the booms louder. Thanks for replying, MAX.
  3. 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.
  4. 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.
  5. 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
  6. 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.
  7. Great job. Inspiration for me to get building again. -smil-
  8. 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.
  9. 2.9.47168 Update has resolved the issue with RSBN reception.
  10. 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.
  11. 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.
  12. Hi, I have a L-39 simpit and I searched hard for that font with no luck. Hope you find it.
  13. 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.
  14. 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.
×
×
  • Create New...