mike2060

It can still be useful for a jet on approach. I imagine it is a bit harder landing with the windshield full of rain.

RID5 works for me with AIRAC 1402. In the "Route" section, DO NOT put the departure and destination airports. Your route should look like RID5 SOT.DIRTY1. Enter KDTW for the Orig. and KATL for the Dest.

The latest version is working very nicely but I haven't played around with it too much yet. I like how the STAR assignments can change after the ai is assigned a STAR already. I received this error today, and I have received it before with the past couple versions. Each time it has happened with a new .ini file: https://www.dropbox.com/s/wxr7ftwokvzyc76/aisidstarerror.png I just remove all the default airports from the .ini that come with the program and all is fine but I don't get why I encounter this error. I got it on maybe the fourth time using the new version of AISIDSTAR.

I would assume you'd still use a yoke/joystick. It would be best just for just buttons and switches I think.

I expect sometime in the near future you will be able to use your hands to click virtual switches on and off, etc. Sort of like Microsoft's Kinect.

The problem with that theory is the initial turn off course was programmed in before the sign off with Malaysian ATC. Since it would show on both PFDs that means either both pilots were in on it, one had killed the other, or there was a highjacking. I don't think they could have both fought to the death. And for the people who say that programming in an alternate in the FMC is sometimes done, it doesn't make sense that it's done once they reach cruise. Why wouldn't they just do it on the ground so if they experience an emergency while climbing, they'd have a quick way of turning back?

Sometimes it works flawlessly. Other times it is all wrong and stays that way. But when it works it's great.

This theory has been debunked countless times already.

One in 45 million chance of dying in an airline accident in USA according to this: http://www.nytimes.com/2013/02/12/business/2012-was-the-safest-year-for-airlines-globally-since-1945.html?pagewanted=all. Flights simulators have been around forever so not sure why this would change anything.

How many Americans may have died on MH370? Three I think? flight sims aren't going to be banned. American government couldn't care less about the other 236 people who died. 9/11 thousands died and billions in damage and flight sims weren't banned. Anyways, terrorists could just go and get a 777 type rating and be all set.

Oh god. CNN is talking about flight simulators again. I can't stop cringing and face palming. They think flight plans take up a lot of "memory".

The plane made a greater than 90 degree turn later in the flight.

That theory was maybe valid for the first 24 hours after the plane went missing. Now it doesn't match up with any of the facts.

Well, flight training wasn't banned after 9/11 so I wouldn't worry too much :-p

I tried again and I got the monitor working. I still oddly got an aircraft assigned RW05 STAR when the wind was 320 magnetic at 20kts at a smallish airport. There is a RW32.

Would they even have the knowledge to look at the log book? Or even the saved game files or .PLN files?

The AISIDSTAR Monitor doesn't seem to be working for me. I press Start Data Collection but I never get anything to show. It used to work for me, I am not sure what is wrong. I am starting with everything new and the latest release. Also, when I first started AISIDSTAR.exe it gave me a bunch of errors for almost all of the airports that are included with AISIDSTAR. I had to delete them in the .ini. I have also witnessed some behaviour where the AI will slow down and speed up every few seconds on final approach.

It would be saved in Logbook.bin and he may have .PLN and .FLT files.

I agree but they should check it out anyways.

They should be checking the Captain's computer. He was an avid simmer and if he had something to do with this, maybe he practiced it? And if he did, they would know if and where the plane landed.

Great, thanks a lot. I flew a bit and at least at CYYZ with a ton of traffic and CYUL with a lot of traffic the planes were flying the correct STARs.

Well I probably spoke too soon. At CYHZ the AI were landing RWY 23 yet some aircraft were getting assigned STARs for RWY05. Any idea why?

The program seems to be a lot better since the last time I used it so good job. I noticed that sometimes AI on final will drop suddenly to get on glide path. I assume this is because they finish the STAR at an altitude that is too high for the final approach and they never get a signal to descend to the proper altitude. Is there anyway to use the approach section of the PMDG navdata to find the approach altitude so that at the end of the STAR they are told to descend? So say the STAR's last altitude restriction is 3100 feet but the ILS approach has an intercept at 2600. When the AISIDSTAR hands the AI over the FSX, it tells it to descend to 2600. Not sure if this is viable at all, just throwing it out there. Maybe they do descend already but I seemed to notice that sometimes they were high.

I have tried that but it doesn't work.

Thanks, I just tried it but unfortunately didn't help.