FBW A320NX project topics

[FS++ 707]

8 hours ago, danbaz said:

center instrument panel engine warning and systems displays	ecam press take off config	not simulated
center instrument panel engine warning and systems displays	ecam show electricity	not simulated
center instrument panel engine warning and systems displays	ecam display wheel	not simulated

 

Kind regards,

Daniel

 

Good to hear you like the full integration.

You could use these commands instead.

"ecam show electrical" or "ecam display electrical"

"ecam show wheels" or "ecam display gear"

"check takeoff configuation" or "check takeoff config", "verify takeoff config", "test takeoff config"

 

[danbaz 5]

Hello Gerald,

Thanks for these. These 3 worked. 

Today I have checked three more panels. To limit the list I will copy only the items with issues.

Note: I am listing them here, not to complain or anything, but to help get it fixed and to learn. This takes quite some time. If you have overviews of what works and what not and accepted verbiage for the knobs, then pls could you provide that to me? Would make my life a lot easier. I do not mind if some is just not ready or even not planned. I just want to know what I can expect to work and what not and the needed verbiage. 😎

Kind regards,

Daniel

Panel	Commands	Result
center instrument panel clocks	start timing	bottom clock: does reset, then stop position
center instrument panel clocks	stop timing	bottom clock: does start the timing
center instrument panel clocks	reset timing	bottom clock: not simulated
center instrument panel clocks	start center chronometer	upper clock: not simulated
center instrument panel clocks	stop center chronometer	upper clock: not simulated
center instrument panel clocks	reset center chronometer	upper clock: not simulated
glareshield captain efis control panel	set barometric reference to qnh	not simulated
glareshield captain efis control panel	set barometric reference to hpa	not simulated
glareshield captain efis control panel	set altimeter to current applicable	not simulated
glareshield captain efis control panel	Push altimeter knob	not simulated
glareshield captain efis control panel	Pull altimeter knob	not simulated
glareshield captain efis control panel	set standard altimeter	not simulated
glareshield captain efis control panel	ils on	Accepted, but does not do anything
glareshield captain efis control panel	ils off	Accepted, but does not do anything
glareshield captain efis control panel	efis show constraints	Accepted, but does not do anything
glareshield captain efis control panel	efis hide constraints	Accepted, but does not do anything
glareshield captain efis control panel	efis show vor	Accepted, but does not do anything
glareshield captain efis control panel	efis hide vor	Accepted, but does not do anything
glareshield captain efis control panel	efis show waypoints	Accepted, but does not do anything
glareshield captain efis control panel	efis hide waypoints	Accepted, but does not do anything
glareshield captain efis control panel	efis show ndb	Accepted, but does not do anything
glareshield captain efis control panel	efis hide ndb	Accepted, but does not do anything
glareshield captain efis control panel	efis show airports	Accepted, but does not do anything
glareshield captain efis control panel	efis hide airports	Accepted, but does not do anything
glareshield captain efis control panel	nav selector one off	Accepted, but does not do anything
glareshield captain efis control panel	nav selector one to adf	Accepted, but does not do anything
glareshield captain efis control panel	nav selector one to vor	Accepted, but does not do anything
glareshield captain efis control panel	navigation selector two turn off	Accepted, but does not do anything
glareshield captain efis control panel	navigation selector two set to adf	Accepted, but does not do anything
glareshield captain efis control panel	nav selector two switch to vor	Accepted, but does not do anything

[FS++ 707]

2 hours ago, danbaz said:

Hello Gerald,

Thanks for these. These 3 worked. 

Today I have checked three more panels. To limit the list I will copy only the items with issues.

Note: I am listing them here, not to complain or anything, but to help get it fixed and to learn. This takes quite some time. If you have overviews of what works and what not and accepted verbiage for the knobs, then pls could you provide that to me? Would make my life a lot easier. I do not mind if some is just not ready or even not planned. I just want to know what I can expect to work and what not and the needed verbiage. 😎

Kind regards,

Daniel

