Pict

There are a few actually (example of one below).... All runways have glideslopes....just that most don't have glideslope guidance (e.g. ILS/MLS).

Be reasonable - 24 Hours haven't even passed yet.....and it's a weekend. At least give a technician one to two business days to respond to a support request (and more time to investigate and come up with a solution). [Edit 201611051718] While you wait you can also search the forum for similar posts and read the stickied posts as well to see if they have anything relevant.

Visit (and register at) their support forum for help: http://qwsim.flight1.net/forums/

Sounds like your scenery.cfg (or terrain related files in the FSX directory) may have been corrupted at some point during the process. I only have the boxed version so not sure if the steam version changed it - but you can try checking your /ProgramData/Microsoft/FSX folder to see if any backups of your scenery.cfg were made by the Orbx installer. *X referring to the primary drive letter your resides in.

Eaglesoft's SR22GTX Gen-5's a personal favourite for me - flies pretty much perfectly on the numbers from my experience, and not taxing on my system at all.

Noticed the same thing as well - particularly the erratic FD commands - better than earlier versions so at least some fine-tuning took place. I'll withhold any judgement until the software is actually complete....as there can (and most likely will be) be major overhauls even at a "v0.85.x" - especially in the area of systems. Unfortunately many of you here (and elsewhere) seem to not understand what beta software actually is though ... VC is far from complete, systems are still being implemented, FBW still being tuned ... and by a two-three person team (how many of you complaining have any programming knowledge? Maybe you should offer your services to them and pitch in rather than poke fun at them constantly). The mere fact that they're taking on developing an Airbus FBW type (notorious for their difficulty in programming/coding for any accurate simulation) is a feat in its own right - and there *will* be major coding/visual/FDM overhauls for sure even before any RC's are released. FSLabs only covers the narrow-bodies for now - aside from Aerosoft's upcoming offering, this is pretty much the only other Airbus wide-body with any (planned) in-depth systems simulation - and the only recent one doing a mid/study level A340 (well there is the Wilco Editions....can't really say anything on it as I don't have a copy of it). [edited for grammar] -sorry for my marconic english

When you (and others here who are constantly complaining) decided to buy what is *beta software* you should have known all that would be encompassing....meaning unfinished systems, bugs, incorrect performance parameters, handling issues, installation issues, texture issues, memory leaks, sound issues, etc etc. Nobody held a gun to your head(s) to buy it. They never once said it was a finished product when they began selling it - so not sure why persons here are acting as though they did. Moral of the story: if you want a finished (or as close to finished as you can possibly get) software - save your pennies and wait until the final release - don't buy beta versions and complain afterwards.

All have some degree of licensing from the respective manufacturers - you can't be making money off their products (or any likeness thereof) without it.

I barely see much flex in the A320s wings in reality myself, so for me if omitting it from the visual model will save on resources and make the flight smoother frameratewise, then by all means do away with it. No point it going all out for realism when the most basic realistic factor in a flight (fluidity) is sacrificed in favor of eye candy that's barely noticable in reality. Same goes for others like the DC9, A300/310, CRJ, ERJ, and older GA all-metal aircraft. Photos/videos (particularly those taken from a quartering angle, ie wings close to the edge of the frame) taken with a zoom lens are prone to being distorted slightly by spherical aberration, which makes the curve more pronounced than it actually is.

Indeed I've flown Senecas through moderate turbulence (found myself under a Cb west of KPBI over the canals once) - but I've never seen the wings flex at all (sure the flaps rattle when deployed, but thats about it)...so I'm not to sure if Carenado is being entirely realistic in that regard.

It's not a bug, have a good read of the manual(s). -Xavier

In most turboprops with non-counter rotating propellers its the same principle. The aircraft will react to power changes all the time, some are benign (like kingairs, dash 8 300/100), while others are rather aggressive, needing frequent retrimming (q400, i heard cheyennes as well and mu-2s). The trick is to counter these changes by being smooth and gradual with power changes and control inputs. Adjust power ahead of time, never when it gets to the time you'll need it, and while doing so, counter with your ailerons/rudders. It takes a bit of time to get your "groove" regarding this. During the landing keep the power up and keep the approach stable - dont fluctuate in the airspeed or descent rate too much. In most turboprops with non-counter rotating propellers its the same principle. The aircraft will react to power changes all the time, some are benign (like kingairs, dash 8 300/100), while others are rather aggressive, needing frequent retrimming (q400, i heard cheyennes as well and mu-2s). The trick is to counter these changes by being smooth and gradual with power changes and control inputs. Adjust power ahead of time, never when it gets to the time you'll need it, and while doing so, counter with your ailerons/rudders. It takes a bit of time to get your "groove" regarding this. During the landing keep the power up and keep the approach stable - dont fluctuate in the airspeed or descent rate too much.

Do you think it's simply a case of disabling the engaged authrottle mode and simply forgetting to renable them afterward? I'm doubting the automation had anything to do with this accident - unless the 777s fbw is supposed to trigger TOGA power like in airbus fbw aircraft. I forsee a recomendation for more emphasis on stall recognition in the works post NTSB report. Xavier

It will both roll and yaw left at full power due to the torque (roll- from the engines) and p-factor (yaw- spiralling slipstream off the propellers)...they use an external fdm for this aircraft so it'll handle a bit differently than an aircraft using FSX's native fdm. [edit - 1208z] This will happen even if the controls (your joystick/yoke rather) are set up properly. About 8-10 right rudder trim units eases this quite a bit on takeoff (you can add about 5-6% right airleron as well if you like - just remember to reset that to zero before engaging autopilot). -pict/xavier

Even the A340-200/300's can't really be considered as underpowered, as they're the only widebodies (outside of the 747/md-11) that can takeoff from SXM/TNCM 7003' runway and clear the terrain just after with an engine out - 777's/A330's are often weight restricted and often takeoff with little fuel to do a fuel stop in PTP/TFFR prior to doing the transatlantic return to Paris; With typical transatlantic load/fuel, the big twins are unable to clear the terrain after losing an engine. -Xavier