Finally! I've checked again and all commands AFTER Clearance delivery request work OK!

Now what is wrong with C&D?

Thanks,

Edited December 22, 20178 yr by Dirk98

Just now, Dirk98 said:

Finally! I've checked again and all commands AFTER Clearance delivery request work OK!

Now what is wrong with C&D?

Thanks,

I've done a quick test and it appears the grammar file for RC4 needs tweaking.

Somehow "Delivery Speedbird XXX requesting ATC clearance to XXX" (which is a perfectly valid ,message) is mis-interprered.

Try other forms like

"Delivery Speedbird XXX is ready to copy ATC"

"Delivery Speedbird XXX is ready to copy"

Will post replacement grammar as soon as possible. File to replace in \Multi Crew Experience\CandC\ folder

 

1 minute ago, FS++ said:

I've done a quick test and it appears the grammar file for RC4 needs tweaking.

Somehow "Delivery Speedbird XXX requesting ATC clearance to XXX" (which is a perfectly valid ,message) is mis-interprered.

Try other forms like

"Delivery Speedbird XXX is ready to copy ATC"

"Delivery Speedbird XXX is ready to copy"

Will post replacement grammar as soon as possible. File to replace in \Multi Crew Experience\CandC\ folder

 

Can't wait for the fix file, and still I'll need to check out all other commands, because I meant I could finally get  to the hold short and I haven't tested afterwards.

 

Thanks,

3 minutes ago, FS++ said:

 

Will post replacement grammar as soon as possible. File to replace in \Multi Crew Experience\CandC\ folder

 

Where will you post it?

Thanks,

Just now, Dirk98 said:

Where will you post it?

Thanks,

In this same thread, hopefully tomorrow.

2 hours ago, FS++ said:

Try other forms like

"Delivery Speedbird XXX is ready to copy ATC"

"Delivery Speedbird XXX is ready to copy"

Don't work neither...

Just now, Dirk98 said:

Don't work neither...

This assumes the callsign is "Speedbird XXX".

The grammar is dynamically updated to expect a particular airline name, as read from "rcv3,dat"

24 minutes ago, FS++ said:

This assumes the callsign is "Speedbird XXX".

The grammar is dynamically updated to expect a particular airline name, as read from "rcv3,dat"

This is clear but not helpful - still can't get clearance delivery, something is broken 

1 hour ago, Dirk98 said:

Where will you post it?

Thanks,

Please download this file

Unzip and replace "vRC4.cfg" file in \Multi Crew Experience\CandC\ folder.

This one is optimized for airliners, with callsigns such as "KLM 234 heavy", "Speedbird 123" etc..

If you notice improvements, will get the other grammar for GA aircraft updated as well.

 

 

Gerald, something must be fundamentally broken. Communication with RC4 ATC just doesn't work, please try it yourself and see. RC4 is installed locally. Or is it perhaps because I'm using it with FSL A320X? I can see in the red text that comes up periodically, that FO is still looking for something on the FCU (if I'm right). Perhaps I should turn off Real Cockpit Crew Coordination and try without it?

 

 

 

Edited December 26, 20178 yr by Dirk98

FO officer says the call sign is not recognized when I contact RC4 Delivery, even though he confirms our call sign correctly. I tried Speed bird 54 also 0454 and 447.

"Please include the proper call sign" 

"I think the call sign is somewhat missing in your message"

This is when I'm in FSL A320X, the callsign is set in RC4/General.

Thanks, 

PS: But not the case in Mooney N327 for example!

Edited December 26, 20178 yr by Dirk98

How to stop FO internally looking something on the FCU? Always been like that with FSL A320X in P3Dv3 as well. I think it's something that you should fix..

Thanks,

1 hour ago, Dirk98 said:

FO officer says the call sign is not recognized when I contact RC4 Delivery, even though he confirms our call sign correctly. I tried Speed bird 54 also 0454 and 447.

"Please include the proper call sign" 

"I think the call sign is somewhat missing in your message"

This is when I'm in FSL A320X, the callsign is set in RC4/General.

Thanks, 

PS: But not the case in Mooney N327 for example!

It can happen when you enable option "Accurate call-sign required" in <ATC> tab.

If your callsign is "Speedbird 2361" and the speech reco picks up the wrong  digits sequence, say "speedbird 2316" or "Speedbird 3261", Fo will tell you that it wasn't right and MCE will intentionally reject your transmission.

 

 

1 hour ago, Dirk98 said:

How to stop FO internally looking something on the FCU? Always been like that with FSL A320X in P3Dv3 as well. I think it's something that you should fix..

Thanks,

Please read this thread in order to understand why it is the case by design until an SDK is available for that aircraft.

If you don't want the Fo to touch the FCU, you cdan disable that behavior as follows.

 

Go to \Prepar3D v4\MCE dlls\ folder and open "mcfslA3X.ini" config.

 

Add this line to the [OPTIONS] section

FCUsupport=0

It is enabled by default.

Fo will then still be able to pull, push and select modes, but won't be able to dial heading, alt, VS or speed.

 

13 minutes ago, FS++ said:

It can happen when you enable option "Accurate call-sign required" in <ATC> tab.

If your callsign is "Speedbird 2361" and the speech reco picks up the wrong  digits sequence, say "speedbird 2316" or "Speedbird 3261", Fo will tell you that it wasn't right and MCE will intentionally reject your transmission.

 

 

The problem is when I press Del button and start trying to communicate with RC4 ATC, that's when FO says something's wrong with the call sign. I'll try to disable Accurate call-sign, first.