Panel	Commands	Result
center instrument panel clocks	start timing	bottom clock: does reset, then stop position
center instrument panel clocks	stop timing	bottom clock: does start the timing
center instrument panel clocks	reset timing	bottom clock: not simulated
center instrument panel clocks	start center chronometer	upper clock: not simulated
center instrument panel clocks	stop center chronometer	upper clock: not simulated
center instrument panel clocks	reset center chronometer	upper clock: not simulated
glareshield captain efis control panel	set barometric reference to qnh	not simulated
glareshield captain efis control panel	set barometric reference to hpa	not simulated
glareshield captain efis control panel	set altimeter to current applicable	not simulated
glareshield captain efis control panel	Push altimeter knob	not simulated
glareshield captain efis control panel	Pull altimeter knob	not simulated
glareshield captain efis control panel	set standard altimeter	not simulated
glareshield captain efis control panel	ils on	Accepted, but does not do anything
glareshield captain efis control panel	ils off	Accepted, but does not do anything
glareshield captain efis control panel	efis show constraints	Accepted, but does not do anything
glareshield captain efis control panel	efis hide constraints	Accepted, but does not do anything
glareshield captain efis control panel	efis show vor	Accepted, but does not do anything
glareshield captain efis control panel	efis hide vor	Accepted, but does not do anything
glareshield captain efis control panel	efis show waypoints	Accepted, but does not do anything
glareshield captain efis control panel	efis hide waypoints	Accepted, but does not do anything
glareshield captain efis control panel	efis show ndb	Accepted, but does not do anything
glareshield captain efis control panel	efis hide ndb	Accepted, but does not do anything
glareshield captain efis control panel	efis show airports	Accepted, but does not do anything
glareshield captain efis control panel	efis hide airports	Accepted, but does not do anything
glareshield captain efis control panel	nav selector one off	Accepted, but does not do anything
glareshield captain efis control panel	nav selector one to adf	Accepted, but does not do anything
glareshield captain efis control panel	nav selector one to vor	Accepted, but does not do anything
glareshield captain efis control panel	navigation selector two turn off	Accepted, but does not do anything
glareshield captain efis control panel	navigation selector two set to adf	Accepted, but does not do anything
glareshield captain efis control panel	nav selector two switch to vor	Accepted, but does not do anything

No worries, you can report anything you like.

If one thing, that will make people aware of the tens of thousands of built-in speech commands that very few even know exist.

Combined with the speech simulator that Voxscript is, one can even build flows for emergency procedures too, Just a matter of putting speech commands in the right sequence (as per SOPs in QRH) for FO to execute, and all triggered with a custom speech command so you won't even need to memorize it..

Clock adjustment was overlooked a bit. Neeeds fine tuning.

Although all chronometers could technically be controlled, we only bother with the one on Captain side ND, and the speech commands are "start chronometer", "stop chronometer" and "reset chronometer"

Efis control commands should all work.

You can even get the FO side EFIS going, using speech commands prefixed with "your" OR  "your side"

The Baro commands you listed don't exist as such. You could use "altimeter standard", "altimeter to qnh", "pull std" or other variations.

Now, if you remember the "aliasing capability" of Voxscript, you can use those speech commands you listed (as they come to you natually), and tie them to built-in commands so that when you say "pull altimeter knob" it would be as if you said "pull standard".

We'll probably just add your speech command to the speech grammar, as it sounds intuitive and should really be there already. But you get the point.

ILS ON, ILS OFF aren't in the grammar. I guess they ought to be. You could use any of these

my landing system on/off

my side ls on/off

your landing system switch on/off

your side ls turn on/off

both landing systems on/off

...many other variations to list here

 

For smooth operation I suggest the following.

If FlyByWire is your peferred plane, ensure it is always the one MSFS starts with.

Load aircraft, and wait until it's ready to fly.

Give it a minute to settle.

Only then start MCE.

Eventually, if some switches cannot be controlled for some reason, restart MCE.

In extreme cases, may need to reload the plane.

One thing we don't recommend, is switching from say CRJ to FlyBywire or vice versa.

If Aerosoft CRJ is your preferred plane, ensure it is the one MSFS loads on startup.

Confirm EFIS switches control working.

Edited May 8, 2021 by FS++

[danbaz 5]

Hi Gerald,

Thanks for the feedback. I will continue to report as I go through them all.

Just a note so that we are on the same page: when I add 'accepted, but does not do anything' this means that the FO responded as if he was going to do the action, but he could not. These commands did not trigger the 'MCE does not recognize this command' message.

Clock on center instr pnl: for the bottom clock, pls note the commands did the opposite action. The reset is not spring-loaded (perhaps it should be) but a setting, so perhaps make the reset a separate selection option.

for the upper: made a note that this one is not planned to be integrated

altimeter: "altimeter to qnh" was not accepted by MCE, the others were. Ultimately, I would be looking for Airbus standard call-outs, but I did not check for that at this point.

LS: "ils off" and "ils on" actually are accepted by the FO, but he does not push the button. (I use Mike16 for voice)

