Archived

This topic is now archived and is closed to further replies.

Guest benvanboom

MD11 FS9 Possible issue in the FMC

Recommended Posts

Dear PMDG,While flying online today from LFKB to LFML i had planned to land on RWY13L at Marseille following the OB 5B Arrival.Then a controller came online and ordered RWY 31R for arrival Runway.I entered the FMC and changed the already choosen RWY13L into 31R and also confirmed the STAR again into the OB 5B.When pressing *Insert my FS9 froze.....just like that.....no OOM, no CTD, but just freezes.I went offline, closed FS9 and restarted it, choosing my autosave file from 4 minutes ago.i thought lets try again, maybe the freeze is cause by een scenery issue?I did exactly the same...flew above STP VOR at FL150 and changed the arrival Runway and choose the STAR and again my FS9 Freezes on pressing *insert.I did this four times....every time same issue.Then again started my autosaved file, changed arrival RWY into 31R and this time i choose a different STAR....the OB 5C.Now on pressing *insert all went right and my FS9 kept flying.The OB 5B at Marseille is actually the wrong STAR for RWY 31R.....and FS9 freezes choosing that one.The OB 5C is the right one.......and FS9 keeps on flying on choosing that one.Is it possible that on pressing *Insert, FS9 Freezes when one chooses a wrong STAR?Or is this any other possible issue?In the STAR Page the Arrivals wich are not connected by the RWY of choice are still visable after selecting a RWY and a mistake is easily made.Beside of this issue: GREAT PRODUCT! VERY CHALLENGING! VERY HAPPY WITH IT !Hope to hear from you.Kind regards,Ben

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Do you have the latest update? There was a bug that might be your problem with the FMS and too many runways.

Share this post


Link to post
Share on other sites
Do you have the latest update? There was a bug that might be your problem with the FMS and too many runways.
Hi Dan,Thanks for your answer.yes i have, actually i downloaded the product after the update.So it must be the most current one.Regards,Ben

Share this post


Link to post
Share on other sites
In the STAR Page the Arrivals wich are not connected by the RWY of choice are still visable after selecting a RWY and a mistake is easily made.
Ben,The STAR page is designed to display STARs that are related to the selected runway. However, sometimes the authors of SID/STAR files neglect to provide this information, in which case all STARs are displayed, assuming they are compatible with all runways (actually approaches). As for the LFML provlem you mentioned, I will try to reproduce and see what happens. Are you using the SID/STAR database that came with the MD-11 installation?

Share this post


Link to post
Share on other sites
Ben,The STAR page is designed to display STARs that are related to the selected runway. However, sometimes the authors of SID/STAR files neglect to provide this information, in which case all STARs are displayed, assuming they are compatible with all runways (actually approaches). As for the LFML provlem you mentioned, I will try to reproduce and see what happens. Are you using the SID/STAR database that came with the MD-11 installation?
Hello Michael,thanks for jumping in.i appreciate your investigation.I use the standard Databases, that came with the installation (one install, updated full install version of last week) However i have updated cycles in the Queen (from NavData) that i last updated more then one month ago, so before installing the MD11.regards,Ben

Share this post


Link to post
Share on other sites

I have experiended the same issue on one of my previous flights, freezing PC after changing a STAR.

Share this post


Link to post
Share on other sites

Sure would help if you provided enough information for an effort to duplicate the lockups. If you can duplicate it, then maybe the developers can too then find the problem.

Share this post


Link to post
Share on other sites

I'm having the same problem in FSX since the update. I'll be using the FMC and then suddenly FSX just freezes. The sound continues but I can't do anything. The only way out is to close it down through the task manager.What is the solution, this is driving me crazy!Regards,Martin Neep

Share this post


Link to post
Share on other sites

HiExactly the same happens to me also to day, for the first time.I was just before TOD and I was trying to change the arrival rwy for LIBD, from 07 to 27, after insert, the FMC was freeze and FS9 also. Couldn't get it to work, I have close FS9 from control panel.Airac version is AIRAC Cycle : 0813 (18/DEC/2008 - 14/JAN/2009) - Rev.1 for LIBDMD-11 v1.10.0050 with the update, v1.10.0051.Regards

