Search the Community
Showing results for tags 'communication'.
-
Anyone having issues getting the coms menu to open while on the ground in the Spitfire?
-
Half the dialogue in Mission 9 cant be heard because overlord base comms isnt muted, so when the scripted dialogue plays you cant hear it, as overlords giving constant updates !!
- 5 replies
-
- radio
- baltic dragon
-
(and 4 more)
Tagged with:
-
I noticed how easy it is to interact with Jester you just 1 button and then just move your head. I think it would be nice to be able to to use comms menu in a similar way. Could be a option in special settings.
-
I found this on the forums to check the value of the VHF radio is set to a specific value, apparently this was for the Mi-8. I'm trying to check the same thing in the F-16 now, but I can't get it to trigger. I've tried entering values an int (127), a float (127.00) or string versions of those ('127.00'), but nothing seems to work. Are the cockpit parameter names different per plane? And if so, how can you check which ones are actually used?
-
Alright so this is what the mission says to tune into Frequencies: AOC: Col. (Overlord): 253.3 UHF Dodge 1 (Your flight, 2 A10s): 35.5 FM Prowler 1 (US convoy): 144.3 AM Guard Channel: 121.5 AM and this is what i did , in the picture does this look correct. I never got the Prowler guy to call me on the radio. This shouldnt be so confusing but it would be nice to hear them to know im doing it correctly. Im new to the A-10 so i dont know or trust what im doing yet so any help would be nice
-
This is not a wish for a new map or terrain. This is a wish for how old maps and terrains are handled. With the December 17 patch, I noticed a number of mentions in the changelog related to added TACAN stations and one airfield getting ATC frequencies it didn't have before. So I sighed and went back to check what these were so I could update my kneeboards with the new information, except, to my horror, I quickly realised that the changelog was… not wrong, as such, but woefully missing in detail. A large number of ATC frequencies have changed, mostly (but not exclusively) in the UHF band. This means that pretty much all the missions I have made on the Persian Gulf map now are broken, and I need to go in and 1) figure out exactly what frequencies changed to what, 2) redraw a large number of kneeboard images listing those (now incorrect) frequencies, 3) change the frequencies on several hundreds of individual aircraft across all those missions. The vast majority of aircraft in DCS have some kind of radio presets. Some aircraft only have presets, and they can't be changed in flight. This means that every time you move a fixed frequency up by 0.05MHz, missions break with those aircraft. They can no longer talk to the ATC, and while that may be a small detail on the scale of things, the same holds true for when you add/remove/change NDBs and TACANs and similar nav aids: suddenly a mission that relies on those aids to get the player to where they need to be no longer exist; the player can't navigate; the mission is broken. This is not to say that you shouldn't fix things that are obviously wrong, but it does mean that you need to be exceedingly clear about what you change when you alter something hard-coded into the map because every time you do that, any mission that is based off of that map runs a significant chance of no longer working as intended. These changes need to listed — in full — in the patch notes so that mission-makers can go in and do some bulk search-and-replace in the lua files (and make new images and mods and plugins to reflect the new reality). You need to specify that Al Bateen has changed from 250.550MHz to 250.600MHz, and every tiny such change needs to be included. It gets very annoying very fast when you have to check on every airport, every beacon, and every unit included in the mission to make sure they all still match up.
- 2 replies
-
- 4
-
- gamebreaking
- patch notes
-
(and 1 more)
Tagged with: