Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Beta for PMDG T7. Now released

Featured Replies

Hello,

I am trying out the beta and have found a couple things so far.  I can't seem to get the IFE/Pass Seat bus to turn on.  The available command doc says that "IFE on" should do it, but I can't get it to work no matter how whether I say IFE or India Foxtrot Echo.  Also, when I try to set the autobrake it turns to multiple positions and ends up settling on disarm no matter what I say.  So far, the other direct commands are working.  I'll advise if I find anything else.

Edited by FS++
no lober in Beta

Don Polidori

  • Replies 33
  • Views 4.2k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • threexgreen
    threexgreen

    @FS++ I've completed my flows and I found only a few things not working: "Your ND mode to" and "Your ND range to" don't do anything. The respective switches aren't operated. "TCAS mode to

  • Thanks for feedback. Will be sorted. There is no need to look-up the documentation. In "Command" tab of the UI, click <Voxscript>. Select one of the pre-made flows (which you can

  • Not required for PMDG planes as they ae interfaced mostly through their SDKs No longer vital for other planes, but recommended mostly for performance reasons. When planes are loaded, they wi

  • Commercial Member
8 hours ago, FlyData said:

Hello,

I am trying out the beta and have found a couple things so far.  I can't seem to get the IFE/Pass Seat bus to turn on.  The available command doc says that "IFE on" should do it, but I can't get it to work no matter how whether I say IFE or India Foxtrot Echo.  Also, when I try to set the autobrake it turns to multiple positions and ends up settling on disarm no matter what I say.  So far, the other direct commands are working.  I'll advise if I find anything else.

Thanks for feedback. Will be sorted.

There is no need to look-up the documentation.

In "Command" tab of the UI, click <Voxscript>.

Select one of the pre-made flows (which you can modify by the way) and click <Edit>

In next screen, click <Edit <script commands>

When you get to "Script commands" panel, click <Command> button.

You should see a listbox containing many commands that apply to the PMDG 777 (dialling commands such as "set speed two fifty" or "com one one eighteen seven" aren't listed because they can only be given as direct orders and not scripted, except for "set speed v two" which can be added to a custom flow).

You either speak the listed command or select one, insert it and press the test button to check whether it's working.

@FS++ I've completed my flows and I found only a few things not working:

  • "Your ND mode to" and "Your ND range to" don't do anything. The respective switches aren't operated.
  • "TCAS mode to" commands don't do anything. The respective switches aren't operated.

A few other things:

  • "EICAS recall" command would work better if there was a longer delay in between recalling and canceling. The current implementation doesn't give enough time to read what it says before it's canceled.
  • Would be cool to have commands for the F/O's instrument source and air data switches to the right of his PFD so he can check them during preflight.
  • Alternate flaps switch (the rotary one to extend and retract flaps) doesn't have a command.
  • Would also be cool to have a command for the broadband switch (depends on livery configuration is it's there or not).
  • If possible, controlling only the visors on the F/O's side with the "visor stow/unstow" command would be better. Currently, he actions all of them and kinda slams the Captain's ones into your face (in VR).

That's all, 98% work flawlessly.

Edit: Is it still necessary to have the plane to be used with MCE set as the one MSFS loads on start-up? Is restarting the flight once still necessary?

Edited by threexgreen

  • Commercial Member
15 hours ago, threexgreen said:

@FS++ 

Edit: Is it still necessary to have the plane to be used with MCE set as the one MSFS loads on start-up? Is restarting the flight once still necessary?

Not required for PMDG planes as they ae interfaced mostly through their SDKs

No longer vital for other planes, but recommended mostly for performance reasons.

When planes are loaded, they will typically register anywhere between 2000 (example fenix A320) to 4000 (Inibuilds A320) Lvars within MSFS and none bothers to release them when you switch to another plane.

 

4 hours ago, FS++ said:

Not required for PMDG planes as they ae interfaced mostly through their SDKs

No longer vital for other planes, but recommended mostly for performance reasons.

When planes are loaded, they will typically register anywhere between 2000 (example fenix A320) to 4000 (Inibuilds A320) Lvars within MSFS and none bothers to release them when you switch to another plane.

 

So, as an example, switching from the PMDG 737 to the Fenix A320 would work just fine, while doing the opposite may result in degraded performance since Fenix doesn't clear their Lvars - unless you restarted the sim with the A320 already set?

  • Commercial Member
1 hour ago, threexgreen said:

So, as an example, switching from the PMDG 737 to the Fenix A320 would work just fine, while doing the opposite may result in degraded performance since Fenix doesn't clear their Lvars - unless you restarted the sim with the A320 already set?

It would work just fine in any scenario.

I wouldn't call it "degraded performance". I haven't measured anything.

It is the same reason PMDG were recommending you start FSX or Pepar3D with the lightest aircraft as the default plane (more so under FSX 32 Bit to prevent running out of memory)

All selected planes in UI leave their Lvars behind when you switch to a different plane.

No big deal memory wise in 64 bit sim, but things like FSUIPC could end-up tracking 12000 Lvars instead of 2000 to 4000 (which is what every complex plane typically adds)

  • Commercial Member
On 7/7/2024 at 1:47 AM, FlyData said:

Hello,

I am trying out the beta and have found a couple things so far.  I can't seem to get the IFE/Pass Seat bus to turn on.  The available command doc says that "IFE on" should do it, but I can't get it to work no matter how whether I say IFE or India Foxtrot Echo.  Also, when I try to set the autobrake it turns to multiple positions and ends up settling on disarm no matter what I say.  So far, the other direct commands are working.  I'll advise if I find anything else.

Sorted.

Please re-download new patch using the same link that was given to you. Thanks

  • Commercial Member
On 7/8/2024 at 6:55 PM, threexgreen said:

@FS++ I've completed my flows and I found only a few things not working:

  • "Your ND mode to" and "Your ND range to" don't do anything. The respective switches aren't operated.

They should be once you re-download and apply the new patch. Use same download link.

  • "TCAS mode to" commands don't do anything. The respective switches aren't operated.

If you meant the TCAS range, above, below and normal, should now work after patching

A few other things:

  • "EICAS recall" command would work better if there was a longer delay in between recalling and canceling. The current implementation doesn't give enough time to read what it says before it's canceled.

Delay changed from 3 seconds to 6 seconds

  • Would be cool to have commands for the F/O's instrument source and air data switches to the right of his PFD so he can check them during preflight.

Implemented in new patch. See commands afyter replacing "Available_Commands.dat" file

  • Alternate flaps switch (the rotary one to extend and retract flaps) doesn't have a command.

New commands are in "manually extend flaps", "manually retract flaps (and other speech variants)

  • Would also be cool to have a command for the broadband switch (depends on livery configuration is it's there or not).

Could you point me to a specific livery or some setting that exposes this feature? thanks

  • If possible, controlling only the visors on the F/O's side with the "visor stow/unstow" command would be better. Currently, he actions all of them and kinda slams the Captain's ones into your face (in VR).

Done. From now on FO only stows/unstows visors on Fo side.

That's all, 98% work flawlessly.

Edit: Is it still necessary to have the plane to be used with MCE set as the one MSFS loads on start-up? Is restarting the flight once still necessary?

Answers embedded above.

27 minutes ago, FS++ said:

Answers embedded above.

That's amazing, thanks!

The broadband switch depends on the satcom option in the FMC equipment settings. Some configs like 2KU+SATCOM come with the switch on the left upper overhead, some don't.

  • Commercial Member
2 hours ago, threexgreen said:

That's amazing, thanks!

The broadband switch depends on the satcom option in the FMC equipment settings. Some configs like 2KU+SATCOM come with the switch on the left upper overhead, some don't.

Ah! found it after dowloading Emirates livery. Thanks

I forgot to mention earlier...

It's now possible to get co-pilot to dial decision height or MDA accurately.

It does take a while for MDA in particular.

Since MCE is multi-threaded and the task would be performed via a worker thread, even if it takes him 5 or 6 minutes to dial say MDA 6500 (good luck doing that manually), you can still interact with him/her while he's completing that task and ask for other things while he's at it..

If for some reason when you make a request to dial a specific value you realize he;s dialling the wrong one, simply issue a new xommand with the correct value and he'll correct on the fly

  • Commercial Member
On 7/8/2024 at 6:55 PM, threexgreen said:

@FS++ I've completed my flows and I found only a few things not working:

  • Would also be cool to have a command for the broadband switch (depends on livery configuration is it's there or not).

 

 

This one is now baked into the most recent patch. Re-download and replace all files, including those in CandC folder.

quick flight my initial obsrv:

1-flaps 20 and 30 orders----FO confirms if i need flaps 20 or 30 ,takes long time and unnecessary

2-during cockpit prep ,FO sets altn flaps switch to ALTN 

3-sync hdg command doesnt work

 

  • Commercial Member
2 hours ago, ayousry said:

quick flight my initial obsrv:

1-flaps 20 and 30 orders----FO confirms if i need flaps 20 or 30 ,takes long time and unnecessary

Usually happens when you don't ask for flaps to be extended incrementally, like going from flaps 5 to 20 or 30. He just wants to make sure it wasn't a case of bad speech reco or value. Without this check, you could often end-up with flaps extended brutally to high values. It's also this kind of protection that prevents FO putting handle to full flaps after speech engine mistook your rabmling "efff effefs" for "full flaps".

For the same reason first engine start always gets you a prompt from FO as you never know what happens with speech reco.

2-during cockpit prep ,FO sets altn flaps switch to ALTN  Will be checked.

3-sync hdg command doesnt work. Indeed, not implemented. Good catch. Will be added in next update. Thanks

 

Answers embedded

Edited by FS++

  • Commercial Member
On 7/12/2024 at 11:40 AM, ayousry said:

quick flight my initial obsrv:

1-flaps 20 and 30 orders----FO confirms if i need flaps 20 or 30 ,takes long time and unnecessary

2-during cockpit prep ,FO sets altn flaps switch to ALTN 

3-sync hdg command doesnt work

 

Sorted in now released package V3.0.9.3

Please ignore the Beta patch and just download using the main download link given to you via e-mail and re-install. Do not use the patch anymore

 

thanks, but the link doesnt work anymore

Edited by ayousry

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.