V6 here. The update is appreciated. One query of the stupid variety.

How to engage the autopilot? I successfully entered all necessary data, but for the life of me could not get it to engage. The yoke was free, ALT was yoke only and IAS by my hand.

'Z' in game to engage seemingly did nothing, never heard a chime when I thought I was disengaging.

So based on what I’m seeing, tfdi is still updating the P3d version of the plane which is good.  
 

Aren’t there still a lot of missing textures (cabin/doorways) and how is performance?  I have a 12gb card so I’m less concerned about VRAM than actual smoothness while in flight.

I got this when it was released last week and I must say originally for me it was a disappointment as to start with as FMS was a total mess. Thankfully FMS has now been sorted with new navdata update from navigraph, however for those who don't have navigraph I do not think there will be an update regarding this. The texture quality I find in P3D not to be very good - there are several blurry textures inside and outside of airplane, some these have been reported to TFDi however whether they are planning to update it is another story (They are working on update for P3D with regards to VRAM issue but that's it whether they will fix texture problem I don't know). One of biggest drawbacks is EFB - P3D one's only includes some of the basics functions whereas in MSFS they have done a lot better. There is no simbreif integration or performance calculations on EFB on P3D version (They have claimed that this is due to primarily sim limitations). GSX interaction don't work well either, I think the GSX profile included has got some errors/issues. Overall I think P3D version was neglected in favour of MSFS version however they still claim that both versions are identical, In my opinion they are not. 

Edited July 12, 20241 yr by CAP1234

19 hours ago, Zatoichi said:

V6 here. The update is appreciated. One query of the stupid variety.

How to engage the autopilot? I successfully entered all necessary data, but for the life of me could not get it to engage. The yoke was free, ALT was yoke only and IAS by my hand.

'Z' in game to engage seemingly did nothing, never heard a chime when I thought I was disengaging.

Press the Autoflight button on the MCP. This essentially engages autothrottle and LNAV at the same time if we are speaking "Boeing language". Pressing "Prof" button on the MCP  will engage the vertical mode aka the equivalent of VNAV.

Disengaging is done by the clicking the button on the Yoke and the clicking button on the back of the throttles with your mouse.

In terms of mapping these buttons to joystick/throttle buttons , I have not found any info from TFDI so far.

Edited July 12, 20241 yr by 787flyer
typo

2 hours ago, CAP1234 said:

 One of biggest drawbacks is EFB - P3D one's only includes some of the basics functions whereas in MSFS they have done a lot better. There is no simbreif integration or performance calculations on EFB on P3D version (They have claimed that this is due to primarily sim limitations). GSX interaction don't work well either, I think the GSX profile included has got some errors/issues. Overall I think P3D version was neglected in favour of MSFS version however they still claim that both versions are identical, In my opinion they are not. 

Completely agree. Only 50% functionality compared to the MSFS version. No mention that the P3D EFB was going to be lacking features.
I did log a Support ticket on this. They told me they will be working on adding future EFB functionality, but there was not ETA given.

Not having Simbrief connectivity is a PITA although it provides plenty of practice for manually inputting all the legs into the FMC.

 

I was glad to see that PDB is working in the FMC. I was able to define a few custom waypoints.

I am not sure how you can enter both an altitude max and altitude min for the same waypoint in the FMC though?

 

Re the GSX profile, I made my own for P3D. The MSFS version of the GSX profile for the aircraft has quite a few door misalignments. PM me I and can share the GSX config file I made. Its for the MD-11F though!

1 hour ago, 787flyer said:

In terms of mapping these buttons to joystick/throttle buttons , I have not found any info from TFDI so far.

For TFDI's 717, I mapped to yoke buttons Autopilot and Autothrottle disengage (or whatever they're called) via the paid version of FSUIPC through the use of LVARs (see here and here for a master list for the 717).

Has TFDI published the LVARs for the MD-11 yet? If so, you should be able to map all sorts of events to joystick/yoke/throttle buttons.

Don’t see how having performance calc excluded from EFB is a P3D limitation. I’ll be keeping an eye on this aircraft. Keen to get it, but only when it’s up to scratch. 

8 hours ago, JRMurray said:

For TFDI's 717, I mapped to yoke buttons Autopilot and Autothrottle disengage (or whatever they're called) via the paid version of FSUIPC through the use of LVARs (see here and here for a master list for the 717).

Has TFDI published the LVARs for the MD-11 yet? If so, you should be able to map all sorts of events to joystick/yoke/throttle buttons.

There's a custom event for each button. If you turn on FSUIPC non-axis event logging you'll be able to see the number.

Cheers

My next, "d'oh" question: where are the manuals?

21 hours ago, JRMurray said:

Has TFDI published the LVARs for the MD-11 yet? If so, you should be able to map all sorts of events to joystick/yoke/throttle buttons.

Yes they have:  https://docs.invernyx.com/en/md11/integration

Many of the button events require you to send separate press and release events, for reasons not clear to me.  Also, in FSUIPC, you have to add a MaxCustomControlNumber=xxxxx parameter to the ini file, as the MD-11 uses custom control numbers beyond FSUIPC's normal top limit of 84232.  IIRC, I set mine to 99999.

On 7/12/2024 at 4:53 PM, 787flyer said:

I am not sure how you can enter both an altitude max and altitude min for the same waypoint in the FMC though?

 

 

Do you mean entering altitude constrains on flightplan? I think if I remember you click on right line select key on MCDU for the waypoint you intend to and then it will give you another page with different options of entering altitude restrictions and speed.. etc.

Edited July 13, 20241 yr by CAP1234

12 hours ago, Zatoichi said:

My next, "d'oh" question: where are the manuals?

TFDI did not provide any pdf manuals I think - all of required manuals and checklists are available here : https://docs.invernyx.com/en/md11/quickstart

The quick start guide there is actually on MSFS but same procedures should work on P3D. With the exception of take-off performance calculator on EFB - That does not exist on P3D yet but maybe they might update it at some point considering P3D owners have complained on their discord channel. 

Edited July 13, 20241 yr by CAP1234

17 hours ago, CAP1234 said:

Do you mean entering altitude constrains on flightplan? I think if I remember you click on right line select key on MCDU for the waypoint you intend to and then it will give you another page with different options of entering altitude restrictions and speed.. etc.

Yes, altitude restrictions. The MD11 FMS does not use "A" or "B" but instead a "+" and a "-" to signify above and below for a given altitude.

 

While one entry in the FMS with either plus or minus works, I have not been able to figure out how to combine them into a single waypoint.

 

For example, "/3000A" (T777)  >>> "/3000+"  (MD-11)  or "/ 5000B" (T777)   >>> "/3000-" (MD-11). This works for me.


However I am trying to figure out how you can enter the equivalent of "5000A/9000B" in the MD-11 FMS?

I tried some combinations but none of them has so far worked.

I have a sneaking suspicion the combo of two limits at one waypoint is not allowed in the MD.-11FMS but have not found any info to substantiate that.

 

I'm pleased to have another aircraft for V6. Their 717 was really a WIP when it came out and eventually evolved into something quite nice. I have no doubt the same will be true for the MD11. For me i am happy with my purchase.

I've been holding off on for this one for a bit while the usual post-release adjustments are made - can I assume by the looks that this is working pretty well in P3D overall? I expect like others with 8gb cards I will need to make the reallight tweaks to avoid any OOM issues.

On that note: has anyone with an 8gb card tried this on a long haul (7-12 hours) by any chance? My one worry would be a memory leak or something on the VRAM side of things making flights above a certain length impractical.

Edited July 15, 20241 yr by SimeonWilbury