scmtech

This was set to: GroundServicesMode=Native I changed the value to GSX and now MCE can initiate the pushback process. Thanks for working through this issue.

A "fsdt-msfs-bridge.wasm" file is present in my GSX community folder "\Packages\Community\fsdreamteam-gsx-pro\modules". MCE is installed at: "C:\Program Files (x86)\Multi Crew Experience" Thanks.

Yeah, I unfortunately do not even get the GSX menu when trying to initiate it. As a note, I'm using the 737-900. Thanks again.

Yes, GSX is up to date - version 2.9.8. GSX is working when I use the GSX menus in the sim. Yep, aircraft also has power via battery and APU or GPU depending on the state of the flow.

When I start MCE, GSX does not start up. Both engines are off when I'm at the gate. I did a test with your exact script setup as a new script, and no luck with GSX - it just does the built in/default pushback - mechanic says "pushing straight". Thanks.

Okay updated to 3.0.7.8. Still not having luck with GSX pushbacks via MCE.

No, I am not hearing anything like in the video you linked. I can see the green text in the Sim tab though. Also, tested again using the steps Burge mentioned too, but I am getting the same results of the "default" pushback, no GSX.

Sorry for the delayed response, been away from the sim for a little bit. I have tried multiple airports gates and ramp parking, same results, I am testing currently at KATL Gate D24. I can get the ramp agent to respond from MCE if I give a command from the "to establish contact" list, such as saying "Ground from flight deck". Then I try to trigger the pushback by saying "Ground mechanic start pushback". Thanks again for your help.

I completed the reinstall process, and re-applied the patch as instructed, unfortunately I am still not able to get the GSX pushback to start. I tried to follow the steps Burge was describing too in the recent post, but it still is trying to use the built in pushback. Below is my latest log file: Thanks for your help. Logging started Simco64_Ldr loading Created Simconnect session CreatedSimconnect data definitions Mapped Simconnect Events About to enter main loop checking for Fenix A320 Connected to MSFS Config data requested... SIMCONNECT_RECV_ID_CLIENT_DATA received: EVENT_CONFIG_RECEIVED Config data updates requested. Lvars received Lvars received Lvars received Lvars received Lvars received Lvars received Lvars received Lvars received Lvars received Lvars received Lvars received Lvars received Lvars received Lvars received Lvars received Retrieved GSX Lvars

No it is not happening, and I installed to a custom path on the drive where my sim is installed. Do you want me to try and uninstall and reinstall with the default path? I did try to run the app as an administrator to see if that would help, no change there either.

As an update from the 3.7.0.6 patch: These commands work now I am using: "push flight attendant call" "press ground call" Thanks for adding these. The right recirculating fan command is working for me as expected in my flows for the MSFS PMDG 737-900. The command is recognized, but it is using the native mode - just causing the aircraft to pushback without a tug - it will not start the GSX pushback. GSX pushback works when I start it via the GSX menu. Hope this clarifies the issue. Please let me know if there are any other details I can provide. Thanks again. I am still encountering issues getting the GSX pushback to trigger via MCE (voice command or via FO flow voxscript). The native push back will work, but it will not start the GSX process. I can start GSX on my own through the native GSX menus in the sim, so I can confirm the GSX app is working. I took a look at the log file just to see if there was anything: Lvars received Retrieved GSX Lvars SIMCONNECT_RECV_ID_CLIENT_DATA received: EVENT_CONFIG_RECEIVED Config data updates requested. Lvars received Thanks again.

The command is recognized, but it is using the native mode - just causing the aircraft to pushback without a tug - it will not start the GSX pushback. GSX pushback works when I start it via the GSX menu. Hope this clarifies the issue. Please let me know if there are any other details I can provide. Thanks again.

This would be nice for additional immersion, so I can include it as part of the flow. I am still having issues with getting the GSX pushback to start via MCE, I have tried many of the commands for pushback described in the "ground_cmd.rtf" document in the "Multi Crew Experience\Docs" folder. I am using the latest version of GSX for MSFS as of today GSX Pro 2.9.4. Thanks.

I know this is another sort of a trivial "novelty" interaction, similar to the sun visor stow/unstow (thanks for adding that 😀 btw), but are there any interactions for the ATTEND or GRD call buttons? I was going to include these in some of my flows for additional immersion such as having the FO "call the ground crew" by turning on the service interphone (which works already) and ring the ground crew via the GRD CALL button. The ATTEND would just be a single push and release, but the GRD CALL should probably hold it for a couple seconds. Another question, does / would it be possible for Voxkey to support joystick button presses?

