mvwissen

No worries, John. I already figured out that you meant me when calling me Mike ;-). I have been called a lot of other names in my life, just not Mike up until now ;-).Mark And again some more information. If you omit step 5 or enter the values partially (either CRZ or CI), inserting the VORD22 will work as mentioned before. As soon as you provide those missing values, after having inserted VORD22, FSX freezes upon entering the CRZ and/or CI values. Very interesting.

Hi Dan again,Bruno and I did some more research in the meantime, this time trying to eliminate as many steps as possible to reproduce the error. Here are the steps performed to have FSX frozen.1. Started a new situation from scratch again using default PMDG MD-11 in YMML on rwy 34.2. Opened up the FMC and switched to the INIT page.3. Entered YMML/NTAA in the FROM/TO field.4. Returned to F-PLN INIT by pressing LSK6R (thus NOT by selecting the offered YMMLNTAA.RTE prebuilt flight plan).5. Entered 310 in the CRZ field and 80 in the CI field.6. Switched to the F-PLN page.7. Selected NTAA to programm the approach.8. Selected the VORD22 on the STAR page.9. Entered 560 in the MIN PROF field.10. Pressed the LSK6L to have the approach inserted. FSX froze again though!!!Now, when omitting step 5, everything works. You can even enter either the CRZ level or the CI and it still works (just not both values). We observed also that the virtual waypoints 'T/C' and 'T/D' only appear if you enter both fields as described in step 5. But I am sure, you already knew that. I just wanted to point this out. Maybe it has an influence.Mark

Dan,I just did the following. Started a new situation from scratch in YMML using the default PMDG MD-11. Than opened the FMC and started a new route by entereing YMML/NTAA in the FROM/TO field, thus NOT by loading a prebuilt route by FSBuild. I completed the INIT page by executing the following steps:1. CWC168 in the FLT NO field2. 310 in the CRZ field3. NCRG in the ALTN field4. 80 in the CI fieldThan I switched to the F-PLN page and selected YMML to program the DOSEL7 departure on rwy34. All worked fine so far. After that, I selected NTAA to program the PONU2M STAR for the VORD22 approach. Upon pressing the insert button, BANG. FSX froze again! So this time, no route entered at all.Now, here comes the big question! When I do the same, without completeing the INIT page (omitting step 1 to 4), than everything works fine!!! Now the question to you? Did you complete the INIT page or not? If not, than this would explain why it worked on your side.It really seems to me that this entire behaviour is somehow linked to the INIT mechanism, as I already described in my initial posting.Kind regards,Mark

OK. Here we go with the route.HOPLA DOSEL7BEATO DOSEL7RIDAL DOSEL7DOSEL DOSEL7EBONY Y59 ARRAN Y59 NONUP Y59 CULIN Y59 TARAL Y59 RIVET Y59 SY 112.10 Y59 DIPSO G595GOVER G595ALLOC G595VARLY G595WARTY G595DONNA G595SARAP G595IGLET G595MUGEN G595NISET G595MALNI G595NIMOD G595ODUTI G595PAVSI G595 RAXER G595 SABUB G595 TAF G595 NTAA DCT I was going to use the VORD22.PONU2M approach.Mark

Hi Dan,Here are the files mentioned in the previous thread. I hope that they are enough to reproduce the error on your side. Otherwise, let me know. Of course, you need to rename the YMMLNTAA.txt file to .rte. I was not able to upload it with the .rte extension.Thanks for your help!Kind regards,Mark

Hi Dan,I will send you the flightplan (YMMLNTAA.rte) and the SID/STAR (NTAA.txt) file that I am currently using, in no later than two hours from now. Would those two files be enough for you to reproduce or do you need any other files?Regards,Mark

