Jump to content

johndrago

Frozen-Inactivity
  • Content Count

    372
  • Donations

    $0.00 
  • Joined

  • Last visited

Everything posted by johndrago

  1. Were all the discontinuties fixed from the legs page?- John
  2. This may help:http://forum.avsim.net/topic/353283-fms-and-loading-panel-state/page__p__2155858__hl__fmc%20loading__fromsearch__1#entry2155858
  3. I have seen this issue as well since SP1b. I never had it happen before. I "wiggled" my CH pedals a little, and tried a few times, and then it stuck. Not sure if the logic changed for the brakes in the update.John
  4. I can confirm this as well. Didn't cause a problem, but I noticed that it wasn't working the way it was described in the release notes.Thanks,John
  5. I've seen this on other planes (747x, LDS 767) as well. Don't know if it's real or not. John
  6. I know this may be premature, but what will the install be like? Will we need to uninstall liveries or panels states again?Thanks for this excellent product!John
  7. Hi Paul,Yes, drag required did show up a few times, and I did deploy speed brakes. It seemed to be excessive. Thanks for the link, I will give it a read.John
  8. HI Guys,I need some help. For the last few months, I've been flying STARS and SIDS using real world charts and flight plans. I've learned what I could about the charts from reading online, but I still have unanswered questions, to which I can't find a "real" tutorial anywhere.So far, I've had pretty good success using STARS, and programing the FMC with the proper altitude and speed restrictions. Last week, I tried to take a real world flight that I've been on many times. It's KSMF to KBUR.The flight plan is FROGO6 FRA REBRG DERBB CEEME1. So, I read the CEEME1 STAR, created the flight plan in FSBUILD, loaded it, and took off. Once in cruise, I went to the LEGS page, and added any restrictions for the approach. VNAV did what it was supposed to do to hit each waypoint properly, however, there were some that were just to hard to make, and this pushed my approach back so that I was too high by the time I hit FIM and ready to intercept the localizer. It wasn't the NGX's fault, or the FMC, I'm sure it was the flight plan and how it was programmed by me. I tried it twice, with the same result.So, my question is this. Can someone who is experienced with using RW STARS and programming the restrictions in the FMC let me know how they would have programmed the FMC with this flight plan and approach so I can compare and see where I went wrong?I've attached the CEEME1 STAR to this note. Any help would be appreciated. I just can't figure out where I'm going wrong, espeically since I've flown so many others correctly.Thanks in advance!John
  9. Hi Guys,I've been flying the NGX since release. Everything has been pretty smooth for me without the initial hotfixes. I did the upgrade to SP1, and I have the expansion pack for the 600/700. Again, all went well. I've taken several flights now with the 700, and all of a sudden today, something strange started during engine start.When I start the engines, the spool up process goes normal, the displays look normal (see screenshot), but after the engines settle into idle, both of them start to spew smoke (see screenshot), and my throttles (although moving fine visually), don't have any affect on the speed. I can shut them down, restart, and the same thing happens. I don't have any failures active (see screenshot)I follow my checklists. Again, I have been flying this plane since day one without this problem. Each flight is a fresh flight from cold and dark. I don't use saved flights. Per PMDG recommendations, I load the plane from the FSX menu each time.I've tried this 4 times in a row, each time closing FSX and restarting to make sure it's fresh, and it keeps happening.Any help would be greatly appreciated!Thanks,John
  10. It's not a matter of distance, but when it's live on the PFD. Once the needle begins to drop, gear down, flaps 15, and arm APP mode.- John
  11. I can't get the carts to come with the fmc either. John
  12. Same problem here. I did an uninstall, and a reinstall. I removed my old panel states, and .ini's before the re-install.- John Update: If I undock the FMC from the VC before I load the ColdDark panel state, it works. I can then dock it back, and I still have control over the FMC. - John
  13. HI Robert,Quick question so I do this right. I've never installed any of the hot fixes. I'm still running off the original base package from August. Do you recommend that I uninstall and download the new base package with SP1, or just load SP1 over my current install?Thanks!John
  14. Looks like you have a 68kt tail wind. Most likely a weather related over speed. Fsx is good at that. John
  15. Not only does the aircraft have to be setup properly, but to arm VNAV on the ground, you need the Collins MCP. From what I've read, arming VNAV on the ground is also a new feature of the 10.8 FMC software. If you search for "VNAV takeoff", you will find a couple of threads that have already gone over this. I arm it on the ground for every flight, and have never had a problem. - John
  16. These guys have a good unit as well. I've been cooling my i7 960 4.08 fine with, even when the ambient air temps went up in the house during the summer. http://www.coolitsystems.com/ The eco alc unit is affordable and good. - John
  17. Thanks Ryan! That was one of my tickets since the release on week 1. I appreciate it. John
  18. This has been reported since the release of the ngx. PMDG knows about it. John
  19. I have had this happen to me once so far as well. I was not flying online. John
  20. Are you loading from a saved flight, or a fresh flight? - John
  21. I had the same problem. The fix for me was to turn off the auto-CRS feature. John
  22. I've flown the NGX since it's been released without any issues. Today, I experienced the first panel freeze. The VC was still active, but the panels and AP were frozen, and the aircraft was not allowing any control input. It was just stuck in a straight line heading toward the ground. The only thing I did different today than all the many flights I have taken is adjust the FMC to a new runway when on approach. I don't know if it had anything to do with it, but so far, I haven't had any problems with the NGX. I know many people have written about this, but I'm just noting what I did in case it helps solve it for PMDG. Thanks, John NGX v1.0 (no hot fixes)Win7 64 Ultimate6GB RAMNvidia GTX460 1gb
  23. Do you have UT2? If so, I have seen this happen for myself and others at their PHNL scenery. The fix for me was to turn off moving jetways, and GA aircraft when flying in that area. Go to the FSDT forum and do a search. John
  24. I've seen this occasionally in the LDS 767 and PMDG 747x. - John
  25. Hi Guys, I have two liveries I want to update. Do I need to uninstall them first via the livery manager, or can I just install over the top of the existing? Thanks, John
×
×
  • Create New...