fixed [FIXED] Easy comms, not comms at all?

[Stratos]

I'm using easy comms, but cannot communicate with anybody, it appears all greyed out and no one ever answers, any idea?

Edited October 20, 2022 by Vibora

[MAXsenna]

5 minutes ago, Stratos said:

I'm using easy comms, but cannot communicate with anybody, it appears all greyed out and no one ever answers, any idea?

Don't think easy comms is supported yet.

Personally, I think easy comms should be disabled in the game all together. Bu that's just me.  

[felixx75]

3 hours ago, MAXsenna said:

Personally, I think easy comms should be disabled in the game all together. Bu that's just me.

 

No, not just you 
(not to be taken too seriously)

[Flappie]

5 hours ago, Stratos said:

I'm using easy comms, but cannot communicate with anybody, it appears all greyed out and no one ever answers, any idea?

F1 radio comms are WIP. Easy comms will be implemented later.

[Zeagle]

There is absolutely no need for easy comms in my opinion. 

[Stratos]

14 hours ago, Flappie said:

F1 radio comms are WIP. Easy comms will be implemented later.

Thanks! Solved!

[tzui]

I need easy comms just for the MiG-15

[Dragon1-1]

MiG-15 should work with complex comms as long as the radio is configured properly in the mission. 

[Ramsay]

On 8/19/2022 at 10:39 PM, Zeagle said:

There is absolutely no need for easy comms in my opinion. 

IIRC there are a number of servers that force "easy coms" on players - it's not a major issue for modules that support "easy coms" as it often just requires an additional button/key binding.

But for EA\WIP modules that don't support "easy coms" i.e. Yak-52; it can restrict a modules inclusion in a server's slots.

IMHO as "easy coms" is supported by 95% of modules, is an FC3 default and helps newbies get flying without needing to learn their radios - backwards  compatibility should be a high priority to any dev and added shortly after EA release.

[XCNuse]

On 8/19/2022 at 5:39 PM, Zeagle said:

There is absolutely no need for easy comms in my opinion. 

Assuming the mission creator sets up ALL comms correctly for each and every aircraft... sure.

 

But as it stands, even in the ME, each aircraft even within the same groups can have different presets, which adds a lot of work for mission editors to double check these things; and in mass multiplayer missions, this is essentially several hours of work.

And no easy comms in preset-only aircraft spells disaster.

 

Personally I'm surprised this is even something third party devs had to deal with; I was under the impression this was a core feature of DCS.

[MAXsenna]

3 hours ago, Ramsay said:

IMHO as "easy coms" is supported by 95% of modules, is an FC3 default and helps newbies get flying without needing to learn their radios - backwards  compatibility should be a high priority to any dev and added shortly after EA release.

 

3 hours ago, XCNuse said:

But as it stands, even in the ME, each aircraft even within the same groups can have different presets, which adds a lot of work for mission editors to double check these things; and in mass multiplayer missions, this is essentially several hours of work.

While I somewhat do agree with both statements, I see your points. But if we got rid of easy comms, users would be forced to get some knowledge of how radios actually works. (Sorely needed in basic training missions for most modules. Kudos to Aviodev/C-101). Users would then have a better understanding of SRS/VoIP. Yes, mission designers might have some extra work, but it would be benefitial in the long run. Now, if the ME had a "Radio tool" of some sorts, where one could apply frequencies easily to both sides, and save those settings in an easy way for future use. We would come a long way. Now it's just too easy to just skip this. 

A certain other sim has a clear approach to this.

EDIT: Of mission designers would add kneeboards to the mission with correct frequencies, and/or the kneeboard could be auto populated. That would also be nice. 

Edited August 22, 2022 by MAXsenna

[XCNuse]

The answer once again falls into more along the lines of data cartridges and users being able to better prebrief and set up their aircraft.

 

The reliance right now stands on the mission editor to setting everything up correct on these jets that don't have programmable radios. There's just no way around it unfortunately. Thus, knowledge isn't always the issue; but lack of inability to fix the problem by the user.

 

That said, all of this comes a bit down to uniqueness of modules and DCS as a whole, and lack of global settings that.... should or could be global.

For example; the A10C/ii doesn't even have radio presets in the ME.... why?

 

Either way I think you see a bit of the issue at hand; which is, it isn't always the end-users' fault, but the situation they're put into.

a DTC system or better briefing capability before loading into your jet is [IMO] the solution.

[MAXsenna]

@XCNuse

Oh, I do! Didn't mean to fault the user, just sayin' the way it works now, it teaches bad habits.

And, yes common settings throughout all modules and "DTC" even for old aircraft.  

 

[Zeagle]

15 hours ago, XCNuse said:

The answer once again falls into more along the lines of data cartridges and users being able to better prebrief and set up their aircraft.

 

The reliance right now stands on the mission editor to setting everything up correct on these jets that don't have programmable radios. There's just no way around it unfortunately. Thus, knowledge isn't always the issue; but lack of inability to fix the problem by the user.

 

That said, all of this comes a bit down to uniqueness of modules and DCS as a whole, and lack of global settings that.... should or could be global.

For example; the A10C/ii doesn't even have radio presets in the ME.... why?

 

Either way I think you see a bit of the issue at hand; which is, it isn't always the end-users' fault, but the situation they're put into.

a DTC system or better briefing capability before loading into your jet is [IMO] the solution.

That's not true. Presets are not required except on some very few older aircraft that are not always present in every scenario. I have made missions where I put in a ton of presets for each flight and put all that info in the briefing. I still do that. But that is part of mission making. It's not a chore. It's just part of the process and not a problem at all.

As far as the A10 not having presets, I say who cares? In real life presets are used mainly by squadrons for local everyday freqs such as approach control, tower, the range, etc. Most other freqs are simply dialed in. Presets are something to simplify the task at hand when time is critical, like on an approach. But they are not required. It amazes me how gamers thing it's such a chore to pre-brief a freq and dial it in by hand. A kneeboard is a good idea..and I don't mean the one on screen. You need to brief your flight. That includes frequencies.

On my server, if a pilot cannot be bothered to dial in a freq when necessary, all by himself, then I don't want him there.  If his aircraft requires presets then he will have them. But I expect a basic level of airmanship and equipment familiarity. 

[Flappie]

Easy comms were implemented in today's OB update.