Thanks for your help. I really appreciate any hint. Switching to the Cessna and than back to the MD-11 has already been done. No success though! Now, regarding the 2GB switch. I was under the impression that FSX SP2 took care about this problem. I also installed a litte piece of software where I was able to check if that switch was really set. I can't recall that option name within fsx.exe anymore but it said that fsx.exe would support more than 2GB (after installing FSX SP2). I have 8GB of memory, so this shouldn't really be an issue. Since I got rid of Bit Defender 2009, all my memory issues were resolved. No OOM's anymore ;-)!Mark

Hi Leffe,Thanks for your suggestions. Here my thoughts to your thoughts ;-).

I am posting a new topic, in the hope to draw PMDG's attention to this problem. Dan, I hope, I can give you some more details on the FMC problem, that causes FSX to freeze when changing an approach in the FMC. So, here is what I responded in threadhttp://forums1.avsim.net/index.php?showtop...p;hl=freeze+FMCHi 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

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

Hi all, hi PMDG,Is anyone of you guys experiencing the follow behaviour? After having started the MD-11, it sometimes starts to jump on the ground. It does one single jump just a few inches of the ground or so and you see the touchdown smoke as well, when it hits the ground again. This behaviour continues sporadically. Let's say, maybe 2-4 times a minute. It usually happens when changing views and gets less (I mean 1-2 times every 5 minutes until it disappears most of the times), when remaining in any particular. So, yes, it happens in any of the views and changing them doesn't make things better. Unfortunately, I can't really provide any screenshots, because by the time I hit that 'print screen' button, the airplane is on the ground again. Maybe, I could capture it on video, if I knew how.Anyway, I was wondering, if anyone else experienced this behaviour, cause it's driving me bananas!I have installed FSX SP2 and PMDG MD-11 with the latest patch.Any hints would greatly be appreciated.Thanks and regards,Mark

Hey John,If you want to enter ILS frequencies into PMDG's 747 FMC, then you need to supply the runway heading, which can be retrieved from any ILS chart. Example: 112.45/184.Mark

Hi guys,With the 747-400 I was able to save the position of the EICAS window. Everytime when I startup a saved situation, the EICAS window would be displayed at the last saved position. This is not the case with the 747-400F. It always shows up at the default position (on left side of the panel). Can anyone tell me, how I can save the position or what file I need to modify to specifiy the initial window position?Best regards,Mark

Dear Robert,Unfortunately, I am experiencing the CTD problem aswell, since updating to Version 1.1. I have followed the forum for quite a while now and I was wondering, if PMDG is still investigating the CTD matter, although it obviously affects only the minority according to an initial statement from your side. From what I understand, PMDG is not necessarily focusing on the 747 package itself but maybe a combination of all add on's and the 747 package. But, after reading this statement from you ...'In ALL CIRCUMSTANCES we have found that users have an unending stream of junk installed with FS- and that this triggers CTDs when using higher hend simulations that tax the capabilities of their system and/or MSFS. If you have taken the time to read through the suggestions we make- and you feel that they will not work- then we are unable to assist you.'... I am not sure anymore, if PMDG is still working on the CTD problem. Or maybe, I just understood it the wrong way. Well, I must admit, I also have installed quite a lot of add on's but they are all genuine products and mostly scenery products besides the most important stuff (such as FSBuild, ActiveSky, FSUIPC, ...). I don't know, if I should go into details right now.I have read your post about removing and reinstalling the 747 and I have followed your instructions exactly. No success however. The CTD's still occur. I have also discovered that when I start the 747 cold and dark (via the provided 'PMDG 747-400 Cold and Dark KPAE.sav' file), the 747 works fine. Until I press the battery button. The screen turns black and after a short while, FS2004 crashes.I haven't done any indepth research yet (and I don't even know, if I am able to do that for such a complex piece of software) but I would be willing to help.But most of all, I would like to know, if PMDG is still working on this issue.Thanks for letting me know.Regards,Mark

Hi there,I have made the HB-IIR, but I must say, I am not a real expert in creating liveries. Although, I like it and fly it regularly. I never uploaded it though. Interested? Drop me an e-Mail and I will send it to you.Best regards,Mark