dandy_don

Most VA's I have been associated with allow you to leave comments when filing a PIREP. What I do is state that I exceeded 250kts under 10K due to weight constraints. No one has ever dinged me yet.

Until the next one is issued the first of next month, however the month-to-month modifications are usually minor. If you are a casual flyer, you could probably update every 3 months and not notice many changes.

When I have used Sim Routes it tries to save the file with a "-" between the departure and arrival airport codes. I always do a "save as" and eliminate the "-". Example: Sim Routes tries to save the file as "KORD-KJFK" and I save it as "KORDKJFK", which is the exact comapny route I type in the FMS. I have no idea if this helps but I know it was one of the issues I have incurred. Also, do a save as and make sure it is saving the file in the correct file.

I'm not sure all of this is necessary, but by trial and error this is what I did. With FSX running, it's under the "Add-ons" tab, "PMDG", "Options", "Airline Options - Equipment". I found it yesterday after reading this post. Then in FSX, go to "Settings", "Graphics" and click "Advanced Animations".

There are multiple FedEx VA's. I am on the staff of the FDXVA http://www.airfrontierva.com/fedex/ where I am the Memphis Hub Manager. Come join us.Don

I remember the same thing. Perhaps we made the same error, but I had to modify the fuel to 30.0 on the load manager as well.

Thanks, however take a look at this:I was flying yesterday from KIAH to KMEM on the flight path suggested by FlightAware (ELD3 ELD TAMMY3) with southern winds for the approach. I had to plan for almost this exact landing. Knowing what I know now, I did change my speeds requirements in the FMS to 250 kts crossing TAMMY, 230kts crossing JAMEA and 210kts crossing TWIKL. Additionally, I forced the altitude at ACALE to be at 5,000 feet (I believe the FMS calcuated elevation for ACALE was over 8,000 feet), which helped when the decent path recalculated upon cutting short the planned route similar to the situation in the prevous post. Even at the reduced speeds, it still cut short the ACALE intersect by at least 5 NMs, similar to the photo in the previous post.

This particular case was KMEM (Memphis Int'l) Rnwy 18C. I was just doing a few departures and landings on this runway. At random, I entered a waypoint along the flight path some +/-10NM to the west then to a waypoint +/-15NM to the north (CADER) of the nearest waypoint for the approach to allow for some distance to adjust, since I understand the aircraft "can't turn on a dime".Thanks for your reply. Perhaps forcing the aircraft to slow down will correct the shorter path issue. I'll give it a try.

more photos of the same issue from the same flight.

Why does the flight path divert from the planned routes by cutting short the various waypoints? In the photo below, the path turns towards the next waypoint approxiamtely 5 NMs from the CADER intersect. When this happens on a decent, the autopilot has to rapidly readjust the decent rate that seems to have been calculated on the longer route (all the way to the waypoint) once the next waypoint becomes active in the FMS and sometimes there is an altitude elevation error message in the FMS because of this.

That's the point. The temperatures were climbing to some unrealistic values.Someone helped me out on a different forum with this as they had the same issues. The weather would not regenerate on it's own, I had to force it.. This has not been an issue with any other aircraft--typically once you hit the CAVOK option, the weather ususally changes immediately. For some reason, with the MD-11, you have to force the weather to regen.Just before this screen shot was taken, the TAT was +48C and rising. Even after selecting the CAVOK option and waiting a minute or so, nothing changed. Once I forced the weather to update, the TAT went to a value that seems logical.

How? When the problem started (aircraft slowing down, climb rate dropping to +/-100 fpm and the temperature TAT +/-50C) I clicked on the CAVOK button on the FSInn panel, which I understand should fix this, and nothing changed? I continued flying thinking it would change at some point but it never did. The aircraft continued to stall, the climb rate remained almost nothing and the TAT stayed where it was. Do you have to hit CAVOK before a certain flight level? What happens if you get to that flight level, like me, where you don't hit the CAVOK button before the problems begin, how do you jump start it?I have since changed my default weather in the settings to "Disable Weather by Default". Will this help?

I have this same problem using the PMDG MD-11 with FSInn flying online. The TAT gets to +50C above FL245 and renders the aircraft unflyable. Using the CAVOK button (in FSInn which is supposed to fix this problem) does nothing, as it does for other aircraft. I was so much looking forward to getting this aircraft and take it for a spin, only to find that it doesn't spin very well online using standard equipment (FSInn).It seems odd that the answer to fixing this problem is for the individual to spend additional money for a weather generator (REX or ASX). I would have thought the staff would have looked into this before releasing this aircraft or at least issued a patch by now to correct it. I am thoroughly disappointed with this aircraft.