Philsfan814

what did you do to fix the issue? I have the same problem and nothing I've done has been able to get TP running.

The average winds are the average wind direction and speed along the route loaded. The wind component is the effect of those winds on your aircraft. For example, your 20 kt wind component means that you will have a 20 kt tailwind along your route (on average).

Are you flying the MADDOG 2010 addon (or another complex addon aircraft) or using photoscenery? Using either causes that to happen to me. I have lost all but the T concourse before. I have no idea how to fix but you aren't alone. This is another example of Imaginesim's sloppiness.

I have recently begun having this issue after SP1b. I've noticed that It isn't actually an ETA being calculated but ETE. Take away the z after the time and its enroute time. I have no idea why it started doing this though. Is this an option that is chosen by the operator and in the option files downloaded with liveries?Sheldon Paprota

Thanks for the help everyone. I ran sfc and the first run it needed to pull a DLL from my install disk. On the next run it came up clean. However, I still have the same problem with the NGX. I then admitted defeat and did an upgrade install of XP64 as Ryan said. This also failed and my issues persist. So now I'm at a total loss.Sheldon Paprota

Whenever this happens to me I just use DIR CKPT on the RC menu and choose whatever my next waypoint ahead is.

I meant to say Paul Gollnick, not Paul Deemer

Hi everyone,I've already opened a PMDG issue ticket on this, but also figured I'd post here and see if anyone else has seen this. I get the following message whenever I try to use the internal FSX menu: FSX.exe - Entry point not found "The procedure entry point GetProcessHandleFromHwnd could not be located in the dynamic link library OLEACC.dll." This started happening after i reinstalled the NGX SP1 without first unintsalling (dumb I know) to try to fix some texture issues I was having. I then did 2 full uninstall/reinstall cycles. After a cycle (or a repair install), I can use the internal menu fine with any other aircraft I have except the J-41 which gives the same error. However, after I load up the NGX or the J41 the problem resurfaces and continues if I end the flight and start another with a different plane, including default ones. The PMDG 747-400 does not gives the error. I did some forum searches that turned up nothing and I'm at a loss how to fix this. This problem is making my NGX completely unflyable as I can't use any FSX menus. The plane still functions otherwise though.Paul Deemer from PMDG replied to my ticket with a new installer and thought it was a corrupted file. I did another complete uninstall/reinstall and still have the same issue. I've relied to him and am awaiting another response. I've also tried re-registering the OLEACC.dll file as well as replacing it, with no luck. I'm running XP x64. Any ideas out there?Sheldon Paprota

back up now

It doesn't seem like it, Vic. I usually land with less than half of what the FMC predicts I should.

Wilco A319 LIRF-LIMF

I just noticed that the release date has been pushed back again to April 1st...

Just wanted to weigh in also. I first got this warning tonight. My computer clock is correct also, but in my case the warning persists after multiple restarts of ASE.

Hi,I haven't been able to connect to the weather server with ASA or ASX for 3 days and was wondering if it was down. I'm guessing the prob is on my end since I haven't seen any mention of this on the forums. If thats the case I'm at a loss since my internet connection has been fine and nothing has changed. I attached a log if that will be of any help, my internet connection was active at the time and i do not have a firewall up.

This is exactly what i see whenever I get the TAT issue. Whatever altitude I am it the SAT reverts to 15C causing chaos, also the weather slowly clears, the clouds disappear and the winds never change, but stay at whatever value they were before the problem started. It like ASA stops communicating and FSX reverts to clear weather. I am going to try this fix and see if it works, thanks for the post russert!