Av-Fan

Had my first crash in a very long time. In cruise over southern Germany. Here are the details from event viewer:Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000Exception code: 0xc0000005Fault offset: 0x00000000Faulting process id: 0xd64Faulting application start time: 0x01ccb80ac9116b68Faulting application path: C:\FSX\fsx.exeFaulting module path: unknownReport Id: b839f4e7-2408-11e1-a52f-00241dd9551dThanks again for the great product!

I've only had this issue with the NGX.

I'm not sure how to interpret that pic as I am not familiar with convertor X. Wonder if there is anything they can do about it or if this was done on purpose for some reason.

I was wondering if anyone else has noticed that AI traffic tends to keep quite a distance from the NGX during taxi, holding in line for takeoff, etc. It's almost as if the model radius is set to some huge number, though this being FSX, maybe some other factor is the cause. In fact, I'm not sure if MDL Radius plays any role in FSX with regards to AI traffic. In any event, it's not a huge problem. It's just weird being in line for takeoff and having the next aircraft stopped about 200 feet behind you. Maybe she just needs a bath? :) Oh, and this doesn't appear to be an AFCAD issue as I've seen it happen at quite a few different airports.

Overriding, "not seeing", ignoring - whatever you want to call the limited functionality of the FSX ATC system is irrelevant. The original poster was asking how to best fit the NGX into the FSX ATC system and I offered my way of doing so. No more ATC directed turns to get back on course.

I use FSBuild. It will create a route in both PMDG and FSX formats at the same time. After aircraft selection, I will load the flighplan into FSX. I then will load the flightplan into the CDU (using company route LSK) or enter manually if not too long. FSX ATC will then allow you to fly the plan as entered except near the destination where it will insist on giving you vectors. FSX ATC will of course override any altitude restrictions in the SID or STAR but I guess this happens in real life too.

I had the same issue. Had a heck of a time finding a solution in the manual. However, the amplified procedures on page NP.21.16 seem to be incorrect. Here is how I set up the Air Conditioning Panel: PACK Switches - OFFISOLATION VALVE switch - OPENBLEED Air Switches OFFAPU BLEED - ON After starting the left engine, I turn on its BLEED Air Switch. This causes the DUAL BLEED light to illuminate. I then am able to start the right engine.

Thanks for this!

I agree regarding FSBuild. Very accurate fuel calculations.

I also think the pitch attitude on final is a bit off.

See following link: http://www.smartcockpit.com/data/pdfs/plane/boeing/B737/instructor/B737-FMC_U10.6_Changes.pdf

For me, setting TEXTURE_MAX_LOAD=4096 back to 1024 got rid of the crashes.

Just in case this might help anyone - I apologize if this has been posted or discussed previously. For my system, setting TEXTURE_MAX_LOAD=4096 results in FSX crashing after a while. Setting this back to 1024 and the crashes go away.

I received a Descend advisory the other day while on final at KPSP. I believe it depends on how much of a threat the other traffic is to your aircraft.

Agreed Scott.

RNP is enabled on the current release of the 737NGX though, isn't it?

The approach was in the FMC database. Maybe the aircraft didn't fly it to RNP standards? It hit all the altitudes shown on the approach and stayed pretty close to the course shown on the ND. The only thing I needed to do was enter the speed restriction at HOPLI of 210 kts. Just before WASAK, I hit the APP button. At WASAK, approach mode engaged and the FAC and G/P annunciations were shown on the FMA. Maybe this isn't the same as a RNP approach? In case you can't tell my knowledge of RNP approaches is pretty thin... :) **** EDIT - The product page shows that RNP has been implemented: http://www.precisionmanuals.com/pages/product/ngx.html

Just did a short hop from KPHX to KPSP. Had the aircraft fly the RNAV Y RWY 13R approach. It was very kick arse! Having never flown one of these in real life, I must say it was very cool watching the terrain go by. Aircraft flew it perfectly as far as I can tell. Here's a link to the approach if you want to try it yourself: http://aeronav.faa.g...00545RRY13R.PDF Thanks again PMDG! Matt Zagoren

OK, tried again. This time I entered the approach in the FMS AND hit the VOR/LOC button first. Waited until localizer capture then hit the APP button. This time, G/S armed in FMA. Glideslope was captured and all was well. Not sure which one of these worked. I will mess around some more.

Does the approach need to be selected in the FMS? I did a short flight between EDDL and EDDK to test the APP function. I used the FMS to get takeoff and approach speeds but didn't select the approach (ILS 14L) in the FMS. I have tried the VOR/LOC first then tried APP after capturing localizer. I get the same result.

Thanks for the quick response Robin. BTW, aircraft I was using is the Air Berlin B738WL in case it makes a difference. I understand about the green bar on the button. For some reason, the FMA is only showing VOR/LOC armed but not G/S armed after pushing the APP button.

Many thanks to PMDG for a wonderful product. However, I seem to be having an issue with the aircraft capturing the G/S. I've tried this at a couple of different airports so I don't think it is airport specific. I've read section 4.20 in the FCOM and the aircraft seems to be within the parameters for G/S capture. I've set the aircraft up to capture the G/S from below, on an intercept angle of 30 degrees and an airspeed of 180 kts. Heading mode, autothrottle, altitude hold are all engaged. Both F/D's are engaged. LNAV and VNAV are not engaged. The APP button is armed. VOR/LOC is displayed on the FMA but G/S is not for some reason. Upon localizer capture, the green light on the APP button extinguishes. Again, no G/S display on the FMA. Of course, this leads the aircraft to blow through the glideslope. Thanks again for the wonderful product. Matt Zagoren

Thanks for the reply Dan. I don't remember what the status indicator was showing on the PFD. However, I will try this departure again and take note of the direction in which I turn the HDG knob - I bet this was the culprit! Thanks!Matt Zagoren

Many thanks to PMDG for such a great product! I'm really having a good time flying the MD-11.I'm having a small problem with the HDG Select mode. I have built a flight plan from PHKO to KONT in FSBuild. For my departure from PHKO, I selected the AMERY2.ROWIN departure. In the MD-11's FMS, all looks OK. Because this departure requires a left turn to a heading of 270 (departing from RWY 35) after passing 500' I did not arm the NAV mode before takeoff. Instead, I preselected the heading of 270 using the HDG knob. After takeoff and passing through 500' I pushed the Auto Flight switched and pulled the HDG Select knob to start my left turn to 270 degrees. However, the aircraft started a right turn that I manually stopped after several seconds. After getting the aircraft headed in a north westerly direction, I re-engaged the HDG Select mode by pusing the Auto Flight button and pulling on the HDG knob. Again, the aircraft started a turn to the right that I stopped after passing a heading of 360 degrees. I finally pushed the NAV button and the aircraft then turned to the left and joined the published route.I've done about 12 flights in the MD-11 but this was the first where I did not engaged NAV mode before takeoff so I'm not sure if this is a fluke or if I am not understanding something here.Any help or ideas would be appreciated.Thanks!Matt Zagoren

Nigel,Search the Avsim library using my last name. You'll find documents that will help you determine "generic V-Speeds". In real-life, airlines have takeoff charts / calculations for specific airports and runways that take into consideration numerous factors such as elevation, obstacles, runway slope, runway length, etc. Though hard to read, I have an example of such a chart in my A300 performance pdf showing the specific v-speeds to use when departing runway 15L at Toulouse.Hope this helps.Matt Zagoren