Fenix A320 takeoff flaps script doesn't work

[Balint Szarka]

Hi,

 

For some reason the script to set takeoff flaps does not work in the Fenix A320. I tried multiple iterations of "set takeoff flaps", "select takeoff flaps", "select planned takeoff flaps". Neither of them worked... When I spoken out either of them he would then confirm with me if I wanted the selected one (that I set in the program) and then he did it. I think by the way confirming what I ask is pretty useless hence it is an order and should not be doubted. I know the check is there to catch it if I were to make a mistake but this would never be done in real life. For that, there is a checklist. Do you think this could be fixed?

Also just another question on the side: is there a possibility to set takeoff trim?

 

Thank you for your continued help.

[FS++]

5 hours ago, Balint Szarka said:

Hi,

 

For some reason the script to set takeoff flaps does not work in the Fenix A320. I tried multiple iterations of "set takeoff flaps", "select takeoff flaps", "select planned takeoff flaps". Neither of them worked... When I spoken out either of them he would then confirm with me if I wanted the selected one (that I set in the program) and then he did it. I think by the way confirming what I ask is pretty useless hence it is an order and should not be doubted. I know the check is there to catch it if I were to make a mistake but this would never be done in real life. For that, there is a checklist. Do you think this could be fixed?

Also just another question on the side: is there a possibility to set takeoff trim?

 

Thank you for your continued help.

Unlike the PMDG 737 or 777 where MCE can get FMC CDU data (using PMDG SDK) straight and eliably from CDU, with Fenix there is no such facility.

Despite that, we have found a way to read CDU data (and FCU data for that matter), but it has a caveat. MCE can only find data (V speeds, takeoff flaps) once at least one engine is running (at which point they are assumed entered). Takes about 45 seconds to a minute to find them, with 1% failure rate.

If you check the <Monitor> tab in MCE after start, should see the data you entered reflected in panel so users don't need to set anything in that panel.

Because of the possibility of not getting the data (say after plane update), when you ask for "set takeoff flaps", Fo will want to make sure it's the right setting that is in CDU (hence the need for confirmation). You can always ask him "set flaps one" or "set flapstwo" after start in which case he won't argue.

As for FO setting stab trim, it's generally something we always stive for when doable. And you can do that with PMDG planes and some others.

Will have to check whether it was an oversight with Fenix.

 

[Balint Szarka]

13 hours ago, FS++ said:

Unlike the PMDG 737 or 777 where MCE can get FMC CDU data (using PMDG SDK) straight and eliably from CDU, with Fenix there is no such facility.

Despite that, we have found a way to read CDU data (and FCU data for that matter), but it has a caveat. MCE can only find data (V speeds, takeoff flaps) once at least one engine is running (at which point they are assumed entered). Takes about 45 seconds to a minute to find them, with 1% failure rate.

If you check the <Monitor> tab in MCE after start, should see the data you entered reflected in panel so users don't need to set anything in that panel.

Because of the possibility of not getting the data (say after plane update), when you ask for "set takeoff flaps", Fo will want to make sure it's the right setting that is in CDU (hence the need for confirmation). You can always ask him "set flaps one" or "set flapstwo" after start in which case he won't argue.

As for FO setting stab trim, it's generally something we always stive for when doable. And you can do that with PMDG planes and some others.

Will have to check whether it was an oversight with Fenix.

 

Great, I will check it out.

I think Fenix provides lvar's for setting the trim as FS2Crew does set the trim for takeoff.

While I am here, I am wondering if the ECAM TO Config push button can be added. As it seems MCE doesn't support it...

Thank you.

[Balint Szarka]

I just checked. I started up the plane, both engines running. Yet MCE doesn't even move the flap lever as part of the script.

[FS++]

2 hours ago, Balint Szarka said:

I just checked. I started up the plane, both engines running. Yet MCE doesn't even move the flap lever as part of the script.

When the MCE UI appears, give it about 45 seconds to settle. Pay attention to FO giving the left seat arm salute indicating he worked out all the Lvars he needs to monitor or set.

