January 29, 201214 yr Hi I'm Emil Nilsson.I was making a flight between Arlanda and Gatwick with Virtual Norwiegan on Vatsim earlier this day. The flight is going perfectly fine until I got a "proceed direct KOPUL". I went to the FMC, then LEGS, then i took the "KOPUL" waypoint and put it at the top of the LEGS page. I noticed that when I pressed in the waypoint over the original one, the "execute" button did not light up (it didn't respond.) I pressed "execute" and the waypoint popped up at the top of the LEGS page, but I noticed that the speeds and altitudes to the right of all waypoints were not there anymore. And when I looked on the ND display, the route had moved to KOPUL. But the aircraft didn't turn. 20 seconds of heartattack after that, London control tells me to contact him. I pressed "SHIFT+4" to get to the radio stack. But when i tried to type in his frequency, nothing happened. It was like the whole NGX just hanged EVERYTHING. I went to the spot view to look at the aircraft. I noticed that there were no engine blades. I decided to disconnect the AP and turn the plane manually but it didn't react to my joystick inputs. It just kept its course and altitude. Suddenly I noticed a slight pitch forward and the second later i was overspeeding and pitching about 10 degrees down. When I pulled down the thrust levers to zero I heard the engines do the same. At this point i knew my aircraft was really messed up. I went into the default menu bar and then to aircraft and failures. I looked through the whole failures pages, but found nothing. I pressed "reset failures" to be sure. When i came back to the cockpit it was the same. London control was still demanding me to contact him via chat. I couldn't do anything, I had to disconnect from VATSIM. I closed FS almost so angry that I could throw my computer out the window. I later took a look in the kACARS, this is what it said:[14:05] - Climbing to TOC[14:24] - TOC reached[14:24] - Cruise started[15:41] - Overspeed! 472kts, 36375AGL[15:41] - Overspeed corrected at 36421AGL[15:42] - TOD reached[15:42] - Descending to destination[15:43] - Simulator Paused[15:43] - Mid Air Refuel! 30325AGL[15:43] - Gear down at 30325AGL[15:45] - Landed at -1575fpm. With 3143kgs of fuel onboard and a pitch angle of 1deg.[15:45] - Simulator Un-Paused[15:45] - Taxiing to Gate[15:45] - Gear up at 0AGLAs you can see, the gear went for some reason down at 30000ft without me noticing. No sound, I didn't even press G! And you can also see that I touched down at -1575ft per minute.. How is that even possible when I see the NGX at 36000ft?Please help me! :)Regards/Emil Nilsson
January 29, 201214 yr Hi EmilAs Gatwick is my "home" airport fr the VA that I use, thought I would try and help you, but in my opinion this is very difficult in a one off computer sieze up that you seem to have. Finding these kind of issues are often easier if they are repeatable and happen often. It is very frustrating when you lose a flight at the end, but that is the world of computing. I doubt anyone could solve your issue from what you have said here...for example is it a computer hiccup, or a 737 hiccup. I would suggest making the flight again perhaps off line and see if the issue is repeatable, if not then just chalk it up to experience and move on. If it becomes repeatable then there are many knowledgeable guys on here that can help you solve it. Sorry I could not be any more help, but we all lose flights every now and then and never find out why, the only satisfaction we get is screeming at the computer.Kind RegardsJohn Calleja (Armchair pilot) John Calleja
January 29, 201214 yr Commercial Member Try flying WITHOUT all the other stuff running and see if it still does it. Note that you might have to edit dll.xml to stop them loading (backup first).It seems there is a conflict somewhere and the NGX and something isn't playing nice.Best regards,Robin.
Create an account or sign in to comment