bob5568p

If your overclock caused a ctd, it's not a stable overclock. Reduce the oc until the ctds stop. Flight sim has historically been a good test for an oc that appears stable but isnt. Sent from my SM-A205U using Tapatalk

Did you use protection? Sent from my SM-A205U using Tapatalk

The autopilot could do this if set to heading and the heading bug is way far from your actual heading. Sent from my SM-A205U using Tapatalk

I decided to explore southern British Columbia. My undoing, or the exciting challenge, was to fly the Just Flight Arrow to the San Juan Islands from Kelowna by VOR and ADF only navigation, with a real VFR chart. Been successful in the past, this is my normal "rules" for my simming. With the amazing scenery, it works and also requires constant checking of what I see against the chart. What I hadnt realized was Kelowna is in the middle of high mountainous terrain. Nearly No Nav aids except the Kelowna VOR. Luckily, the weather was no factor, and when all valleys went the wrong way I climbed up to 8000, eventually 11000. Eventually I got confused. Thinking I was following the Fraser river, but it wasn't, I got super lost. Kept dialing navaids from the chart without success. Eventually I starting getting concerned. (It felt so real as to get me a bit nervous). After a long time, I broke down and activated the in sim map. Imagine my surprise to find out I was well into Washington state, now over the north cascades. The fuel was getting low, but I was just on the route 2 (Steven's pass) and If I could just reach the west side of the cascades I could land at Monroe and refuel. Oh, that last 30 miles was quite a toe tapper. Watching the fuel guages tick down, I pulled the prop lever back to 2200 rpm, assume the fuel savings could be needed. Finally reached the lowlands and got close to Monroe when the engine quit. Feather the prop, but didnt have enough energy to reach the strip. I flew gear up nearly to the ground aiming at a farmer's field. Tried to lower the gear at the last second but was to late and I did a pretty sweet belly landing and my adventure ended without a "crash". Quite an adventure. Sent from my SM-A205U using Tapatalk

My last takeoff was very sloppy, but I put it on the pilot. Moderate right quartering headwind, shouldn't be a deal, but sometimes a cross wind can weather vane you. So I'm sloppy and using rudder to compensate for torque, only to find the plane veering right. Luckily I could rotate, and pull the gear, so it all got sorted. I've always said swimming is harder than the real thing. Sent from my SM-A205U using Tapatalk

Haven't had that problem. It does take some feel to steer it well, a light consistent touch on the rudder, as you are offsetting engine torque. On lift off with gear down you still have that full power massive torque, but no ground to resist it, so the wing should dip. Physics! Yould you'll need some opposite aeleron to oppose it. Once you lift the gear, and airspeed rises, aerodynamics assists, the lift and weathervaning help with control. Sent from my SM-A205U using Tapatalk

Uninstalled and reinstalled, and now it works. Sent from my SM-A205U using Tapatalk

First try, no joy. Full throttle for takeoff, but its stuck on the ground as though the parking brake is applied. Been toggling the brake with no impact. Wheels are turning like crazy, but no motion. I'm even reading airspeed! Crazy. Sent from my SM-A205U using Tapatalk

All I know so far is the altimeter adjustment window is now in in-HG, which is great. Bad news is every weather update from flight centers report standard pressure. Perhaps a msfs 2020 bug. Until buying the just flight plane, I wasn't motivated to pay attention to such a detail, so I hadnt noticed this. Sent from my SM-A205U using Tapatalk

One suggestion, I've had trouble with a twitchy elevator, most pronounced at slow speeds. This adjustment helped, find the file "flight_model.cfg" for the aircraft of choice and find the line called "elevator_effectiveness= 1". I edited it to 0.1. Takes a little getting used to on takeoff, but it seemed to help a lot maintaining a steady pitch on final. Sent from my SM-A205U using Tapatalk

For washington pilots, Snoqualmie pass is a delightful challenge in good weather, and a knee knocker in low ceilings. I've flown this pass (over I90) in irl in a skyhawk and once in an s22. Always a favorite trip in the sims, I finally got around to it in msfs 2020. Extra special. I recommend it to all. A good starting point is Boeing Field KBFI, with arrival in Eastern Washington at Ellensburg, KELN. Sent from my SM-A205U using Tapatalk

Tried a suggestion I read on avsim for a twitchy elevator, in the flight_model.cfg is a parameter called "elevator_effectiveness". Its set at 1. I changed it to 0.1 per the op at avsim, and found the slow flight much easier to control. Made my first smooth landing. Sent from my SM-A205U using Tapatalk

Starting the next flight and I'm watching the plane in the animated taxi sequence dance around as though the throttle in in and the plane is straining against the parking brake. Never saw a real plane do that. Anybody else see that? Sent from my SM-A205U using Tapatalk

While I was doing all that testing, as I wrote above, I was putting the sim on active pause a lot as I documented the results, and at first I was taking screenshots of each test, all of which menat the sim was on active pause for quite a while. Once complete, I attempted to finish my flight. Removed the autopilot, and for some reason, the aircraft could not be controlled. Uncommanded bank angles were extreme, and simple corrections with the yoke resulted in massive overcorrection. I'm certain the flight would end in a crash, and I hate denting a new/old aircraft, so I quit. Memory Leak?????? Inadequate computer perhaps to run at ultra high. To experiment, I reduced the setting to high, and I then took a short flight using the nearly successful 75% power setting, and I had a fine 30 minute flight with only a small control problem on final. The problems on final persist on every flight. This being the elevator over controls pitch at slow speed, which has me bobbing my nose until luckily a descent landing. My next experiment will be to adjust the y axis sensitiviy on my old logitech extreme 3d joystick to make a flatter curve near the origin. Will report back.

Update on my concern about speed control: I am a licensed pilot, but my PIC experience is limited to fixed prop simple airplanes. My understanding of a variable speed prop is from “book learning”. My simming experience began flying the early Bruce Artwick AFS2. I’ve owned the new Just Flight PA28 Arrow III for a few days, and starting to fly my new purchase. I have been generally observing performance. As previously mentioned, on a recent flight over India, I took it up to 8000 ft, and tried for 65% power, 21.5 mp, 2500 rpm, per the supplied POH. No go, simply couldn’t reach those numbers. And the airspeed and ground speed were disappointing. So I went to bed saying, hmm. Re-read the book on flying the prop, and I seemed to be doing it right. So today, I decided to take another flight with the express purpose of testing all the best power settings on the power setting table of the POH. For this flight, I flew at 5300 ft over Japan. The air pressure was standard, so I’m using the 5000’ Pressure Altitude line of the chart. For 55% power, I succeeded in nailing the controls to perfectly meet the suggested settings. This was true both at 2200 rpm, and 2500 rpm. At 65% power the results were mixed. First try for 65% was for 2200 rpm, I was at 24.3 mp with the throttle all the way in. But it was not possible to reduce the rpm to 2200. Closest I could get was nearly 2300 rpm. The settings for 65% power, at 2500 rpm were easy to achieve. And finally, 75% power for which we seek 24.6 mp at 2500 rpm. This was very close to possible. I’ve got the throttle in 100% but can’t quite get the mp up to 24.6, but its close. Actual best mp is 24 while at 2500 rpm. All in all, I’m most impressed. One final note, at 75% power the airspeed has climbed to a respectable 127 kts indicated, which is pretty sweet for this old bird. I need to return to my 8000 ft altitude to explore what was wrong. Logically, I should be making better gs than at lower alt, but I wasn't being diligent about what the atm pressure was on the previous flight.