Sounds great, thanks again for all the work you put into this.  It'll be a few days before I can try it, but I'll report back 👍.

I converted all my scripts from PMDG's NG to use with iFly's MAX. I found a few, still outstanding issues:

• Oxygen check doesn't check oxygen, instead it moves the F/O's seat and armrests.
• Fuel flow reset puts the switch to used fuel twice instead of to reset once.
• Autoflight disengage lights are tested for both Captain and F/O. Personally, I'd prefer this to be separate commands for left and right side.
• No command for runway inhibit switch.
• Engine/APU fire test: The left overheat switch gets stuck in A position. Generally, the test should be:
  • Both overheat switches normal
  • Test switch to fault/inop
  • Test switch to overheat/fire
  • Both overheat switches to A
  • Test switch to overheat/fire
  • Both overheat switches to B
  • Test switch to overheat/fire
  • If that's too elaborate for MCE, perhaps it's better to just go with both overheat switches normal and test switch to fault/inop, then overheat/fire.
• Cargo fire test switch needs to be depressed longer to actually activate the test.
• "Transponder standby" command puts the right switch to altitude off instead of operating the left one that actually turns the transponder on and off (and to auto).
• "Reset rudder trim" command sometimes misses the 0 target (same in the PMDG NG).
• F/O is able to operate the elevator trim even with cutout switches set to cutout (maybe a limitation in iFly's SDK though).
• A command for the VSD for both sides separately would be nice.
• Chrono commands need to be mapped to the chrono button on the outer edge of the glareshield.
• There is no command for the VNAV button on the FMC (that replaces climb, cruise and descent).
• Recall is being pressed twice.

On 11/24/2024 at 1:39 PM, threexgreen said:

I converted all my scripts from PMDG's NG to use with iFly's MAX. I found a few, still outstanding issues:

• Oxygen check doesn't check oxygen, instead it moves the F/O's seat and armrests.
• Fuel flow reset puts the switch to used fuel twice instead of to reset once.
• Autoflight disengage lights are tested for both Captain and F/O. Personally, I'd prefer this to be separate commands for left and right side.
• No command for runway inhibit switch.
• Engine/APU fire test: The left overheat switch gets stuck in A position. Generally, the test should be:
  • Both overheat switches normal
  • Test switch to fault/inop
  • Test switch to overheat/fire
  • Both overheat switches to A
  • Test switch to overheat/fire
  • Both overheat switches to B
  • Test switch to overheat/fire
  • If that's too elaborate for MCE, perhaps it's better to just go with both overheat switches normal and test switch to fault/inop, then overheat/fire.
• Cargo fire test switch needs to be depressed longer to actually activate the test.
• "Transponder standby" command puts the right switch to altitude off instead of operating the left one that actually turns the transponder on and off (and to auto).
• "Reset rudder trim" command sometimes misses the 0 target (same in the PMDG NG).
• F/O is able to operate the elevator trim even with cutout switches set to cutout (maybe a limitation in iFly's SDK though).
• A command for the VSD for both sides separately would be nice.
• Chrono commands need to be mapped to the chrono button on the outer edge of the glareshield.
• There is no command for the VNAV button on the FMC (that replaces climb, cruise and descent).
• Recall is being pressed twice.

Sorry for the delay caused by the need to urgently support MSFS 2024.

The runway inhibit switch should have been working. with commands "gpws runway to override", "gpws runway to normal"

In the current patch, there is a "available_commands.dat" file more appropriate to the MAX. The commands showing in listbox under that plane come from there and it's slightly different from the one for PMDG 737NG. 

Other issues now sorted except for VSD which isn't understood. Could you confirm which switch you're referring to? and what speech commands you'd like to use?

Should have new patch by next Tuesday if you reply quickly.

 

Issues now sorted e

21 minutes ago, FS++ said:

Sorry for the delay caused by the need to urgently support MSFS 2024.

No worries.

21 minutes ago, FS++ said:

The runway inhibit switch should have been working. with commands "gpws runway to override", "gpws runway to normal"

Will try this.

21 minutes ago, FS++ said:

Other issues now sorted except for VSD which isn't understood. Could you confirm which switch you're referring to? and what speech commands you'd like to use?

The Vertical Situation Display that can be shown on the bottom of the Navigation Display. The switch to toggle this is located on the EFIS (the square switch between the minimums and altimeter dial switches that says VSD). A separate command for the F/O to switch this on on his side would be appreciated. Something plain like "your side nd show vsd/vertical profile".

I also noticed some other issues. When I command an altitude to set in the MCP, the F/O seems to be unable to read the currently set altitude and dials it back to 0 in order to go from there up to whatever I've commanded. This is problematic since he will dial down past the current altitude the airplane is at (when in VNAV speed for example, the climb will stop and VNAV goes into VNAV altitude).

Some other minor issues are that the F/O seems unable to determine the current state of the generators, probe heat switches, IRS switches and I think APU bleed and APU switches. During the checklist, he will hesitate and operate the switches and announce "now set" even though they were already in the desired position. Not too important but a minor annoyance.

Edited December 7, 20241 yr by threexgreen

1 hour ago, threexgreen said:

No worries.

Will try this.

The Vertical Situation Display that can be shown on the bottom of the Navigation Display. The switch to toggle this is located on the EFIS (the square switch between the minimums and altimeter dial switches that says VSD). A separate command for the F/O to switch this on on his side would be appreciated. Something plain like "your side nd show vsd/vertical profile".

I also noticed some other issues. When I command an altitude to set in the MCP, the F/O seems to be unable to read the currently set altitude and dials it back to 0 in order to go from there up to whatever I've commanded. This is problematic since he will dial down past the current altitude the airplane is at (when in VNAV speed for example, the climb will stop and VNAV goes into VNAV altitude).

Some other minor issues are that the F/O seems unable to determine the current state of the generators, probe heat switches, IRS switches and I think APU bleed and APU switches. During the checklist, he will hesitate and operate the switches and announce "now set" even though they were already in the desired position. Not too important but a minor annoyance.

 

Thanks

Newly reported items will be looked at as well

Regarding MCP ALT dialing...

Was the ALT window blanked when you asked him to dial?

1 minute ago, FS++ said:

Was the ALT window blanked when you asked him to dial?

No. It was set to FL190, then F/O dialed way back down in order to go up to FL390.

On 12/7/2024 at 6:40 PM, threexgreen said:

No. It was set to FL190, then F/O dialed way back down in order to go up to FL390.

It is confirmed and fixed in new patch along with other items you reported earlier. Please replace all files in this patch (V3.1.1.0)

.

On 12/12/2024 at 12:27 AM, FS++ said:

It is confirmed and fixed in new patch along with other items you reported earlier. Please replace all files in this patch (V3.1.1.0)

.

From what I can see, the items still don't work despite the update.

• IRS switches state reading
• Generators state reading
• VNAV button no command
• VSD no command
• APU bleed air switch "now set"
• Fuel reset is set to used twice instead of reset
• Autobrake setting to anything higher than off rotates the switch to RTO first, resulting in the amber disarm light illuminating and staying illuminated
• WX radar is set to MAP instead of leaving it on auto when turning on WX radar
• Flaps up command doesn't seem to work when within a script

Is there a separate command for "your side start chrono" for the F/O to start his chrono on his side like it works for Airbusses?

On 12/21/2024 at 3:49 PM, threexgreen said:

From what I can see, the items still don't work despite the update.

Thanks for reporting these items

• IRS switches state reading
• Might be to do with the type of reply. OFF, Align, NAV are well covered with the respective switches needing to be in specific positions (that can be read), We'll ensure any other reply gets accepted
• Generators state reading
• Should be sorted in next update
• VNAV button no command
• If you mean FMC VNAV, should be in next update
• VSD no command
• Provided you replaced the grammar files in \CandC\ folder. The commands are already in the revised grammar. I guess the "available commands doesn't list it. Doesn't mean it doesn't exist though, Try these commands
• efis show vertical profile   (Edit)
• efis hide vsd                             (Edit)
• your efis display vsd   (Edit)
• your efis remove vsd (Edit)
• APU bleed air switch "now set"
• Will be checked again. Would be helpful is you could post the checklist line for this item
• Fuel reset is set to used twice instead of reset
• We'll double-check
• Autobrake setting to anything higher than off rotates the switch to RTO first, resulting in the amber disarm light illuminating and staying illuminated
• This was due to the fact the same code is shared with iFly737NG and the state couldn't be read in early implementation. OK, this will be changed to increment/decrement relative to current position
• WX radar is set to MAP instead of leaving it on auto when turning on WX radar
• Will be looked at
• Flaps up command doesn't seem to work when within a script
• Try scripting alternatives like "retract flaps" or "flaps retract"

Is there a separate command for "your side start chrono" for the F/O to start his chrono on his side like it works for Airbusses?

The "Available commands.dat" file is listing "start the clock", "stop the clock". That was a mistake as this plane can work out flight time on its own. As it happens, those commands will activate the chrono. Fo starts both left and right chronos. Proper commands for chrono...

start chronometer

stop chronometer

reset chronometer

 

Answers embedded above

Edited December 24, 20241 yr by FS++

On 12/21/2024 at 3:49 PM, threexgreen said:

From what I can see, the items still don't work despite the update.

• IRS switches state reading
• Generators state reading
• VNAV button no command
• VSD no command
• APU bleed air switch "now set"
• Fuel reset is set to used twice instead of reset
• Autobrake setting to anything higher than off rotates the switch to RTO first, resulting in the amber disarm light illuminating and staying illuminated
• WX radar is set to MAP instead of leaving it on auto when turning on WX radar
• Flaps up command doesn't seem to work when within a script

Is there a separate command for "your side start chrono" for the F/O to start his chrono on his side like it works for Airbusses?

Issues with switches should be sorted in latest package. You'll need to re-install as new files and folders have to go into various places to support FlyBywire A380 and Inibuilds A330 in MSFS 2024.

Try scripting "flaps retract" or "retract flaps".

If there is anything else required, will be addressed via a patch.

 

On 12/28/2024 at 6:37 PM, FS++ said:

Issues with switches should be sorted in latest package. You'll need to re-install as new files and folders have to go into various places to support FlyBywire A380 and Inibuilds A330 in MSFS 2024.

Try scripting "flaps retract" or "retract flaps".

If there is anything else required, will be addressed via a patch.

 

Thanks, will update and report back as soon as possible.

On 12/28/2024 at 6:37 PM, FS++ said:

Issues with switches should be sorted in latest package. You'll need to re-install as new files and folders have to go into various places to support FlyBywire A380 and Inibuilds A330 in MSFS 2024.

Try scripting "flaps retract" or "retract flaps".

If there is anything else required, will be addressed via a patch.

 

I found that responding to "IRS selectors" with "NAV" during the checklist still makes the F/O respond with "now set" even though it was in NAV already. Same thing still for the generators and probe heat (auto position).

On 1/12/2025 at 4:40 PM, threexgreen said:

I found that responding to "IRS selectors" with "NAV" during the checklist still makes the F/O respond with "now set" even though it was in NAV already. Same thing still for the generators and probe heat (auto position).

Please write down the exact lines that are present in your custom checklist related to IRS and generators so they can be tested through the debugger to see what's happening. Thanks

Edited January 17, 20251 yr by FS++

For those on a budget, there is now a dedicated package for the iFly 737 MAX in MSFS 2024 or 2020

https://secure.simmarket.com/fs-limited-multi-crew-ifly-737-max-msfs2420.phtml

 

Package now updated to V3.1.4.8 and ready for AI voice pack.

 

Edited March 16Mar 16 by FS++