Is GSX supported for the PMDG in MSFS with MCE? I tried some of the commands listed in the included "ground_cmd.rtf" document and it was not using GSX. I also saw the config option [MECHANIC] PushWithGSXandAES=0 I tried this both as 0 and 1 with no luck in triggering GSX.

Thanks for the explanations. Okay, contact via email?

First, thanks again for the update. I am not sure if you got to this one or not yet but I'm still having some issues with my displays controls on the PMDG 737-900 (MSFS). When the SOURCE knob is set to ALL ON 1, I cannot get it to set to AUTO. When the CONTROL PANEL switch is set to BOTH ON 1, I cannot get it to set to NORMAL. Please let me know if there is anything else I can provide to troubleshoot this. Thank you so much for all the work on the new guard commands, I went through and tested them with my flows. All capped guards are working as expected. With majority of the guards, if the switches are guarded they should be in their normal and expected position. I did discover the commands "guard switch eec one set to secured", and "cover switch eec two switch to closed" are only checking the guard and not the push button state. I'm wondering if since you can visually check the state of the switch through the clear guard cap, if these could have logic to check to see if the push button is set to ON (by checking the ENG_EECSwitch_0 and ENG_EECSwitch_1 variables set to 1)? If they are set to OFF (value 0), the FO would complete the ON operation and close the guard. If they are already ON (EEC value 1) nothing would happen (guard would not be opened or the button pressed). I know these are kind of an edge case because all of the other guards set their switches to the normal position when they are closed. Thanks again for all your efforts and support, I am really enjoying the app.

Thank you. I look forward to working on my flows with this new update this weekend.

I also did notice when I was working on flows this evening, that the commands for - Main Panel Display normal - commanded as "main panel du normal" and also for the lower display "lower du normal" do not appear to be working as expected (expected them to be switched to the NORM positions). Also I was wondering if these are just for the FOs side or if there is a "your lower du normal". I imagine it could just be for the FO since the captain can control their own. If there is any additional information you want me to gather for this or any of the other items, please let me know. Thanks again.

Thanks yet again for your support, and looking into these items and new enhancements. I am flying in the 900 series in MSFS. If this is helpful, I tried binding the switch in another joystick app and it was using the "EVT_OH_BLEED_RECIRC_FAN_R_SWITCH" event. The LVAR was "switch_196_73X". Thanks, using the commands you provided I was able to get the left/right, and both, as well as "stab trim" (for both) of the throttle quadrant switches to work using "normal" and "cut out", when I used the term "override" it was going to "normal" as well. But I still cannot not figure out how to get the stab trim override switch to work though on the AFT of the pedestal (where the stab trim cutouts are working on the throttle quadrant). I'm thinking maybe the override term should apply to this override switch since the ones on the throttle quadrant are the cut out switches. When I was testing in another joystick app it looks like the event "EVT_STAB_TRIM_OVRD_SWITCH" controls the guard position, and the "EVT_STAB_TRIM_OVRD_SWITCH_GUARD" controls the switch OVRD and NORM while the guard is open (either 0/1 values). Very cool, thank you. If this is helpful here should be a list of most of the 737 guarded switches - I might be missing some specific ones for another variant - (I also included the clear covered guarded press switches): flight recorder eec one on eec two on passenger oxygen normal (I noticed with this one it wasn't activating the switch when I tested using the on command, just opening the guard) flight controls switch a flight controls switch b spoilers control switch a spoilers control switch b alternate flaps master battery standby power drive disconnects 1/2 (I tried the disconnect generator drive one / two and these were not working / having a response) bus transfer emergency lights gpws flaps gpws gear gpws terrain left/right (both) stab trim cutout switches (normal position is guarded into place) cargo fire disch stab trim override nose wheel steering (Captain's side, but thought I'd list it anyways)

