gmt2001

Also remember that FSX is using very OLD information and thus the frequencies in your charts will not always match up to whats in FSX

Operating Manual Volume 2. Pages 4.10.2 and 4.10.3 (186 & 187 in PDF)MCP Speed Condition SymbolsOverspeed or underspeed limiting symbol appears when commanded speed cannot be reached.Underspeed limiting (flashing character “A”)-minimum speedOverspeed limiting (flashing character “8”)-Vmo or Mmo limit-landing gear limit-flap limit.

i found the post on vatsim forums According to the post below the quoted one its a bug related to FSX's SimConnect SDKThe solution is to either use 3rd party weather, in which case FSINN weather should always be on CAVOK or disabled through the menu. Or to go CAVOK and activate FSX real world weather from the menu when you get near the problem altitude (or transition alt as this guy suggests)

make sure the weather symbol is not filled in on FSINN next to Vatsim. If it is then try selecting CAVOKWith FSINN once you get above a certain altitude (i belive it was 10k) it is reccomended to go CAVOK and then switch to using the FSX real world weather or a 3rd party weather addon because FSINN enters the temperature using the wrong temperature offset

I must point out that aircraft lights on VATSIM is a feature provided by the client software (FSINN/Squawkbox) and that no matter what the developers here do, it would still depend on those programs light syncronisation facilities enabling the correct lights in the correct way. This isnt a feature of VATSIM. The way the client software implements things like lights and animations is by creating their own peer-to-peer connections between pilots and sending data about aircraft state. The VATSIM network itself does not support any of this.

This completely defeats the purpose of the FMC and Auto Throttle then

I am having a similar problem when flying EWR to PHL except im doing everything in what seems to be the right way. I programmed for a 4L departure via EWR8 to BIGGY MAZIE and then PHL ILS 9R via DQO with a cruise of 8000 and i let the FMC automatically decide my speeds and altitudes at each waypoint. Near my T/D which is just before DQO i set the MCP to 4000 which is the altitude of the first waypoint after DQO (i planned to set the altitude of each subsequent waypoint until glideslope capture as was necessary to simulate being cleared). The problem is as im descending the aircraft speeds up by about 30-40 over the selected speed for DQO (when im already past it and the decel marker) and then at around 5350 it reduces vertical speed to -50 and none of the controls to intervene work. In the end after trying all my buttons its so late that the glideslope is impossible to catch and have to go around. Also after the EWR8 when i am in the (VECTORS) instruction and i use HDG HOLD to vector to BIGGY i notice that for some odd reason the plane always flys a heading 2 degrees less then what i set and therefore i cannot use the heading bug/line on the moving map to set an accurate course