Then assuming Vspeeds have been entered, it would take another 45 seconds or up to a minute to fetch the Vspeeds, takeoff flaps, flex temp.

There is no hard coded "set takeoff flaps". Either you add it to a flow or give it as a direct command.

Remeber Fo won't be able to manipulate switches or levers until the Lvars detection phase is finished. So, maybe that's why he didn't set the flaps.

 

[FS++]

On 8/16/2024 at 3:13 PM, Balint Szarka said:

I think Fenix provides lvar's for setting the trim

 

Indeed.

I checked and elevator trim on voice command is already implemented for Fenix since it was officially supported. Not via "set takeoff trim" command as you would need to provide a panel with value to be typed in when it's not possible to read CDU input trim.

On ground only, you can ask co-pilot to set pitch trim to any value, any time. Words in parenthesis are optional

set pitch trim one point five (units)

set elevator trim two (units)

set pitch trim up one point five

pitch trim down one decimal three (units)

set elevator trim minus one decimal two (units)

....there are other variations.

It appears MCE can read the CDU input value for trim as well as Vspeeds with Fenix, so maybe we could add a new "set takeoff trim" cmmand if necessary.

 

 

[Balint Szarka]

Just now, FS++ said:

Indeed.

I checked and elevator trim on voice command is already implemented for Fenix since it was officially supported. Not via "set takeoff trim" command as you would need to provide a panel with value to be typed in when it's not possible to read CDU input trim.

On ground only, you can ask co-pilot to set pitch trim to any value, any time. Words in parenthesis are optional

set pitch trim one point five (units)

set elevator trim two (units)

set pitch trim up one point five

pitch trim down one decimal three (units)

set elevator trim minus one decimal two (units)

....there are other variations.

It appears MCE can read the CDU input value for trim as well as Vspeeds with Fenix, so maybe we could add a new "set takeoff trim" cmmand if necessary.

 

 

Good to hear that the command is available. It would be very nice if we could have a set takeoff trim command or something along the lines so that we could script it.

Do you think the ECAM Takeoff Config Push Button command exist? As I was unable to script it or ask for it. I have tried all kinds of variations but it seems like MCE doesn’t recognise it.

[FS++]

1 hour ago, Balint Szarka said:

Good to hear that the command is available. It would be very nice if we could have a set takeoff trim command or something along the lines so that we could script it.

Do you think the ECAM Takeoff Config Push Button command exist? As I was unable to script it or ask for it. I have tried all kinds of variations but it seems like MCE doesn’t recognise it.

There are commands such as

check takeoff configuration

check takeoff config

test takeoff config

takeoff config check

takeoff config verify

...many other variations

They should work, otherwise report it

If you are so used to "Ecam takeoff config" or whatever other command in fs2crew manual, you could teach the co-pilot to accept it as if you said "check takeoff config".

See this thread on how to speak to the crew naturally when the odd built-in command doesn't spring to your mind intuitively

When we say "voice control", we do mean it, that's why we built a "speech simulator" into MCE 🙂

 

[Balint Szarka]

On 8/16/2024 at 6:26 PM, FS++ said:

When the MCE UI appears, give it about 45 seconds to settle. Pay attention to FO giving the left seat arm salute indicating he worked out all the Lvars he needs to monitor or set.

Then assuming Vspeeds have been entered, it would take another 45 seconds or up to a minute to fetch the Vspeeds, takeoff flaps, flex temp.

There is no hard coded "set takeoff flaps". Either you add it to a flow or give it as a direct command.

Remeber Fo won't be able to manipulate switches or levers until the Lvars detection phase is finished. So, maybe that's why he didn't set the flaps.

 

I just tried again. I waited until the V speeds and flap setting were fetched from the plane however when I ran my script which includes set takeoff flaps nothing happened. I wonder if it's because if I were to ask him with engines running to set takeoff flaps he would ask me to confirm if I wanted "x" flaps. And only then he would set it. So set takeoff flaps as a script does not work unfortunately...