Thank you once again for your support and answer to my questions, I have been really enjoying working with the app so far and building flows - and am excited about the potential. As I have been working on my flows, I have had some additional questions and a few issues I have encountered. 1. First more of a concern, rather than a question: I discovered on accident if you go to create a new flow in VoxScript, if you type the exact same name as an existing flow/script it will be overwritten immediately without any warning. It would be nice if the app could either prompt you if you wish to overwrite, or just prohibit and warn you of the name conflict. Steps to reproduce: Create a new script/flow called "Test A", edit and add a command to it, save and go back to the VoxScript Overview screen, create a new flow again called "Test A", edit the script - there are no commands present in the script. 2. In the 737 the "displays source set to auto" command does not trigger when the knob is set in the "ALL ON 1" position. Also, the issue is the same for the "displays control panel switch to normal position" when set to the "BOTH ON 1" position. Both are on the DISPLAYS section of the NAVGATION panel on the forward overhead. 2. The "bus transfer auto" command is setting the switch to off and then back to auto when it is already guarded. In this case I was expecting the FO to just open the guard check the switch was in auto and replace the guard. I also tested this when the switch was in the off and unguarded position, and the command would immediately guard the switch, open the guard again, set it to off, and then guard it back to auto. The other guarded switches do not seem to be behaving this way - they are just opening and closing the guard. I know you mentioned before that the FO opens the guards because: I might be in the minority of users, but in the flows that I am replicating there are many guarded switches that the FO is responsible for checking, but maybe you could consider an additional alternate phrase for the guarded switches as a future feature such as "verify {switch name} guarded" and check against the LVAR of the guard - and if it is already guarded and in the right position, take no action. Since in terms of realism / time, in most scan flows you would not unguard a switch to verify it is already in the expected position. 3. The R RECIRC FAN (right recirculating fan switch on/off) commands are not working. The left recirculating fan switch on/off commands work as expected. 4. I have been trying to learn more about the SimBrief integration features with MCE. I was wondering if it is/would be possible for the FO to automatically set the pressurization panel based on the flight plan based on the cruise level and arrival airport elevation? I was imagining a phrase with a keyword like "set flight altitude to cruise altitude" - where "cruise altitude" is the value from the SimBrief data, and "set landing altitude to destination altitude" where "destination altitude" is the elevation value for the destination set to the nearest 50 foot increment based on SimBrief data. 5. Are there any commands for setting the N1 SET and SPD Ref bug selector outer knobs? I understand that the inner knobs might not be feasible to implement to set the actual bugs, but it would be nice to control the outer knobs as they are to be checked in the flow to the auto positions. 6. I have not found commands for the various STAB TRIM switches including the STAB TRIM MAIN ELEC NORMAL / CUT OUT and AUTO PILOT NORMAL / CUT OUT positions on the throttle quadrant. As well as the STAB TRIM OVERRIDE switch on the aft of the pedestal. Are there commands for these switches? 7. The check fire squibs command only seems to be checking the #1 engine. I was expecting the test to go: hold to 1, lights illuminate, release switch and lights extinguish, hold to 2, lights illuminate, release and lights extinguish. 8. I know this is a convenience/novelty type feature, but would you consider a command for stowing / unstowing the sun visor(s)? I was able to observe a LVARs for visors_stow_unstar_R and visors_stow_unstow_L the value can be set to 0/1. There also visors_L_drag_h and visors_R_drag_h LVARs for positions. For me just having the FO being able to stow / unstow their side visor would be cool, and stowing it is part of a flow. This a low priority but just an idea I had. Thanks once again for taking the time to review these.

TLDR; If your switches are working, but not quite as expected check that your "fsuipc-lvar-module" is in your community folder. Maybe I missed this in the documentation 🤦‍♂️ My issue was the virtual FO was setting the switch to the test position, but unfortunately the switch was not being returned to the NORMAL position. I re-applied the patch again today just to confirm and re-tested - no luck. Then, I also tried a complete uninstall, and a fresh install of the patch - including removing the Multi Crew Experience folder within the Documents folder and the mce.ini file. Still no luck. The About tab of the app indicated I am using version 3.0.70. Then I reviewed the log Simco64_Ldr.log file in %appdata%\Multi Crew Experience: Config data requested... Config data requested... server wasm module not responding. Trying again Config data requested... I noticed the the "fsuipc-lvar-module" in the \Multi Crew Experience\Support\Files\MSFS\fsuipc-lvar-module directory. I recognized the file structure as a MSFS community package, so I copied this over to my community folder and restarted everything, tried the command again and it worked as you described. I do have a "custom" community folder path, so if this is supposed to be installed automatically - maybe that was the issue - or maybe I missed this in the docs. Either way it is working now 🙂👍, but wanted to share in case anyone else encounters as similar issue. Thanks again!

