On 1/21/2025 at 6:53 PM, Daytona125 said:

Probably the worst msfs purchase I made. This plane is pretty much useless in VR. I for one am sorry I bought it. If you use VR like I do just do your homework before you buy it.

I don’t fly VR, but I'd have to agree, my worst purchase for MSFS by a country mile. What is more galling is that I then picked up the Inibuilds A300F for £25 and it's far better. (I had posted as to which to get).

My cargo fleet now is pretty much the 777, 737 & 146 if I want retro. A300 gets an occasional spin.

 

G

On 1/18/2025 at 6:17 AM, Dreamflight767 said:

I think DEVs do not do themselves any favors when they release a beta/early access of their product. 

I'd rather say that customers who buy early access products are the ones who do not do themselves any favors. 😉

41 minutes ago, Farlis said:

I'd rather say that customers who buy early access products are the ones who do not do themselves any favors. 😉

I'd say both the devs and their fomo customers deserve each other 😉

On 1/18/2025 at 5:17 AM, Dreamflight767 said:

I won't necessarily say it's soulless.  When I fly it, I can feel the weight and sluggishness of an older airplane.  The DEV has definitely been slow in rolling out updates no matter how "big" the next update is supposed to be...which means some things that work are going to break.

I think DEVs do not do themselves any favors when they release a beta/early access of their product.  That initial release is extremely important and when an add-on has so many open ended issues, no matter how many updates are released the user is always going to find the airplane broken and less than adequate.  Users/customers also expect quick, solid, successive updates and when those don't arrive, people remember and blacklist.  It feels like the DEV stole a customers money.  

 I really want to like the MD-11 but TFDi has rubbed me the wrong way with this product.  I don't regret my purchase but probably won't buy from them again.

On a separate note, I find it...interesting some like the A-300 over the MD-11.  The A-300 feels cheap.  I hate that there isn't a pause at TOD either with that airplane.  I won't be going near the A-350 if they don't have it.  

Oh, quickly, back to the MD-11.  I never update it.  I always do a clean install.  You should also find all the extra MD-11 files installed and delete them too.  Always a fresh install with the MD-11.  I do that too for the A-300.

 

  

May I ask how the A-300 feels cheap? I enjoy flying it very much. 

Dosen't feel "soulles" to me, i love to fly this bird and did already a ton of flights. 

She is not a PMDG, but a lot good updates are done and more updates ( Fadec, ILS flight and landing ) are coming soon, so i am a HAPPY camper with this AC !

cheers 😉

 version 1.0.49 is now available!

Simply open the MD-11 Install Manager to update. Happy flying!

1.0.49 (11 March 2025)

 ADDED - AUTOPILOT SINGLE alert

 ADDED - Needles and deviation bar to VOR/APPR mode

 ADDED - V-SPEED exports

 ADDED - Third NAV DISPLAY functionality

 FIXED - ND range text alignment in MSFS

 FIXED - 500 foot altitude ticks being same size as others on PFD

 FIXED - PFD pitch ladder line thickness

 FIXED - Alignment of radar and mode settings on ND

 FIXED - PDWs not being deleted upon flight completion

 FIXED - Inability to delete PDWs via DEFINED WAYPOINT page

 FIXED - Various display alignment issues between P3D and MSFS

 FIXED - Flight director drawing in wrong order on PFD

 FIXED - Incorrectly shaped PFD slat/flap arrows

 FIXED - Incorrectly sized airplane symbol on split axis PFD

 FIXED - Green track diamond displaying above compass ticks on PFD

 FIXED - Missing FD bar shadow

 FIXED - PFD stall feather location

 FIXED - Incorrectly sized vertical speed geometry on PFD

 FIXED - Missing level diamond on vertical speed indicator

 FIXED - Ignition engaging when takeoff flaps set instead of with takeoff thrust

 FIXED - FPLN and tuned VOR coexisting on ND

 FIXED - Incorrect VOR pointer usage relating to bearing to point

 FIXED - Autoflight turning in wrong direction on certain turns

 FIXED - Initial state of FMS/systems being upset by weird values in MSFS during loading

 FIXED - Altitude constraints appearing incorrectly as FL incorrectly on the ND

 FIXED - Simbrief import not properly detecting and importing H-format coordinates

 FIXED - Simbrief import breaking due to DCT* leg types

 FIXED - Simbrief import not importing last airway in route

 FIXED - Issue with climb between restriction display on MCDU

 FIXED - APPR<SEL> text alignment

 FIXED - Incorrect approach FMS SPD behavior

 FIXED - Aircraft completing turn segments early under certain conditions

 FIXED - XTK appearing on VOR mode

 FIXED - Approach phase triggering not considering flaps

 FIXED - Misaligned ADD DRAG text (MSFS)

 FIXED - Cruise wind entry behavior

 FIXED - Missing "STD" text on APPR page

 FIXED - FCP altitude ignored during cruise

 FIXED - Missing magenta line on VOR/APPR mode

 FIXED - Missing static elements on VOR/APPR mode

 FIXED - Missing turn predictions and VSI on VOR/APPR mode

 FIXED - Missing to/from indicator in VOR/APPR mode

 FIXED - Standby altimeter drum rolling at 30 feet, not 100

 FIXED - AFS outline color with AFS OVRD off

 FIXED - AFS not disconnecting when paddle is pulled

 FIXED - Flickering between climb and altitude hold modes

 FIXED - Navaids not cross-syncing between FMS's properly

 FIXED - Thrust limit not raising automatically

 FIXED - Thrust limits not adjusting to MCT during low speed protection

 FIXED - Incorrect thrust limit behavior with slats extended

 FIXED - Certain FCP altitude knob behavior

 FIXED - Autothrottle not engaging with PROF

 FIXED - Invalid distances on altitude leg calcs

 FIXED - Temperature units being reset on load

 FIXED - Roll triangle and slip indicator not turning red when approaching VSS

 FIXED - THRUST ATS OFF box location

 FIXED - Invalid FCP speed targets showing on PFD (i.e. TAKEOFF mode with no V2)

 FIXED - Target speed setting behavior on TAKEOFF phase

 FIXED - Invalid internal default speed and altitude targets on FCC

 FIXED - FMA altitude appearing during GROUND PROX warning

 FIXED - Incorrect PFD altitude and speed bug designs

 FIXED - Misplaced barometer text on PFD

 FIXED - Incorrect PFD speed and altitude arrow designs

 FIXED - HI/LO SPEED PROTECTION flashing alternate with ATS OFF box

 FIXED - Incorrect fuel quantity alignment

 FIXED - Incorrectly sized/placed outlines on certain SD pages

 FIXED - Thrust limits not resetting after landing/FMS reset

 FIXED - Various panel state persistence issues

 FIXED - Selected and preselected speed separating when speed is not captured

 FIXED - Invalid altitude leg position if altitude already passed

 FIXED - Secondary F-PLN not showing on ND before activating

Edited March 12, 20251 yr by MPL

Any timeline on when this could work in MSFS 2024?

On 3/12/2025 at 10:11 PM, Purr said:

Any timeline on when this could work in MSFS 2024?

No timeline to give but i'm pretty sure that tfdi is working on 2024 compatibility also

Copied from tfdi discord by one of developers:

The upgrade to 2024 will come, but only once we're totally happy with 2020

Edited March 14, 20251 yr by MPL