Edited August 20, 2024 by Balint Szarka

[FS++]

On 8/20/2024 at 2:15 PM, Balint Szarka said:

I just tried again. I waited until the V speeds and flap setting were fetched from the plane however when I ran my script which includes set takeoff flaps nothing happened. I wonder if it's because if I were to ask him with engines running to set takeoff flaps he would ask me to confirm if I wanted "x" flaps. And only then he would set it. So set takeoff flaps as a script does not work unfortunately...

Please re-download patch (uploaded today V3.0.9.8).

Should be able to script "set takeoff flaps" command (no prompt).

Make sure you don't call "after start flow" too early ( I mean before MCE has fetched CDU data from Fenix).

Cannot reproduce black screen, at least not with this release.

Anyone else affected with V3.0.9.8 please chime in

 

[Balint Szarka]

44 minutes ago, FS++ said:

Please re-download patch (uploaded today V3.0.9.8).

Should be able to script "set takeoff flaps" command (no prompt).

Make sure you don't call "after start flow" too early ( I mean before MCE has fetched CDU data from Fenix).

Cannot reproduce black screen, at least not with this release.

Anyone else affected with V3.0.9.8 please chime in

 

Thank you for the update on the "set takeoff flaps" command. I will have a look on that now 😊

Would any of this setting cause the black screen you think? Please see my mce.ini below:

[WINDOW]
Left=1404
Top=1
NoActivate=1
NoSound=1		//(set value 1 if you want to cut the various UI sounds emitted when clicking buttons or MCE minimises)
NoFullScreenDraw=1	//(set to 1, to avoid the occasional graphics artefacts than can happen when MCE UI tries to draw, and the sim is in full screen mode)
StartToTray=1

[FEATURES]
ExecuteCaptainOrders=1
ReadCheckListWhenAsked=1
PilotSpeaksToAtc=1
CopilotReportsFailures=1
EnableInterfaceVoice=0

