Captain:

I appreciate you letting us know that the issue is being worked on.  I have submitted a support ticket on this issue, and was not happy with the outcome.  I think it is unacceptable for you to say that we will have to wait for 4.3 to come out spring of '09 for a fix to this.   MOST of us have paid around $80 for your product and cannot use the product as it's represented without it crashing to desktop.  Whoever is working on this needs to find out what is causing it and produce a patch to fix this FMC issue much before Spring '09.  

I hope you can understand the frustration.  If you purchased a product and expected it to work as represented and it doesn't, which causes you not to be able to use the product and then the manufacture says....sorry can't help you till we release another update 4 or 5 months later.....I'm sure you won't be very happy about that.      

Point is...The support team needs to get this fixed asap, and we (the customer) do not expect a representative to tell us sorry...you will have to wait for a full update to be released.

Thank You.


Captain Sim wrote on Dec 15^th, 2008 at 10:49pm:

Well I've just spent a couple of hours re-installing FSX and testing. The 757 crashed within 10 minutes of the first test when I changed the approach. The bug is in the FMC coding, not FSX.

CS,

After reading your answer I am thinking CS is not getting the full scope of the issues.

Some like me, where under the impression, if a trouble ticket was submitted then the issue is known. However, I see now from your post that even if the issue is known, that CS is counting the tickets to see if maybe it is a major issue.

Based on that response, then I am submitting tickets even if it was reported by someone else.

As an example, the RAT, even though it does not affect flight is an issue with many.

The Rocking back and forth is another.

Now finally this one described above 

Regards

I just purchased the 757 and on the first flight that I made, on the very first change to the FSM flight plan (I added a missing crossing restriction on the OLM5 approach into SEA) I got a CTD.

I then started reading the forums and saw how many people have this problem. I have no patience to deal with this kind of problem on every flight.  I will try this a few more times, but if this continues, then it is into the hanger for me.

Eric,  done....this happened again 2.5 hours into a 3 hour flight.  I simply changed the runway from 35L at KDEN to Rwy 26, selected FUZZZ intersection, tried to close the discontinuity and bam, CTD, game over.

I have had this problem on all flights but one so far, and that one I had the AP not disconnecting problem.

Oh, and changing to FSUIPC 4.3 didn't help me with the AP disconnect problem.  Into KSEA at 200', I disconnected the AP, had no controls and the aircraft landed itself at -600 fpm .  I reinstalled FSUIPC 4.3 and was going to try it out again on this flight...but....CTD

Beachdog2001 wrote on Jan 6^th, 2009 at 4:01am:


Yeah, I've tried everything too. The problem is with the FMC code. I suspect the customers who don't have this issue don't use the FMC fully and don't do things like switch runways or insert crossing restrictions.

This issue was reported so long ago that I can't remember if I created a ticket or not. I too assumed that since CS was aware of the issue that they would fix it. I'm starting to think they can't or won't for whatever reason.

Yeah, I was thinking about some work-arounds. Perhaps not entering the runway/approach until you know what it will be for sure. And just don't use vnav for descent and manage it yourself. It's kind of a drag because that's what the FMC is for, but until they fix it, this might work.

Also, I've been wondering why some people don't get this crash. The people who are crashing are you using lbs or kg? I'm curious if that could be a cause. I've tried both PW and RR variants and it makes no difference.

I could be chasing my tail here, but until CS fixes it, I'm very frustrated. They won't return it, because I had good faith and have waited for a fix, so it's been too long now. I'm stuck with a very broken airplane.

Slowdive wrote on Jan 13^th, 2009 at 8:10pm:


I still think you are exactly right that perhaps the majority of purchasers load up the airplane, firewall the thrust, and fly VFR.  I actually bought this to train for checkrides/recurrents at my airline, and boy was it a mistake!  Once again, beautiful outside, but as it is at the training academy, you can't see the outside, just the cockpit, and you live in the FMC.

Until there is a fix, which may be asking too much because they would need to completely redesign the FMC/AP system, the another company 767 will be my aircraft.  I think CS even advertising that this thing has a "full FMC" is sad...

Don't get me wrong, terrific attempt at a sim, but fix the darn thing!  It is unflyable as a commercial aircraft, only flyable as a big beautiful C172.

JB