HighFlyer310

Thanks for the replies. The last takeoff I had issues with was with winds 190 @ 11 kts departing on a 140 heading. So thats not anything crazy but I nearly went off the edge of the runway before it finally started reacting to my rudder input; kind of frustrating.

Hey all, This aircraft is a blast to fly. The only issue im having is directional control on takeoff is sometimes very hard to manage with crosswinds. Im using ASN for weather and CH pedals with sensitivity maxed out. When the steering shuts off around 30-40 knots I have to go full right / left on the pedals respectively to keep the plane from going off the runway. Can someone let me know if this is operator error or is there some kind of limitation? Thanks!

Im trying to activate my Lear 35 installer purchased through Simmarket. The code they provided doesn't seem to be working. Any help here or do I need to contact simmarket? Thanks Tom Moretti

People continue to buy their overpriced garbage, so why should they change their standards? They wrap fancy textures around half @$$ default functionality and then have the nerve to charge 35-40 bucks for that? It's not about being prideful in their design, it's just carbon copy one product after another and watch the cash come in.

This is interesting. I seem to have a similar situation going on. I've never had any OOM problems period before the last couple flights with the 77W. Both times it crashed on me in cruise with hardly anything being loaded. The first week of release I did quite a few long routes with no issue, then out of the blue I can't complete a flight. Nothing changed at all either, no settings, no added scenery, nothing. I really don't load the sim down with much to begin with.. REX UTX GEX and ASN.. 1024 clouds. That's it apart from my airport sceneries. I monitored my VAS on this last flight which had me between 2.0-2.5 through most of the flight. I'm stumped as to why I'm getting the crashes. I'll try and update my video driver and check for framework updates and report back.

I myself have no experience in a leveld sim or the real thing. I do know a few airline guys, one who flies the 777. They all say that the autothrottle comes off on approach during turbulent conditions. I should say disconnected, but still armed in the event TOGA thrust is needed. The difference between RL and sim is that in RL, even with the autothrottles engaged, the PF still has authority over the thrust, the servos won't fight manual control. I'm not exactly a manual junkie but I'm sure that there is something in the FCOM that covers autothrottle ops in turbulent air. If not I'm sure that's left up to airline SOP. The trick is to keep "throttle jockeying" to a minimum during approach in any conditions. Large changes In thrust upset stability and ultimately creates more work on the controls than is necessary. I usually disconnect a/p and a/t at about 2500'.. Configure flaps/gear and find a sweet spot for thrust, from there it's only small changes to stay on glidepath. I guess my point here is that having an actual hardware throttle makes all the difference in flying a good approach in any conditions.

Bottom line.. The autopilot/throttle has limitations. If your in unstable/turbulent air, the automatics are going to struggle because they are trying to chase their set values. I would recommend going out and buying a good hardware throttle (I use saitek x52 pro).. Either that or reduce your sliders in active sky. It is very common IRL for crews to disconnect the automatics when the going gets rough.. They simply can't keep up, which PMDG has modeled very well IMO.

The sound changes depending on if the packs are on or off.. Turn em on and you get a nice roar!

Thanks.. So far I've only been able to find one other with the same problem, posted over in the FSDT KORD support forum.

Does anybody else get no approach/arrival data for KORD? I also get a message in the scratchpad "ERROR. RWY 10C N/A". I have the latest navigraph cycle installed. It doesn't seem to happen with the NGX (or any other airports as far as I've noticed) so I'm not sure what's going on.

Thanks for the superfluous response there captain Kyle. Your etiquette around here sucks and you know im not the only one to express that. Perhaps "I dont think" alluded to the fact that I had already covered that base, sorry for being so indirect. I posted this here to see if anybody had seen these anomalies before, not have a few words dissected for the purpose of personal ego inflation. I wont say anything more because I have better things to do than pontificate on forums all day.

I don't think it's a controller problem.. I've had it set up like that for dozens of flights with no issue. Also, I tried unplugging everything and still have the same problem. I use a saitek x52 pro throttle and I use the aft detent for reverse.. Only way to configure that is through Fsuipc I believe.

Im posting this here because I cant seem to figure out the source of the issue. This started happening to me out of the blue, I didn't change anything with the sim or in general with my PC. Below is a video I made of the problem.. there are two points in it to highlight. The first is at 1:30 during startup.. things get goofy. The other is toward the end, just after takeoff when the FADEC switches to CLB thrust.. this is the meat and potatoes.. very weird. I took the video in the NGX so I posted here, but I seem to be having similar problems with the 777 as well... at least the engine/sound issues, havent noticed the weird artifacts in the VC. I tried a full reinstall of both birds as well as a rebuild of my fsx.cfg with no luck. I guess my next step would be a reinstall of the simulator which i'd prefer to avoid. Any help would be appreciated! Add-ons: -Ultimate Terrain X USA -Ground Environment X -REX 4 Texture Direct -Active Sky Next -Registered FSUIPC (all controls assigned and calibrated) -PC specs in signature

Speed management is everything while orchestrating a descent path to the IAF. Therefore I almost always use FLCH to keep the speed under control. Its just a matter of learning the distance required to lose a certain amount of altitude at a given speed. This is also very useful for speed restrictions such as 250 kias under 10k feet. If the need arises to expedite your descent, just pop some spoilers out to come down quicker without increasing ground speed. For climb I'm almost always in VNAV.

I used to have only a CH yoke as my controller with auto rudder turned on.. I was always fighting to stay on the runway in crosswind conditions. I bought a pair of rudder pedals and now I can floss the nose wheels with the center line every time!