Share this post


Link to post
Share on other sites

I don't know how to put this, but without any information specific to the problem I don't know how anyone can look for a solution or even try to duplicate the problem. "I'm using the FMC" is pretty vague, were you using the FMC by entering data in the MCDU perhaps changing a STAR? If so, what is the fpln and where were you in the fpln when you tried to change and what were you doing to change it? Come on guys, we all want to get the bugs out but a little more help would be great.

Share this post


Link to post
Share on other sites
I don't know how to put this, but without any information specific to the problem I don't know how anyone can look for a solution or even try to duplicate the problem. "I'm using the FMC" is pretty vague, were you using the FMC by entering data in the MCDU perhaps changing a STAR? If so, what is the fpln and where were you in the fpln when you tried to change and what were you doing to change it? Come on guys, we all want to get the bugs out but a little more help would be great.
OK, FSX has frozen 3 times this evening.1st time I was following a LOREL arrival into EGGW. Tried to repair a discontinuity and then.... nothing.2nd time I was on approach to EGSS. Pressed the TO/APPR page and it froze again.3rd time I'd just departed EGLL. Turning right on a WOBUN2F, pressed DIR INTC, program froze again.This problem wasn't present prior to the MD11 - FSX update.Martin

Share this post


Link to post
Share on other sites

Great info, got a lot more to work with now. Thanks Martin.I am in a flight KDEN/KIND and have edited fpln enroute, added place/distance fix and used GO TO on departure... no random lockups. So now lets look at what makes your installation different from mine: I have the FSX Update for MD11, Vista64, and I am using Norton2009. Have your problems started with the update or did they start later?There's a cause for this, but random lockups in the MD11 know problems right now only deal with LFPG and that will get fixed soon. So lets find this one.

Share this post


Link to post
Share on other sites

I didn't notice the problem immediately after the update. It seems to be getting more and more common, I just can't seem to complete a flight!I've tried starting with the default flight, but to no avail.I'll post back if I find a solution,Martin

Share this post


Link to post
Share on other sites

Ok, I may have sorted it.I loaded the FSX default aircraft (C172). Re-saved the flight and then loaded the MD11. Unfortunately the same thing happened. As soon as I started playing with the FMC, it froze.So, I closed FSX from the task manager and then started again. This time I loaded the C172 again, but didn't select the KLM-MD11. Instead I chose the default PMDG MD11 with GE engines.Now all seems fine. I can't replicate the problem. I flew some circuits, different approaches. Touch wood, it seems ok.Regards,Martin Neep

Share this post


Link to post
Share on other sites

