I dont know if anyone else is seeing this or not, but if they are I'd like to know..Over the last couple mof days I've run test flights using the hotfixes as they were issued. Now, the way i fly is probably not correct according to the book.. I disconnect the AP and autothrottle before I land. What i'm seeing is this..If I disconnect the AP and autothrottle, but leave the AP disco klaxon alone, the plane flies correctly and can be hand landed. However, If I turn off the warning klaxon by clicking on the AP Disco warning light, the plane refuses any more input from any controller ( joystick or keyboard ) and crashes..Is anyone else seeing this??Pam

HI Pam, Noticed a couple of approaches where I turned off the AP alarms, as you describe, ac veered to left. NO response to yoke until full control deflection to right, resulting in sharp bank in that direction. Go round needed as alignment with runway completely blown. Kevin Kyle

I had something similar happen to me. I turned off the AT and AP to land manually and in the very second the main gears touched down a yellow alert light came on on the front panel, the controls locked and all the other usual panel freeze symptoms ensued. So nope, even hotfix #3 didn't fix the panel freeze issue. If anything it seems to happen more frequently now.

Thanks Guys..I'm going to ask you to run one more test.Fly it again, only this time, dont turn off the alarms. Just hit Q to silence the sim.. My guess is that you will be able to complete a normal landing.. and once stopped, can turn the alarms off without there being any negative effect to the control inputs..As you can tell, i'm really suspicious of those alarms.. The above recommendation works on my machine ( leave the alarms alone and land ) but it consistently breaks if i turn them off..Thanks..Pam

Tried the approach both ways, alarm on, alarm off. No control problems either way so problem, for me anyway, is intermittent. However, on 2 occasions out of last 4 landings ac suddenly veers sharply off the ILS on final, yet it allows me to steer it back... all without disengaging the AP. I'll keep try and post here if I have anything new.

I also noticed FPS drop in the VC. Bought 5 to 8.

Thanks Guys.. Your awesome..So we have Three machines, with what appears three different problems but all related to the same subsystem.. I've also had the ILS ( so I thought ) yank my plane to the left, from 10000 feet because the plane didnt descend at T/D. But that was in the first release of the hotfix. Its only speculation, but i'm wondering if we arent all seeing the exact same problem manifested idifferently because of the base differences in our machine. I'm running windows 7 ultimate with 8 gigs of ram, and twin GPUs strapped together for another 1.somethiong gig of video ram, and 500 some cores of processing power since i'm running Cuda drivers in the background which use the GPU as paralell processors.. I'm also running the 170 version of NVidia's drivers and not the latest ( for a good reason ).Now, when i disconnect, I'm still five miles out as i hanf fly the landing all the time. The ILS doesnt have the opportunity to grab the plane and pull it off course.. Or rather, the plane doesnt have the opportunity to grab the ILS and pull itself off the heading.. It still thinks its headed right for it when i hit disco.. However, if part of the navigational subroutines doesn't recognize that they have been disconnected, then they are going to continue to behave exactly the way we are seeing.Its all about control.. Which subroutine is in co0ntrol at what point.. For mexample, your in VNav, but you need to descend quickly, so you hit flch.. FLCH appears to have control, but really whats happening is that VNav is silently looping in the background waiting nfor FLCH to pass control back to it. So, now with the AP disconnect, VNAV Passes off control to wht?? The Alarm lights, because as far as its concerned thats the next subroutine to take control. But as soon as you turn off the alarms, you turn control back over to VNav, even though you think you disconnected it, because some subroutine in there is orphaned and unaware thats its supposed to be dead.So why nis this only happening on some machines??Theres also some graphics and redraw issues going on there as well as we've seen in other posts with skeleton planes and horrible frame rates, but i cant perceive how that ties in, even though i know that somehow it does.. I know i must sound completely insane, but like everyone else, I'd really like to see this thing fly right, and with three unsuccessful hotfixes perhaps its our turn to do a little homework and offer up our findings as an aid to the programmers. And yes, i'm a developer, but no, I'm not a coder.Talk soonPam

I dont know if anyone else is seeing this or not, but if they are I'd like to know..Over the last couple mof days I've run test flights using the hotfixes as they were issued. Now, the way i fly is probably not correct according to the book.. I disconnect the AP and autothrottle before I land. What i'm seeing is this..If I disconnect the AP and autothrottle, but leave the AP disco klaxon alone, the plane flies correctly and can be hand landed. However, If I turn off the warning klaxon by clicking on the AP Disco warning light, the plane refuses any more input from any controller ( joystick or keyboard ) and crashes..Is anyone else seeing this??Pam

Just do me a favour chap, when you get time of course, set up an approach and leave everything on A/T & AP watch what happens. please report back "don't disengage anything

Excellent suggestion Steve. I'll make two runs. One with weather on and one with weather off, because ive seen weather mess with my planes before in a very dramatic and annoying way.

Tried your suggestion. Used the Leena4 approach to LAX.. The approach as it is in the database brought me in diagonally to the airport, and I missed the tower by about a hundred feet. the plane landed on all three wheels but i wont call it correct because i was still traveling diagonally to the airport.. On Touchdown,I disconnected A/T and the panel completely froze and refused all control inputs. However, after hitting the AP disconnect switch, I could still turn on the AP light even though it had no effect. ADI HSI everything was frozen. Moving the joystick had zero effect, moving throttles the same..i'd swear that once vnav is engaged and your in a descent, it stops listening to anything else thats trying to talk with it.. Disconnecting the A/T or AP simply takes away its ability to do what its supposed to do, but it still ends up in a loop and refuses to relinquish control..

i just did the same flight a second time only this time, I used LNav, flch .I programmed the radios as usual for the ils beakon, and began a manual decent at the T/d. I also switched over to App at SLI as i came up on final ( still diagonal ( grrrr ) ).. I switched off the A/T at a thousand feet, and the Ap at 800, and maneuvered the plane to land on the runway this time.. on "touchdown" the aircraft veered heavily to the left, and all directional controls were frozen, so was the MFD and the PFD as well as the backup instruments.. The Brakes however, worked fine, and i was able to NOT hit any buildings as I coasted around 9in a circle trying to stop..

Has anyone installed hotfixes? At this stage I have not because reading other threads the hotfixes seem to be confusing the issues. I am not installing any of these yet, just waiting until some of the many issues are resolved. Just a thought!

Has anyone installed hotfixes? At this stage I have not because reading other threads the hotfixes seem to be confusing the issues. I am not installing any of these yet, just waiting until some of the many issues are resolved. Just a thought!

yes, we have installed the hotfixes.

On the release version I never experienced any freezes or lockups. The first Hotfix gave me an irrecoverable freeze/lockup when I tried to set departure runway in the DEP/ARR page of the CDU. The 16th Aug Hotfix then gave me a freeze/lockup as you guys have described; AP/AT disconnect and warnings cancelled. Not having warm feelings about these Hotfixes! Specs: Win XP SP3 32bit, Core2Quad E9650 3.0Ghz, 4GB DDR2 RAM, 8800GTS 512 G92 Thanks.

And our system is still quite a bit different than anyone elses here and yet with the same errors appening at the same point..The more I think of this the more i think theres a syntax error in the VNav subroutines..