I've just installed FS2Crew again for the PMDG 738. I've tried 2 flights from KLAX to KEWR and it CTD both times, at the same place in the flight - about 150 miles out from TOD with the IN RANGE window open.Are there still problems with FSINN, PMDG and FS2Crew?

Hi Terry,If FSINN was the problem, you probably would have experienced the CTD much earlier in the flight, usually around takeoff (I say probably because I'm not at your computer to see how you're using the simulation).My suggestion is to fly in a totally different area (like Asia) to ensure that the CTD is not related to a scenery issue.Let me know how it goes.Chrs,Bryan

Hi Bryan:Well, I created a new flight plan from KLAX to KEWR (thought it might have had a bad waypoint) and tried it again, this time it CTD about 1/2hr into the flight.I was going to try it with Radar Contact but I was getting numerous key conflicts. I can't fly with SB3 - doesn't work on my system for some reason (I'm running a wideFS system) so I have to use FSInn which, btw, is a pretty good program. I ended up deleting FS2Crew and flew the KLAX to KEWR flight again but this time no CTDs.I was running FS2Crew, FSInn 1.2, AS6, FSPassengers, PMDG 738, FSRealtime. Again this is a wideFS setup.Any suggestions?

Hello Terry,It's a tough one.Re-install FS2Crew 737 but uninstall FSINN.See what happens then.-Bryan

Well, upgraded my firmware for the router and now I'm able to get SB3 working again. Strange as the router isn't new and SB3 did work at one time. Anyway, deleted FSInn, ran SB3 with the PMDG and FS2Crew and no problems so far - knock wood -. That was from KEWR to KSFO. I'll try the KLAX to KEWR flight soon.Too bad too, FSInn is a better program IMO.