Cool, I tested this and it works in combination with the "alternate flaps selector switch off" command Wow that was fast. Thank you for adding this command. I am observing though that the test does not seem to finish as the switch stays in the test position after commanding "check flight data recorder". I tried commanding the switch back to NORMAL via "flight data recorder normal" "fdr normal", etc. but didn't have any luck. Please let me know if I am missing something. The procedure for the test is completed on the ground and the FLIGHT RECORDER OFF annunciator is illuminated, test by unguarding and setting the FLIGHT RECORDER switch to the TEST position. The FLIGHT RECORDER OFF annunciator should be extinguished once the switch is in the TEST position. At this point, the switch is returned to the NORMAL position and the guard is capped. In my opinion, the entire test procedure could be completed just via the "check flight data recorder" command. Thanks for this info, these commands are working as expected.

Thank you for the reply and details. This worked, found them. Great, thank you. The ALTN Flaps, toggle on the right. It is included in the flow, just to make sure it is not in the Up position (since it can only be at UP or OFF since it is spring loaded back to OFF from the DOWN position). My use case for these checks (including the guarded items I mentioned), is if you used a saved panel state and had a non-normal procedure and it was not set back to the OFF position. I understand that many of these are edge cases. Sorry, can you clarify, is there any implementation of this currently for the FO side? If so, can you please let me know what command this should be? Thanks. Understand, I was wondering if there maybe was some way to manually script, even if it would be in a file and not via the UI. Weird, I was confirming immediately after the FO prompted for me to confirm start. 👍 Great to hear. Thanks once again.

Hello MCE community and support team. I am a new user to MCE. I was recommended to check out the forums, and I have been searching and reviewed many of the “beginner” posts, but I still had a few questions for flows I am trying to build in MCE. 1. I was working on building and testing custom flows. I wanted to complete a command in the flow where the FO toggles the Flight Recorder switch to test and then back to the normal and guarded position. I know there is a “test CVR” command, but that command is for the cockpit voice recorder on the forward overhead (push green test switch). I am trying to test the Flight Recorder as shown in the screenshot on the AFT overhead. 2. I noticed when running some of the commands for some of the guarded switches are being opened to set them to what would be their normal guarded position. I added them to my flow as making sure they are in the guarded position is part of the flow - and ideally I would want to check this - so if it were not the case it would be put back to the correct position. These included the alternate flaps, standby power, and bus transfer switches (screenshot below). Is there a way that if a switch is already set in correct position, that the guard will not being opened? 3. In relation to the last question, I also wanted to check the alternate flaps position switch to the right of the guarded arm switch, to make sure it is set to off and not in the up position (down should “spring load” back to off). 4. Is there a way to check a variable or value of a gauge or a switches position within a MCE flow (not necessarily an checklist) and if it is out of bounds alert the user? I am imagining a potential failure case - where an annunciator is illuminated, a gauge is above or below a certain value, etc. Examples: Landing gear down - 3 green, Crew oxygen > x psi, oil level, hydraulic quantity, ac/dc voltmeters within range, etc. Some flows call for checking such instances, so it would be nice to be able to handle this through MCE. 5. Is there any way to have a condition for a step based on another value / switch etc. - or script such a case? One example use case would be - if there is fuel in the center tanks - turn on the center pumps. Conversely, it would also be nice to automatically have the FO shut off the center tank pumps when they are empty (low pressure lights illuminated) - maybe this happens already and I just haven’t experienced it yet? Another example use case I thought of is checking the flaps position to the flaps lever and correcting a disagreement (example: aircraft is de-energized during cockpit preparation - flaps indicate 5, but lever is set to 0, FO sets the flap lever to 5). I realize these might be more complicated use cases. 6. In the flow I was building I noticed a weird issue where duplicates were being added to the drop down list to the available completed task statements. I tried removing all of these items and saving but when I returned to this menu they were back. Screenshot below for reference. 7. I was going through the various lists of tests in the drop down, I did see an option for the master lights switch test, but I could not find an option to perform a test for the CPT or FO side AP, A/T, FMC indicator lights (set test to 1, set test to 2). Is there a command for this? Screenshot below for reference. 8. When I was going through and testing, I tried to command an engine start via speaking “start engine two”. The FO then prompted me to confirm start. I tried various commands “yes, confirm, etc.” but I could not get the FO to begin the engine start via voice. I was able to use the “button” commands to select the start process through the drop down, and the FO went through the start process. How do I command the engine start via voice commands? As a note, I have completed the various recommended voice training processes. 9. In one of my test flights, I was testing a few of the flaps commands and the FO would announce “speed checked flaps __”, however there were several test instances where I was significantly above the maximum deployment speed for these settings. Does the FO in MCE check speeds? Sorry for the extensive list of questions, but I thought it would be better to prepare a comprehensive list versus several different posts. Thank you in advanced for assistance.