Tried all above EFIS commands again, but they had the same result (accepted, but no action).

PS: For the UI, for VOX script, for the VoxScript input field, would it be much work to make paste into that field work and/or place the cursor anywhere in the text, so that the whole command does not have the typed again if you had a typo in the first word? 😀

Have a nice evening,

Daniel

[FS++ 707]

6 minutes ago, danbaz said:

PS: For the UI, for VOX script, for the VoxScript input field, would it be much work to make paste into that field work and/or place the cursor anywhere in the text, so that the whole command does not have the typed again if you had a typo in the first word? 😀

Have a nice evening,

Daniel

Good idea for consideration. Should be doable.

You may have files out of sync, having used patches earlier.

I suggest you un-install previous version, then download and install the very latest

[danbaz 5]

Today I have tried to do a complete and full uninstall and re-install of MCE.

What I have done: Pls let me know if I had missed a step.

• Copied license key file and flows to keep to a safe place 
• Removed the app through windows app remover
• Deleted MCE directory and all files from normal program location
• Deleted MCE directory in appdata\roaming\
• Deleted MCE directory in documents
• Restarted computer

In app data I came across a log file that said not all Hvars were accounted for. Perhaps this was the problem?

Then I re-downloaded the latest version from the website - version 2.9.17 - and installed as administrator and ran the wizard, but skipped voice training as not required.

Then I started FS2020, loaded FWB A320NX at EHRD and waited for at least a minute before I did launch MCE.

MCE started normally. Of course I needed to redo a few settings. Keeping Clive for now for testing. One problem: no voxscripts were copied to the documents folder. I know where to find them, but this seems like a flaw in the installation process or there is another log/ini file somewhere that I should have deleted and I did not know about. I have copied all scripts from the installation folders manually.

Checked the log file again, but still it shows the message that not all HVARS are accounted for.

I now exited out of MCE to re-run to make sure the missing scripts did not cause the hvar error message.

That seems ot have done the trick. No hvar error this time. I will now re-check all the flows done before and will report in a separate message.

Logfile seems clean now:

Logging started
Simco64_Ldr loading
Created Simconnect session
CreatedSimconnect data definitions
Mapped Simconnect Events
About to enter main loop
Created Simconnect LVars definitions
Hvars received
Hvars received
Lvars received
Lvars received
Lvars received
Lvars received
Lvars received
Retrieved all relevant FlyByWire Lvars
Retrieved all relevant FlyByWire Hvars

Kind regards,

Daniel

[danbaz 5]

Happy to report much more is working now 😀

ECAMS - as before - no change

Center instr panel - clocks - same as before

Center instr panel - landing gear panel: all work, but autobrake wired incorrectly - see below

Panel	Commands	Result
center instrument panel landing gear panel	brake fan on	OK
center instrument panel landing gear panel	brake fan off	OK
center instrument panel landing gear panel	auto brake low	Set autobrake to medium!
center instrument panel landing gear panel	auto brake medium	Set autobrake to maximum!
center instrument panel landing gear panel	auto brake maximum	Switched off auto brake, nothing on 2nd try
center instrument panel landing gear panel	auto brake off	Set autobrake to low!
center instrument panel landing gear panel	anti skid on	OK
center instrument panel landing gear panel	anti skid off	OK

Glareshield - captain chronometer - All Ok as before

Glareshield - captain EFIS: All OK now except for the altimeter knobs. Also what is text command to set altimeter to three zero one two (or any variation)? Setting standard is the only action I got to work for this knob.

Few months ago I installed flows for the NEO from David. He introduced Dieter. After my reinstall I still have him onboard! how did he manage to do that? Also the FO asks for the ramp without me asking for that. I think I had to copy some xml file. Is this file causing some of my problems? Will find the installation instructions for that one now and see..    EDIT: Think this is default MCE behaviour as everything changed by the named flows was deleted at uninstall. IfThen, how can I stop Dieter to introduce himself in the cockpit? We already met in the crewroom. 😎  Also no need to ask for the ramp. It will come and go away within a few minutes anyway.

Kind regards,

Daniel

 

 

 

 

 

 

Edited May 9, 2021 by danbaz

[FS++ 707]

49 minutes ago, danbaz said:

Today I have tried to do a complete and full uninstall and re-install of MCE.

What I have done: Pls let me know if I had missed a step.

• Copied license key file and flows to keep to a safe place 
• Removed the app through windows app remover
• Deleted MCE directory and all files from normal program location
• Deleted MCE directory in appdata\roaming\
• Deleted MCE directory in documents
• Restarted computer

