FalcoGer

Many aircraft have a KY-58 or other crypto hardware on board. It would be really neat if turning those on or changing the settings would affect the crypto settings in SRS. Furthermore aircraft like the AH-64 have systems for time based frequency hopping on multiple radios, SINCGARS and other such features. For simplicity and realism the hopsets and encryption codes should be different between red and blue coalitions, even for the same aircraft type. It would also be really neat if special radio effects would be audible, for example due to the tiny clock differences between aircraft or radio hardware needing a small amount of time to tune to the next frequency. Or if encryption is used that people who don't have encryption hear static instead.

All modern aircraft use a hotas system where there are dozens or several dozens of key binds, quickly using up the buttons on the actual user's hardware. Furthermore there are plenty of users who use replica controllers that try to emulate the real hardware, where every single button is used for the correct function. Radio is one such important button. But VOIP and the regular AI interaction via the radio menu requires 2 different key bindings for ED's aircraft, creating problems for people running out of buttons. This gets progressively worse the more PTT controls you have. This has not been a problem with SRS since SRS allows users to bind their PTT button to the same button as the radio menu in game, and even have a delay option to not transmit every time you hit the button if you press it short enough. Personally I have set that delay to 200ms and it works fine. It's not perfect as every time you transmit you also open the radio menu, but at least you don't transmit every time you open the menu. Heatblur has come up with a solution that should be implemented with all DCS aircraft, namely allowing players to bind keys for the radio menu and the VOIP separately or using the same button press for both of them, with a short press being the radio menu and a long press being the VOIP. Implementing this will also help the SRS users as long presses on that button should no longer bring up the radio menu, even if the built in VOIP is not enabled on the server. The delay should be either configurable or documented somewhere clearly, maybe even directly in the description of the key bind (that is not on page 247 in some obscure manual that isn't even for a specific aircraft), and be the same across all aircraft, so users can configure SRS accordingly to match with the same delay settings. The delay should be very short, that is much shorter than 500ms as often used in aircraft with short/long press logic, maybe 250ms or even less, so that there isn't too much of a delay before the user can talk. Alternatively the user's voice gets recorded and buffered immediately upon button press and it is then discarded if the user released the button within the threshold, or transmitted with a short delay if he continued to hold it. It's probably sufficient if the user is made to wait a small fraction of a second before transmission though and much easier to implement.

What about the tracks? I pressed the empty buttons on the left on the autopaged engine page that would've been the FMC channels.

@Lord Vader were you able to reproduce the problem?

Just today I was in the apache and checked the UHF radio settings page again, and guard receiver was not barred out. I could just turn it on. But I don't know why, or why I couldn't before. When can I or can I not turn on the guard receiver?

I know that rotor start max windspeed is 45 knots. But what is the maximum wind speed for operations? I couldn't find any such limits anywhere. Surely you can't fly into hurricanes and such limits exist, right?

Squelch off was broken before, so you would only hear the static when someone was transmitting on any other radio. Now it is correct in that you get the noise by just turning it off. It's fixed, but annoying as any real helicopter crew would've had squelch on when they shut down their helicopter. The squelch state in the real aircraft is the same as it was on last shut down.

Did I say any different? *Edit: I see what you mean now. This was originally posted in wishlist, because, as I stated, it's not a bug per se. Thus the title reflected my wish, not the problem. Someone moved it to bug reports. I changed the title to be less confusing.

I think it also depends on the effort to fix. Something like this is a 5 second fix, including finding and opening the correct text file where the tooltip is stored whereas an autopilot behaving erratically might be more impactful, but might also take many hours to fix and test.

Sorry. Also thank you.

It should probably be more in line with Arma. I don't know the effects of explosives on trees, safe for that one clip of the nuclear test where they concreted a forest into the desert.

I guess that's true. I'm not a native english speaker.

When setting up the datalink, you can mark individual aircraft as either TEAM or PRI or both. What does each option do exactly? When I tried, I found that you can not send or request reports to members that weren't marked as PRI. But what else does PRI do? What does TEAM do or enable? And what do datalink members in your NET with neither option offer? Is there a reason to not just mark everyone as TEAM/PRI? Is it that PRI show up when you can select or deselect individual members, and TEAM get sent data when you send files through the COM page to all members? Is neither just a setting for you so can receive from them, but not send anything to them? What happens if one member added another to their NET, but the other member didn't add them? What if the PRI/TEAM configuration is mismatched?

The AH64-D's squelch circuits are in the position they were in after a shutdown. If the previous crew had squelch turned off, it will be off when the helicopter is started the next time. So squelch being off and you getting blasted by 5 radios angry static noise as soon as you switch the battery on is not a bug. Previously this was requested the squelch was broken, and it would only play white noise when someone was talking on any of the radios. With the squelch now working correctly it is as bad as it would be in real life. It is simply not realistic for a helicopter crew to turn off squelch for every single one of their radios, as squelch off is only used when a transmission is broken up when the transmission power does not reach a required minimum. Then squelch would be turned off to receive the transmission regardless of the power it is transmitted at. The default state for squelch is ON. Any crew turning all of the squelch circuits off would go insane and/or deaf from the white noise they'd get blasted with from every one of their radios, making this highly unrealistic. And that is what we get in DCS with the 2.9 update. You turn the key and your headphones explode with no way to prevent it. Please put more priority on making the default state to be squelch on as any real crew would have had it prior to shut down.

If the problem is not just showing in DCS but elsewhere, like in the windows axis position indicator, then it's not a DCS bug. I can't tell you what's wrong with your pedals. Ask TM.

To get on the same net as someone else you must have their datalink ID in your radio preset. manual frequencies don't work. If you want a custom frequency or want to start from scratch with datalink you need to do the following Go to COM Select a Preset (only preset 1-8 can use datalink) that you want to use Hit PRESET EDIT (optional) Name the preset and give it a callsign (what you call that preset). This need not be the same between datalink members, it doesn't even need to be the same preset index. You can change preset 1 to be ABC and your friend can change preset 6 to be DEF and it will still work as long as the rest is OK. Select the radio you want to use on the top. For example FM Enter the frequency. For example 34.55 for FM2 (on the right) Hit MODEM Make sure PROTOCOL is set to DATALINK, auto ack as desired (just set it to ON, since there is no detailed electronic warfare in DCS that would give away your position) Click NET Add all datalink members to that preset. There are multiple ways to do this. Yo u do not need to add yourself. Manual Click a spot that is free (the ?) Click C/S and enter a callsign, this does not need to match your friend's actual aircraft callsign as seen in his aircraft and is for your reference only. Click SUB and enter the datalink subscriber ID of your friend. The SUB button will not appear until a callsign is entered. It will also not appear if the PROTOCOL in MODEM is not set to DATALINK Member DIrectory Click MBR DIR Find your friend's callsign and/or aircraft description as per the mission editor Hit ADD or REPLACE, when REPLACE then select a slot for them to go into Optionally change the C/S to something that you can recognize better than what DCS put in there Set your friends as PRIMARY and TEAM Select IDM to be on the desired radio, in this case FM2, with the IDM switch on the EUFD Select the radio, in this case FM2 with RTS Hit the preset (P) button the EUFD Select the correct preset you programmed earlier with the WCA switch Hit the Enter button to the right of the preset button Your friend does the same thing with your info. Notes Check your callsign (C/S) and Subscriber ID in COM -> ORIG ID, your callsign is on L1, your ID on R1. Both are also found in the info box in the middle. Aircraft callsigns can have up to 5 letters or numbers. If you change it, other people's MBR DIR won't be updating. They would have to switch it in their NET configuration Aircraft callsigns that are longer than 3 characters will get truncated for IDM Subscriber Idents when receiving a position report. Aircraft callsigns need not match, the only thing important to match is the ID and the frequency. The aircraft callsign in the datalink member list is used for reference: When receiving position reports (truncated to 3 characters for the IDM Subscriber ident control measure) For received reports to indicate who sent them For the push button labels on the MFD when sending data to indicate who shall receive the data Only presets can have a net configuration. When entering a frequency manually, then the radio can not be used for datalink until a preset with a net configuration is reselected on it. Preset unit IDs (Names) are up to 8 characters long Preset call signs are up to 5 characters long

In the apache when editing a preset's NET, there is the member directory feature. How does the (real) apache know which other aircraft exist, what their callsign and datalink ID is? Is it just in the data cartridge? How many slots can there possibly be?

When having a human CPG, that adds datalink members twice when editing a preset's net and adding a member with the member directory function. To reproduce Join hot AH64 COM -> Preset 1 -> Net Delete members if any are present Select MBR DIR Select one and click ADD Deselect MBR DIR Check Members, there will be 1 in the first slot Delete the added member so it's blank again Have CPG join MBR DIR Select one and click ADD Deselect MBR DIR Check members, there will be 2 identical ones Sever track only. CPG did literally nothing but join. server-20231022-091207.trk

Since the 2.9 update, hitting COM -> MAN -> UFC Guard no longer turns on the guard receiver for the UHF radio and instead tunes the UHF primary to 243.0MHz and pushes the active frequency to standby. I'm not aware of any other method of turning on the UHF guard receiver (Indicated by the G symbol in the UHF row on the EUFD in the radio settings column). How do you enable it in this version of DCS? I was digging through the COM menu, then UHF, but guard receiver is barred out. Why? I liked being able to monitor guard with SRS.

The comms preset have this primary frequency thing in the mission editor and also in the preset editing it has the same settings. What is actually doing? You can set frequencies for all the radios in the preset even if it has a "Primary" radio set and you can select that preset for any radio on the EUFD and it will use the corresponding frequency of the preset. So I don't understand why you need this primary thing. All it seems to do is move this little arrow around (next to VHF in the box there) and make the radio selection box and radio mode white on the main comm page when you select a preset. Is it just visual?

Just tested it. Radio settings allow lower case letters and invalid letters to be entered. There also is no character limit in place

yes. it is perfectly smooth for me. it isn't a DCS bug if your hardware fails. try https://support.thrustmaster.com/en/ just to be sure, we're talking about these thrustmaster pedals, right?

I wanted to test if the wind indicator shows in yellow if the rotor RPM is < 50% Np and wind speeds are > 45kt. So I made a mission with some insane winds to also have a bit of fun. I would imagine that if the winds were above the maximum display value of 99kt, it would simply display 99, not calm. I don't know what's going on here. I thought it might be icing, but anti ice isn't implemented, so it would be a really dick move to simulate adverse ice effects like frozen ADSs and not allow us to deal with it. But the helicopter shows "CALM" in the wind. I take off to prove my point, and immediately get tossed around like a leaf. winds_are_calm.trk silly weather test.miz

You say thrustmaster pedals are not working in the bug reports. Of course me saying that my thrustmaster pedals ARE working is helping because it shows that the problem is not with the pedals themselves. mine are about 6 years old.

That's still a bug if the UI allows you to enter invalid characters. It is probably a good idea to filter the characters you can put into the text boxes, limit the text length to the maximum allowed in the aircraft, and also change them to upper case either as you type or as it's transferred to the aircraft. Remember to test edge cases such as no text input or copy+pasting text in there with invalid length and/or invalid characters.