n77737

I really enjoy flying the Waco having flown one in real life. However, on a long flight it can become tedious. In P3D I had no problem adding an autopilot but in MSFS I haven't come up with a solution. Is there a way to add an autopilot, even just a wing leveler? Do not need the instrument itself, could just control via the keyboard. Thanks Dave

I'll be at the front of the line for a B727 in MSFS.

There is a button on the back of the unit to turn it off. Trouble is it comes back on every time you power up the yoke.

I've been flying real aircraft for almost forty years, I can make a bad landing in ANY aircraft, including the models from Alabeo.

Yes, what about the DC-6? It's, by far, my favorite PMDG aircraft.

Boeing 727-200 and the DC-3.

Now we need one for Prepar3d v4.4.

I think Bambi is going to need a bigger set of antlers.

Nice to have a BBQ Bambi-berger now and again. Just wish they would stay out of the road.

See, deer are vandals: that's why we need to kill then all.

My experience: V-sync off frames unlimited, 40 to 140 FPS depending on where I'm flying, smooth and stutter free. Frames locked at 30, no change, the sim is fantastic. The big difference is that with the frames locked at 30 my video card is running 10 deg C cooler. So I will continue to lock my frames to ease thermal stress on the system.

Bad timing. I'm in the process of loading my plane for the flight to Oshkosh. The DC6 will have to wait till after the fly-in.

I had this problem with the X52 Pro Joy stick. The method below, from Saitek support worked. Try substituting your driver. Dave After the major Windows 10 update (build 1511) there have been a few reported issues with Microsoft. Try this short version first: - Connect X52 - Open device manager -> look for an USB input device with an ! - Right click: update driver - Choose "search on my PC" and then "let me pick" (2nd option) -> you get a list of 2 compatible devices - Now select the 1st option "USB input device" or something similar NB: NOT the 2nd one with USB X52 in the name!!! - Device should work now... If this does not work: this is the long version which was the first way I found to get it working again: - Plugin the X52 - Go to device manager and delete the X52 and USB devices with an ! sign (warning/not installed correctly) - Restart your PC - Unplug your X52 - Run the installer (with the latest beta drivers for W10) - When the screen pops up with the instruction to plugin your X52 -> plug it in... - Just let the installer run (with the NEXT button greyed out) and go to device manager - Right click on the X52 device and select update driver - Choose "search on my PC" and then "let me pick" (2nd option) -> you get a list of 2 compatible devices - Now select the 1st option "USB device" or something similar NB: NOT the 2nd one with USB X52 in the name!!! - Directly after this W10 detects your X52 and you can select NEXT in the installer - Install will continue and finish correctly The right selection of the USB device (AND NOT X52..) is important. If you select the X52 line you get a critical error and it stops.. Also I would recommend disabling FAST START. It seems that Windows starts too fast for USB devices to report themselves and to be enabled. You can find this option here: Energy management -> behaviour of on/off buttons -> Fast start is greyed out, but if you select "choose options which are not available right now" you can disable it. -

I was reaching for my credit card until I noticed two of the engines are about run out and the other two are over half time. I'll keep looking. Dave

I'm wirh ya on a DC-3