In app data I came across a log file that said not all Hvars were accounted for. Perhaps this was the problem?

Then I re-downloaded the latest version from the website - version 2.9.17 - and installed as administrator and ran the wizard, but skipped voice training as not required.

Then I started FS2020, loaded FWB A320NX at EHRD and waited for at least a minute before I did launch MCE.

MCE started normally. Of course I needed to redo a few settings. Keeping Clive for now for testing. One problem: no voxscripts were copied to the documents folder. I know where to find them, but this seems like a flaw in the installation process or there is another log/ini file somewhere that I should have deleted and I did not know about. I have copied all scripts from the installation folders manually.

Checked the log file again, but still it shows the message that not all HVARS are accounted for.

I now exited out of MCE to re-run to make sure the missing scripts did not cause the hvar error message.

That seems ot have done the trick. No hvar error this time. I will now re-check all the flows done before and will report in a separate message.

Logfile seems clean now:

Logging started
Simco64_Ldr loading
Created Simconnect session
CreatedSimconnect data definitions
Mapped Simconnect Events
About to enter main loop
Created Simconnect LVars definitions
Hvars received
Hvars received
Lvars received
Lvars received
Lvars received
Lvars received
Lvars received
Retrieved all relevant FlyByWire Lvars
Retrieved all relevant FlyByWire Hvars

Kind regards,

Daniel

OK, good to hear you're up and running.

In general, you don't need to go into all that trouble to update MCE. Just do this

Un-install MCE via Windows Control panel

