Jump to content

crash_continental

Frozen-Inactivity
  • Content Count

    199
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About crash_continental

  • Rank
    Member

Recent Profile Visitors

2,011 profile views
  1. Ah, maybe I am remembering it wrong, then. Thanks for checking Mike. I appreciate it. - Daniel
  2. Hi Mike, Thanks for your reply. No altitude restrictions, although that was a good thought. I suppose your solution for putting slower speeds in the first two waypoints might work - thanks for that. Rather than using charts I must admit I've been using Utopia, with some modified .tod files I created. Using charts takes absolutely forever! It's funny as I don't remember this behaviour before for the PSS 777s. I wonder what I might have changed? - daniel
  3. Hi there, Strange problem, don't know if anyone can give me a suggestion here... I have the PSS 777-200 and -300 merged with Opensky models, something that has worked quite well. I am also using FSCaptain to load them. Everything works really well except for one small item. Having passed my real world Flight DIspatchers exam, I always calculate my derated take-off, flap and v-speed settings according to weight, atmospheric conditions and aerodrome departure procedures. For a NADP 1 it's usually TOGA thrust to around V2+10 to 800' AGL and then climb thrust until 3000 AGL, when the flap retraction schedule begins. All of this works fine, except for one small quirk. In the real world, if you were to engage autopilot as soon as you get both VNAV and LNAV indications on the PFD, the aircraft would fly this profile until 3000' AGL and then lower the nose to begin to accelerate through the flap retraction schedule while remaining in a positive climb (say; v/s +500 to +1000). Lately I have been finding that the PSS autopilot lowers @ 3000' AGL and maintains a vs of 0 (that is to say, holds 3000'AGL) until flaps are essentially fully retracted. I know the PSS autopilot is largely independant of the default FS2004 autopilot, but I am wondering if there are any parameters that I can edit that would make the autopilot any less aggressive in speeding through the flap retraction schedule. Any ideas anyone? (FS9.1, PSS 777s with Opensky model, FSCaptain, AS 6.5) Thanks, Daniel
  4. Sounds great! Is there some way of keeping us interested simmer apprised of your progress? (BTW the FS9 rebuild did not fix the issue) - Daniel
  5. Hi Inout, Thanks for your answer. I share your opinion about it being a weather related issue. I have FSUIPC wind smoothing, temp smoothing, and barometric pressure smoothing on, but to no avail. I see no weather jump (wind, temp or pressure) when it happens. When it disconnects I can immediately re-engage the VNAV button, the MAX ALT condition seems to exist for a split-second - just enough time to disconnect the VNAV. It might also be the FSUIPC button/axis control that I have set up for my PMDG and my CH pedals, Saitek Yoke+Throttles, and extra Saitek Throttle unit. When I go into the Modules menu in FS2004 and enter into the FSUIPC options box, exiting again causes the Throttles to instantly "appear" at somewhere around the 25% mark, which also disconnects the autopilot. I'm actually in the process now of entirely rebuilding my FS2004 installation from scratch, thinking something may be amiss. At the very least, it allow me to pare back some of the things I no longer use (Air Simmer, Feelthere/Wilco products, etc.). This alone could help, I believe. I'll be excited to keep hear more about your weather program. Do you plan to offer it for FS2004? - Daniel
  6. Thanks Rudy, but I think you fail to understand the issue. Just to clarify; I am a pilot, and also have my Flight Dispatcher qualifications, which is only to say that I understand the proper operation of the PMDG 747-400, with regards to weight/opt altitude/etc. My issue is technical, not operational. Something is conflicting with the regular operation of the PMDG autopilot gauges. That's what I'm trying to track down. But I do appreciate your response, and understand that you are trying to help. - Daniel
  7. Okay, I've read that ASE has problems with non-FS9 waypoints and will give you an "incomplete weather synthesis" (unlike AS 6.5, which always did). Even when I go into FS9 and re-save the flightplan with the FS9 flight planner, it still doesn't work. So my question is; how can I get my head/tailwind component? On trans-oceanic flights this is a must. Or should I go back to AS 6.5? Thanks, Daniel
  8. Yes, but the point here is that this condition exists only for a split-second. Just long enough to disconnect the autopilot. Like (for instance, but not necessarily true) there is a 'spike' in weather information that gets through and tells the PMDG autopilot that there is a massive change in pressure altitude, before it resets to the normal pressure altitude. I do understand the correct operation of the 744. There's just some technical anomaly that I'm trying to track down. Since it's only with PMDG, I'd say it's an 'over-sensitivity' with the PMDG autopilot gauge. I'm in the process of reinstalling fs2004, at the moment.
  9. Yeah, tried this. Did not work, unfortunately. It's a really crazy issue. My controllers can't be configured (you tell it to do one thing, it does another. Links two controls together, etc) In FSUIPC when I look at Joystic calibration it clearly shows a huge lag behind the movement of the axis. My view hat is like it's permanently in the "up forward" position. It's like the .dll for the controllers has been erased, or changed somehow. Don't know. I read about another guy who had exactly the same issue, but just did a reinstall. Maybe that's all I can do? Any guides for reinstalling FS2004 out there? I have many modifications that I'd hate to lose. - Daniel
  10. Nope, didn't seem to do anything at all. Thanks for the suggestion though. Any other ideas? Thanks - Daniel
  11. Hi, Looks like my FS9 is messed up after a FSX unistall. Control assignments, views, at the very least. Anyone know what's happened? Any easy fixes? Thanks, -Daniel
  12. Yeah, above FL180 I'm using Standard. I do agree there is a high level of programming going on here in the PMDG gauges. Unfortunately - in this case only - it seems like an achilles heel. Just about a showstopper, actually. I hope one day the PMDG guys can overcome this so I can start buying their a/c again. Cause in every other way they are fantastic! I've done my Transport Canada Flight Dispatcher Exams (and have my PPL) here in Toronto, and I'm looking for work in the airline industry. So I'm trying to run my flights as close as possible to the real world (opt level, route, etc.) to exercise that which I've learned. Maybe someone will come across this at some point and offer a technical solution to the problem. Until then I guess it will remain unresolved like all the other threads I've come across. Thanks for everyone's help, though. I appreciate the effort. - Daniel
  13. Hi, Yeah, sorry I realize I should have set this up a little better. This happens randomly at cruise, at the optimum altitude, with all the correct weights, etc. I get the message, an aural warning, then the SPD indication (FMA) goes away. Autothrottle and VNAV remain engaged but the speed is no longer controlled by the autopilot/throttle. I have to press VNAV twice to get it to engage again. I'm using FS2004, AS6.5, FSCaptain, and a slew of other things, so I'm trying to find what conditions trigger the condition so that I can eliminate the issue. My instinct is to say AS6.5, but I have done everything I should need to do to stop it from suddenly and radically changing winds/temps/pressure. I have read that the PMDG autopilot is really susceptible to weather changes (not just the 747, but the MD11, 737, etc.) causing this issue with a lot of people, 'S-turns' for others. I don't get this with my other complex add-ons. An inability to resolve this problem led to my decision not to buy the MD11. Just taking one last shot to save the Queen, before I retire it. All the threads I read on this are abandoned before a resolution is posted, so my hopes are low. If anyone can think what other conditions might cause this, I'd be most grateful. Thanks, Daniel
  14. That's what I assumed. But iIf I have wind, temp, and barometric pressure smoothing on in FSUIPC, these sudden spikes should not happen, should they? Is there anything else that could possibly a MAX ALT message? Thanks, - Daniel
×
×
  • Create New...