Hi Dan, hi all,Unfortunately, I am experiencing the same problem as described in this thread. Dan, as I don't know what information you are really looking for, here is a summary of what I have done.1. I have planned a flight from YMML to NTAA using the following route YMML DOSEL7 Y59 SY G595 TAF NTAA with NCRG as an alternate. I copy/pasted this string to FSBuild or FSCommander, which results in slightly different .rte files, but both have the same effect.2. I started a new flight from scratch, placing the MD-11 in YMML on rwy 34 and I waited for the initialization to complete.3. Than I opened the FMC and loaded the route entering YMMLNTAA. The route was loaded successfully using either of the flight plans (FSBuild or FSCommander). Now, the interesting stuff starts. I am going to describe two different scenarios, one where the FSX crashes and one, where FSX doesn't crash.Scenario 1 (NOT successful)***********************4. I do a complete initialization on the INIT page (thus, entering NCRG in ALTN, 80 in CI, 310 in CRZ). Nothing else. I than switch to the F-PLN page and scroll all the way down to where I can select RWY04 (when using the FSBuild flight plan) or NTAA (when using the FSCommander flight plan). As mentioned before, there is no difference in either of the waypoints (RWY04 nor NTAA). Selecting this waypoint will enable me to select a STAR and I will change that to a VORD22 approach, using a 3000 MIN PROF and the PONU2M arrival. Upon inserting this STAR, FSX freezes. Screen frozen, sound still available. The only thing to stop this is to kill the fsx.exe process.Scenario 2 (successful)*******************5. And now the successful case. I do exactly the same as described above! The only difference is that I only load the route as described in step 3 but I don't initialize the INIT page as described in step 4. So the only thing that I have done on the INIT page is loading the route. Than I switch to the F-PLN page as described in step 4 and do everything the same way as described there. IT WORKS! I can successfully program the approach to use the VORD22 approach!Now, some additional details. I can always successfully program any approach to rwy04. No matter whether I initialize the INIT page or not. I can successfully program any approach on other airports. At this current stage. I have experienced otherwise though. Currently I am able to reproduce both scenarios at request, so everytime I am doing this, I can reproduce the successful and the unsuccesful case!Here is my current configuration.Windows Vista SP1 64bitFSX SP2PMDG MD-11 using the latest service packsAIRAC 0903FSBuild 2.3.7.5.1FSCommander 8.4.2Orbx scenery for YMML (although I don't think that this matters)Aerosoft scenery for NTAA (although I don't think that this matters)I have playing around for more than 4 hours now on this problem but I haven't found any other clues yet other than I know how to reproduce. If you need more information, I would be more than happy to answer any questions you might have. Maybe I could install some sort of debugging program that would give you more information. I can also say that a colleague of mine has experienced this on other airports but the results are always the same. As soon as you start changing anything on the approach, sometimes it works, sometimes it doesn't.I hope, I could give you some more details and I would be very happy to hear any comments from your side! Thanks for your help!Kind regards,MarkAn additional note. I have tried the scenario as described previously in this thread, by loading a default aircraft and than the MD-11 again. This had no effect. The results were the same as described in my last post. It doesn't matter either, if you are loading the 'default' PMDG MD-11 or a custom painted MD-11. So, if I had to answer your question regarding loading the KLM MD-11, my answer would be, 'yes, I could load any other PMDG MD-11, but the result would be the same'. If you know, what I mean ;-).Regards,Mark

Share this post


Link to post
Share on other sites
Ok, I may have sorted it.I loaded the FSX default aircraft (C172). Re-saved the flight and then loaded the MD11. Unfortunately the same thing happened. As soon as I started playing with the FMC, it froze.So, I closed FSX from the task manager and then started again. This time I loaded the C172 again, but didn't select the KLM-MD11. Instead I chose the default PMDG MD11 with GE engines.Now all seems fine. I can't replicate the problem. I flew some circuits, different approaches. Touch wood, it seems ok.Regards,Martin Neep
I also had a problem in FS9 with the KLM passenger livery with a lock-up and computer freeze shortly after take-off from LIMC. Testing with other aircraft indicated it was an MD11 problem and choosing another livery on the MD11 showed it to be the KLM livery. Incidentally, at the time of the lock-up I was not doing anything on the FMC.Iain Smith

Share this post


Link to post
Share on other sites

I just experienced the same thing this time on arrival in JFK. CAMRN STAR for ILS22L, then change of the rwys for ILS31R; upon inserting ILS31R total freeze.Happened prob once or twice before, not sure where though.FS9.1 PMDG MD-11 (can

Share this post


Link to post
Share on other sites
I just experienced the same thing this time on arrival in JFK. CAMRN STAR for ILS22L, then change of the rwys for ILS31R; upon inserting ILS31R total freeze.Happened prob once or twice before, not sure where though.FS9.1 PMDG MD-11 (can

Share this post


Link to post
Share on other sites
I just experienced the same thing this time on arrival in JFK. CAMRN STAR for ILS22L, then change of the rwys for ILS31R; upon inserting ILS31R total freeze.Happened prob once or twice before, not sure where though.FS9.1 PMDG MD-11 (can

Share this post


Link to post
Share on other sites
Ditto for me. I also seem to get a consistent CTD when trying to enable my alternate destination...
Hi All!Last night my MD-11 froze for the first time, when i tried pressed ALTN from lat rev...I had an engine failure and wanted to land to a close airport. I hadnt put alternate airport from the beggining , so i just put it at that time and tried to press switch to ALTN...i dont quite remember all my steps but that was genrally my move..FS9 froze...no blue screen or something, just froze...Of course it did it again when i tried loading the flight.....

Share this post


Link to post
Share on other sites