Do NOT manually delete anything as the license,key file and installed additional recorded voice packs remain in place (they aren't part of the main installer).

Download (save) latest version, unzip and just run InstallMCE. Safest option is to accept default installation path. That way, won't need to disable Windows UAC.

If you have any issue, click WIndows Start->Muilti Crew Experience->Restore factory settings. That will reset MCE settings in case they are messed-up and the wizard will ensure you're all set.

The flows are always saved to \My Documents\Multi Crew Experience\Copilot\Aircraft\ folder. What's more, MCE will never overwrite a flow with the same name as we always assume they will be edited by users.

I'd say the number one support issue these days, is users thinking they can totally control Windiows 10 permissions the way they used to with Windows Vista or even Windows 7.

Don't want to sound patronising, overriding Windows folders permissions is never a good idea. This usually causes Windows to deny the wizard (or any other app) creating those folders and copying files to them programmatically, something it should be able to do with standard rights. That's where all those Gemlins most people experience come from.

In my opinion, when it comes to Windows 10, leave UAC at default, never override permissions and just set apps you trust to run as admin.

See this thread for all the strange things that may happen when you play with C:\Program Files (x86)\ folder permissions.It's not worth it. Lefe's too short.🙂

 

 

[FS++ 707]

1 hour ago, danbaz said:

Happy to report much more is working now 😀

ECAMS - as before - no change

Center instr panel - clocks - same as before

Center instr panel - landing gear panel: all work, but autobrake wired incorrectly - see below

Panel	Commands	Result
center instrument panel landing gear panel	brake fan on	OK
center instrument panel landing gear panel	brake fan off	OK
center instrument panel landing gear panel	auto brake low	Set autobrake to medium!
center instrument panel landing gear panel	auto brake medium	Set autobrake to maximum!
center instrument panel landing gear panel	auto brake maximum	Switched off auto brake, nothing on 2nd try
center instrument panel landing gear panel	auto brake off	Set autobrake to low!
center instrument panel landing gear panel	anti skid on	OK
center instrument panel landing gear panel	anti skid off	OK

Glareshield - captain chronometer - All Ok as before

Glareshield - captain EFIS: All OK now except for the altimeter knobs. Also what is text command to set altimeter to three zero one two (or any variation)? Setting standard is the only action I got to work for this knob.

Few months ago I installed flows for the NEO from David. He introduced Dieter. After my reinstall I still have him onboard! how did he manage to do that? Also the FO asks for the ramp without me asking for that. I think I had to copy some xml file. Is this file causing some of my problems? Will find the installation instructions for that one now and see..    EDIT: Think this is default MCE behaviour as everything changed by the named flows was deleted at uninstall. IfThen, how can I stop Dieter to introduce himself in the cockpit? We already met in the crewroom. 😎  Also no need to ask for the ramp. It will come and go away within a few minutes anyway.

Kind regards,

Daniel

 

 

 

 

 

 

Normally, when MCE sees Dieter as the current Fo, the "Dieter ramp agent" who pops-up at German or Austrian airports (and maybe other places) should switch to some other rampy.

May want to reset MCE to factory settings. No need for speech training when you go through the wizard again. It will generate a new "mce.ini" with default settings.

It's possible to disable ramp agent greeting permanently with option

[RAMP]

NoGreeting=1

 

Edited May 9, 2021 by FS++

[FS++ 707]

4 hours ago, danbaz said:

Happy to report much more is working now 😀

center instrument panel landing gear panel	auto brake low	Set autobrake to medium!
center instrument panel landing gear panel	auto brake medium	Set autobrake to maximum!
center instrument panel landing gear panel	auto brake maximum	Switched off auto brake, nothing on 2nd try
center instrument panel landing gear panel	auto brake off	Set autobrake to low!

 

If you want to use the Dev version, as you mentioned earlier instead of the stable release it's fine. If one thing, it'll give us a heads-up with regards what may have changed and may require a few agjustments every now and then. Thanks

 

[danbaz 5]

19 hours ago, FS++ said:

The flows are always saved to \My Documents\Multi Crew Experience\Copilot\Aircraft\ folder. What's more, MCE will never overwrite a flow with the same name as we always assume they will be edited by users.

Thanks for the responses Gerald,

As there were no files as I had deleted everything, would the installer not have copied Asobo script folders to documents automatically? I use default file locations for all FS/MCE etc. related.

 

19 hours ago, FS++ said:

"Dieter ramp agent" who pops-up at German or Austrian airports (and maybe other places)

Yeah, he works in Rotterdam too. Thought he was the purser. Should listen better when he is introducing himself I guess. Thanks for the hint on how to mute.

 

14 hours ago, FS++ said:

If you want to use the Dev version, as you mentioned earlier instead of the stable release it's fine.

Yes, I will move to Development at some point and will report issues found.

Regards,

Daniel

[FS++ 707]

1 hour ago, danbaz said:

Thanks for the responses Gerald,

As there were no files as I had deleted everything, would the installer not have copied Asobo script folders to documents automatically? I use default file locations for all FS/MCE etc. related.

 

 

Folders for older supported planes (Prepar3D or FSX) were copied when the wizard ran, from MCE installation folder.

For MSFS, they are now added by installer "InstallMCE.exe"

It has all the rights it needs to create new folders and copy files to them on a typical standard Windows installtion. If it fails, the only likely reason is altered folders permissions. Not telling anyone off, just letting everyone know, when one overrides those permissions, you expect to do some checking and manual intervention.

You can find the flows by going back to downloaded unzipped file. Look under

\Resources\Files\Voicescripts\Copilot\Aircraft\ folder. Manually copy and paste them.

I will also add, many users would probably miss out on a smooth Demo experience because of that.

Normally, just need to install Demo and fly.

Only requirement, with MSFS, one has to wait until aircraft is ready to fly, fully settled, before starting MCE.

 

[hadi 30]

Hi there

What command could i use to turn the brightness of the MCDU screen, making it brighter?? i tried a few to no avail

Edited May 10, 2021 by hadi

[danbaz 5]

6 hours ago, FS++ said:

If it fails, the only likely reason is altered folders permissions.

To my knowledge I have not changed permissions, but it sounds something happened that prevented proper file transfer.

 

6 hours ago, FS++ said:

Manually copy and paste them

I copied to my documents folder. Assume that is where they needed to go. So when I understand correctly there is a permission issue with my documents folder (not the program files folder where core MCE program is installed in)?

 

6 hours ago, FS++ said:

I will also add, many users would probably miss out on a smooth Demo experience because of that.

Would be a pitty. MCE is a great program. Hope you can take that barrier down some way.

[FS++ 707]

19 hours ago, danbaz said:

To my knowledge I have not changed permissions, but it sounds something happened that prevented proper file transfer.

 

 

There is one way to find out.

Un-install MCE via Windows Control Panel.

Do not delete anything manually.

Create a new account on PC (not the type requiring Hotmail or Outlook account), with admin privileges so you can install software.

That will give you a virgin account with all default permissions and UAC to default. Don't chnage any of that.

Login to the new account.

Install MCE to default path.

Immediately after that, check that the <Aerosoft CRJ> and <ASOBO_A320_Neo> folders have been added to \My Documents\ folder.

Run the wizard and you should see many more added, including <Voxkey> folder.

If it's not the case, we'll look at the installer again.

Obviously can't run MSFS fom new account as its DRM ties you to the one you installed it from.

After that, just switch back to your usual account.