[OPTIONS]
ConfidenceLevel=100
Debug=0			//(only set this to 1 when instructd by support)
PilotIsBVI=0		//(must be set to 1 for Blind Visually Impaired Pilots)
UIlanguage=1033
MikeTuneOnStartup=0
EnableOptimizations=1
AutoStartWithFS=0
MinimizeToTray=0
MoreResponsive=0
TrainingCompleted=1
RandomFailures=0
TweakFsConfig=0
AtcMikeUseIvao=0
ForceCopilot=1
AudioIn=Microphone (HyperX Cloud Stinge
AudioOut=Speakers (Realtek(R) Audio)
PilotName=balint			
ShowCommands=0
ForceCommands=0			//(deprecated. Do not use)
DisplayTime=3000
UseMacros=1			//(must be set to 1 For VoxKey to work)
UseNarrator=0
LoudData=0
EnableAnnouncements=0
UseVoxScripts=1
DisableNagging=1			//(set this to 1 to prevent Copilot monitoring your flying)
GroundServicesMode=Native
NoBadLanguage=1			//(set this to 1 to prevent detection of mild insults)
NoFMAcallouts=0
NoEngineStartCallouts=1
AllowActionOnEvent=1
V1CalloutIsGO=0			//(Enable this to follow Lufthansa standard call-out procedures. PNF calls-out Go instead of V one)
ReduceChatter=1
AutoNotifyOnSilentFlowStart=0 //(if "0" FO won't announce start of a procedure)
UsingFullHardwareCockpit=0	//Enable this is using a simpit with all switching via hardware
DisableVolumeFade=0
UseAlternateGrammar=1

[MSFS_HARD_MUTE]
CatchScrollLock=1

[PROFICIENCY]
Level=0

[SPEECH]
CanDo=1
Volume=69
CpuUsage=80
SpeechPace=690
InprocReco=1
DisablePitchChange=0
MaxConcurrentTasks=4
NumLockKeyMutesReco=1
NotifySRstateAudio=0

[SKILL]
Tol3=030,030,400,900,100,100,100,050
Tol2=020,020,200,700,075,075,075,030
Tol1=010,010,100,500,050,050,050,020
Tol0=005,005,050,300,025,025,025,010

[VOICES]
Voice0 =CereVoice Adam - English (East Coast America),1,0,1,0
Voice1=Richard,0,0,0,1
Voice2=Stella,0,0,0,1
Voice3=Trav,0,0,0,1
Voice4=Microsoft David Desktop,0,0,0,0

[ATC]
Mode=Native
PreventNativeATCCancellation=0
UseRadioNoise=0
StaticNoiseLevel=0
SecondaryNeedAtcWindow=0
atc1=0
atc2=0
atc3=0
atc4=1
atc5=0
UseRadarContact=0
IgnoreRC4Registry=0	//(Set this to 1 when RC4 isn't installed on the same machine as MCE)
RC4path=
IgnorePFERegistry=0	//(Set this to 1 when PFE isn't installed on the same machine as MCE)
PFEpath=
IgnoreFlightPlan=0
FlightPlansPath=C:\Users\szark\Documents\Prepar3D v5 Files
SimbriefID=369


[SIMCONTROL]
FsPanels=0
FsMenus=0
FsDialogs=0
FsKneeboard=0
ViewsAndViewpoint=0

[GAMEPAD]
JoyManID=Alpha Flight Controls
JoyProdID=Alpha Flight Controls
JoyButton=1
UseWithVoxATC=0		//(set to 1 if you want to use the same joystick assignment with VoxATC. It will ensure FO doesn't listen to your speech while the joystick button is held down using VoxATC)

[GO-FLIGHT]
Use=0			//(set to 1 for MCE to monitor the manual radio dialling process. Whether you do that via mouse-clicks or by rotating Go-Flight or other hardware modules)
TimeOut=3000		//(sets the amount of time in milliseconds that must elapse after you last click on the radio switches in VC panel, or physically rotate a button on the radio rack, before MCE assumes you are finished with dialling. Values between 2000 and 5000 are accepted)


[CHECKLIST]
ReadHeader=1        //disable only if you don't want the Fo to read the checklist section name he is about to read and go straight to checklist items
NoStateCheck=0		//(when set to 1, co-pilot will just read the checklist aloud, wait for any answer and move on, without challenging you on any item. Useful for people running simpits with hardware switches. It can be difficult for FO to read these)
Strict=1
CS 757-200 United Airlines N41140=D:\Multi Crew Experience\ChkLists\B757_check.txt
CS 767-322ER Delta Air Lines (N179DN)=D:\Multi Crew Experience\ChkLists\B767_check.txt
CS 767-322ER Delta Air Lines (N1200K)=D:\Multi Crew Experience\ChkLists\B767_check.txt
CS 757-200 Delta Airlines N723TW=D:\Multi Crew Experience\ChkLists\B757_check.txt
CS 757-200 UNITED AIRLINES N17104=D:\Multi Crew Experience\ChkLists\B757_check.txt


[MECHANIC]
PushWithGSXandAES=0
ConfirmFuel=0


[RAMP]
NoGreeting=1
NoRampToOfficeTalk=1
NoPaxDoorsAutoHandling=1
NoCargoDoorsAutoHandling=1


[PACE]
ActionDelay=1500     //The simulated delay that takes place before FO takes action. Values from 0 to 4000 milliseconds)
MCPdial=250	   //The pace at which FO increments or decrements MCP values from 100 to 250 milliseconds). Doesn't apply to some aircraft where the value is hard coded
ButtonPress=1=1000	   //The simulated time in milliseconds it takes the FO to flip a single switch. Values 500 to 2500 are accepted
VoxKeyAction=1000  //The delay in milliseconds between two consecutive VoxKey actions. Valid entries 0 to 4000.


[SPLASH]
NoSound=0

[VATSIM]
NotifyPTTstate=0

[PILOTS]

[MISC]
Path=D:\Multi Crew Experience
LastSimRun=1704996820



[TERMINATE]




[OTHER]
LastSimRun=1704723967

[CAT_III]
FlightCalloutHeight=
FlightCalloutText=
GroundCalloutSpeed=
GroundCalloutText=

[CALLOUTS]
PowerSet=0
100knots=1
V1=1
VR=1
V2=0
TransitionAltitude=1
TenThousandClimbing=1
TenThousandDescending=1
TransitionLevel=1
OneThousandFinal=0
FiveHundredFinal=0
80KnotsDecel=0
Minimums=0
100KnotsDecel=1
70KnotsDecel=1
60KnotsDecel=0
[HARD_MUTE_JOY]
JoyManID=Logitech Attack 3
JoyProdID=Logitech Attack 3
JoyButton=10
[MSFS_CHECKLIST]
FenixA320 CFM Aer Lingus EI-EDP=C:\Users\szark\Documents\Multi Crew Experience\Checklists\Aer_Lingus_A320_check.txt
FenixA320 CFM Aer Lingus EI-DEP=C:\Users\szark\Documents\Multi Crew Experience\Checklists\Aer_Lingus_A320_check.txt

 

Edited August 21, 2024 by Balint Szarka

[FS++]

1 hour ago, Balint Szarka said:

Thank you for the update on the "set takeoff flaps" command. I will have a look on that now 😊

Would any of this setting cause the black screen you think? Please see my mce.ini below:

[WINDOW]
Left=1404
Top=1
NoActivate=1
NoSound=1		//(set value 1 if you want to cut the various UI sounds emitted when clicking buttons or MCE minimises)
NoFullScreenDraw=1	//(set to 1, to avoid the occasional graphics artefacts than can happen when MCE UI tries to draw, and the sim is in full screen mode)
StartToTray=1

[FEATURES]
ExecuteCaptainOrders=1
ReadCheckListWhenAsked=1
PilotSpeaksToAtc=1
CopilotReportsFailures=1
EnableInterfaceVoice=0

[OPTIONS]
ConfidenceLevel=100
Debug=0			//(only set this to 1 when instructd by support)
PilotIsBVI=0		//(must be set to 1 for Blind Visually Impaired Pilots)
UIlanguage=1033
MikeTuneOnStartup=0
EnableOptimizations=1
AutoStartWithFS=0
MinimizeToTray=0
MoreResponsive=0
TrainingCompleted=1
RandomFailures=0
TweakFsConfig=0
AtcMikeUseIvao=0
ForceCopilot=1
AudioIn=Microphone (HyperX Cloud Stinge
AudioOut=Speakers (Realtek(R) Audio)
PilotName=balint			
ShowCommands=0
ForceCommands=0			//(deprecated. Do not use)
DisplayTime=3000
UseMacros=1			//(must be set to 1 For VoxKey to work)
UseNarrator=0
LoudData=0
EnableAnnouncements=0
UseVoxScripts=1
DisableNagging=1			//(set this to 1 to prevent Copilot monitoring your flying)
GroundServicesMode=Native
NoBadLanguage=1			//(set this to 1 to prevent detection of mild insults)
NoFMAcallouts=0
NoEngineStartCallouts=1
AllowActionOnEvent=1
V1CalloutIsGO=0			//(Enable this to follow Lufthansa standard call-out procedures. PNF calls-out Go instead of V one)
ReduceChatter=1
AutoNotifyOnSilentFlowStart=0 //(if "0" FO won't announce start of a procedure)
UsingFullHardwareCockpit=0	//Enable this is using a simpit with all switching via hardware
DisableVolumeFade=0
UseAlternateGrammar=1

[MSFS_HARD_MUTE]
CatchScrollLock=1

[PROFICIENCY]
Level=0

[SPEECH]
CanDo=1
Volume=69
CpuUsage=80
SpeechPace=690
InprocReco=1
DisablePitchChange=0
MaxConcurrentTasks=4
NumLockKeyMutesReco=1
NotifySRstateAudio=0

[SKILL]
Tol3=030,030,400,900,100,100,100,050
Tol2=020,020,200,700,075,075,075,030
Tol1=010,010,100,500,050,050,050,020
Tol0=005,005,050,300,025,025,025,010

[VOICES]
Voice0 =CereVoice Adam - English (East Coast America),1,0,1,0
Voice1=Richard,0,0,0,1
Voice2=Stella,0,0,0,1
Voice3=Trav,0,0,0,1
Voice4=Microsoft David Desktop,0,0,0,0

[ATC]
Mode=Native
PreventNativeATCCancellation=0
UseRadioNoise=0
StaticNoiseLevel=0
SecondaryNeedAtcWindow=0
atc1=0
atc2=0
atc3=0
atc4=1
atc5=0
UseRadarContact=0
IgnoreRC4Registry=0	//(Set this to 1 when RC4 isn't installed on the same machine as MCE)
RC4path=
IgnorePFERegistry=0	//(Set this to 1 when PFE isn't installed on the same machine as MCE)
PFEpath=
IgnoreFlightPlan=0
FlightPlansPath=C:\Users\szark\Documents\Prepar3D v5 Files
SimbriefID=369


[SIMCONTROL]
FsPanels=0
FsMenus=0
FsDialogs=0
FsKneeboard=0
ViewsAndViewpoint=0

[GAMEPAD]
JoyManID=Alpha Flight Controls
JoyProdID=Alpha Flight Controls
JoyButton=1
UseWithVoxATC=0		//(set to 1 if you want to use the same joystick assignment with VoxATC. It will ensure FO doesn't listen to your speech while the joystick button is held down using VoxATC)

[GO-FLIGHT]
Use=0			//(set to 1 for MCE to monitor the manual radio dialling process. Whether you do that via mouse-clicks or by rotating Go-Flight or other hardware modules)
TimeOut=3000		//(sets the amount of time in milliseconds that must elapse after you last click on the radio switches in VC panel, or physically rotate a button on the radio rack, before MCE assumes you are finished with dialling. Values between 2000 and 5000 are accepted)


[CHECKLIST]
ReadHeader=1        //disable only if you don't want the Fo to read the checklist section name he is about to read and go straight to checklist items
NoStateCheck=0		//(when set to 1, co-pilot will just read the checklist aloud, wait for any answer and move on, without challenging you on any item. Useful for people running simpits with hardware switches. It can be difficult for FO to read these)
Strict=1
CS 757-200 United Airlines N41140=D:\Multi Crew Experience\ChkLists\B757_check.txt
CS 767-322ER Delta Air Lines (N179DN)=D:\Multi Crew Experience\ChkLists\B767_check.txt
CS 767-322ER Delta Air Lines (N1200K)=D:\Multi Crew Experience\ChkLists\B767_check.txt
CS 757-200 Delta Airlines N723TW=D:\Multi Crew Experience\ChkLists\B757_check.txt
CS 757-200 UNITED AIRLINES N17104=D:\Multi Crew Experience\ChkLists\B757_check.txt


[MECHANIC]
PushWithGSXandAES=0
ConfirmFuel=0


[RAMP]
NoGreeting=1
NoRampToOfficeTalk=1
NoPaxDoorsAutoHandling=1
NoCargoDoorsAutoHandling=1


[PACE]
ActionDelay=1500     //The simulated delay that takes place before FO takes action. Values from 0 to 4000 milliseconds)
MCPdial=250	   //The pace at which FO increments or decrements MCP values from 100 to 250 milliseconds). Doesn't apply to some aircraft where the value is hard coded
ButtonPress=1=1000	   //The simulated time in milliseconds it takes the FO to flip a single switch. Values 500 to 2500 are accepted
VoxKeyAction=1000  //The delay in milliseconds between two consecutive VoxKey actions. Valid entries 0 to 4000.


[SPLASH]
NoSound=0

[VATSIM]
NotifyPTTstate=0

[PILOTS]

[MISC]
Path=D:\Multi Crew Experience
LastSimRun=1704996820



[TERMINATE]




[OTHER]
LastSimRun=1704723967

[CAT_III]
FlightCalloutHeight=
FlightCalloutText=
GroundCalloutSpeed=
GroundCalloutText=

[CALLOUTS]
PowerSet=0
100knots=1
V1=1
VR=1
V2=0
TransitionAltitude=1
TenThousandClimbing=1
TenThousandDescending=1
TransitionLevel=1
OneThousandFinal=0
FiveHundredFinal=0
80KnotsDecel=0
Minimums=0
100KnotsDecel=1
70KnotsDecel=1
60KnotsDecel=0
[HARD_MUTE_JOY]
JoyManID=Logitech Attack 3
JoyProdID=Logitech Attack 3
JoyButton=10
[MSFS_CHECKLIST]
FenixA320 CFM Aer Lingus EI-EDP=C:\Users\szark\Documents\Multi Crew Experience\Checklists\Aer_Lingus_A320_check.txt
FenixA320 CFM Aer Lingus EI-DEP=C:\Users\szark\Documents\Multi Crew Experience\Checklists\Aer_Lingus_A320_check.txt

NoFullScreenDraw=1

StartToTray=1

The settings above play a part. as MCE won't do any UI drawing. Shouldn't even see a black rectangle until you right-click the MCE tray icon and select "show control panel" from the drop-down menu

Could also have been caused by tweaks to the UI with regards Voxdcript panel, that's why we are always open to the possibility something may break with all those hectic updates. It's not like the first release.

By the way, everything you see in the UI is just an optical illusion.

There are no standard tabs, checkboxes or buttons.

Only a single window (Main MCE window 512 x 256 where sprites (sections from a bitmap) are drawn depending on context.

simulated buttons and checkboxes can get their text labels in 6 different languages.

See this picture

The only standard control we use is the Windows listbox in Voxscript panel because it was too hard to emulate one.

We tend to do things the hard way here 😛..... not for the sake of it though.

Seriously, there is a big benefit in that we don't use a translation layer like Dot.NET, no framework to install. The app talks directly to Windows core dlls (user32.dll, GDI32.dll and kernel32.dll) and the speech engine. That's why it's the most responsive and can run on a dual ccore CPU with FSX without affecting simulator performance.

 

 

[Balint Szarka]

13 hours ago, FS++ said:

 

Oh you are a star 🤩 Unchecking the two above mentioned functions solved the issue.

I love your enthusiasm for making things efficient and better.

Now this is a long shot I think but do you think that in the future there could be a function where one could write in an Lvar and assign that particular Lvar to a particular command? Or to even make the program even more versatile let the user assign conditions in which particular flows are carried out?That would be a dream come true, literally!

 

Thank you for your continued help. Very much appreciated.

Edited August 22, 2024 by Balint Szarka

[Balint Szarka]

Sorry for being so active on here and possible annoying with this too, but just curious. Would there be a list of all the functions that one can insert in the mce.ini?

It's very difficult to piece them all together from hundreds of pages of Avsim forum topics.

[FS++]

2 hours ago, Balint Szarka said:

Oh you are a star 🤩 Unchecking the two above mentioned functions solved the issue.

I love your enthusiasm for making things efficient and better.

Now this is a long shot I think but do you think that in the future there could be a function where one could write in an Lvar and assign that particular Lvar to a particular command? Or to even make the program even more versatile let the user assign conditions in which particular flows are carried out?That would be a dream come true, literally!

 

Thank you for your continued help. Very much appreciated.

Thank you

To clarify, I'm not the main dev at FS++

This functionality gets requested about once every 3 years.

Let me explain why we won't go that route.

We need to keep MCE as mostly a speech based app, with no programming skills required.

Even naming "Voxscript" was a mistake. Should have been called "VoxFlow". Essentially putting speech commands in a sequence to make a custom task for the crew to perform..

If we start adding conditions and things like that, we would make perhaps 50 to 100 people very happy, but we could alienate many others who would wrongly think it's that "voice control for programmers".

Also, not all Lvars are settable, and sometimes they get renamed or removed.

Edited August 22, 2024 by FS++