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.

I figured out by RTFM, that there is a lock on mixture lever, never knew about that so the mixture issue is user error. Other issue with control persists, with fps being pretty constant. Tonight I flew for a few hrs and attempted to set the controls for max power, without success. Perhaps it's me again, but no matter what I tried to do but at 8000 with 65% power nothing I did could produce 20 inhg on the egt. Best speed I managed was about 112knots at 8000. Sent from my SM-A205U using Tapatalk

Just bought it myself. I have a concern. On parking I tried to used the mouse to bring mixture full lean and the lever wouldn't go lower than midrange. The rpm lever and throttle were free and easy to move over their range, but not mixture. Funny The other concern is with my old logitech extreme 3d pro joystick, the elevator controls were "sticky", so the control was poor at approach speeds. The elevator smoothness could be a fps issue, didnt check. Tomorrow I'll look if a sensitivity setting could be adjusted. But I cant make sense of the mixture control. Sent from my SM-A205U using Tapatalk

I knew a woman in the late 70s that homesteaded on spruce island, just off the kodiak island coast. Was gonna wave, but found myself pretty busy. Sent from my SM-A205U using Tapatalk

I just have to share, this one was a doozy. Started out with the weather pretty perfect. Getting out over the ocean at about 5000', watched a huge storm develop. I'm noticing the Ocean water changes with the weather and actually shows dynamic movement. Very cool. So I'm now seeing whitecaps as this storm gets to me. Down to 2000 to run under the storm, but lose Airspeed indicator. No pitot tube heat that I can find on the 152, so I flew on by "feel". Then everything iced up!!!! Oh crap, down to 1000 over the ocean without speed feedback. Barely any space between stall and sink. Just clinging on as I approached Kodiak. Couldn't even see the runway til I was on it. Smooth landing. Took this shot on departing the aircraft.

I'm one who bought the standard version, and would enjoy the 172 with std gauges also. Funny pricing model based on which aircraft you can fly, and yet, no matter what version you have you can add more aircraft. So the price differentiation was very artificial, as all versions can eventually have lots of extra aircraft and scenery except for the "special" ac like the 172 with steam gauges. They and they alone will eventually separate those that spent more or less at the start. Honestly, this is a poor example of price discrimination, a standard practice to offer a lower price for people who will never pay full price. Good examples are lower bus fare for students, bad example is various versions of flight sim, which after several years will be, for all intents and purposes, identical, but those that paid more can have a classic 172. So silly, as I'll bet a std gauges 182 will show up, as well as the other way with a c140 taildragger. It makes me think this was the first time Asobo tried to establish such a pricing. Remember how MS did the same thing, but smarter, when they provided the sdk only for the higher price. That made sense. No one could obsolete the need for an sdk, for those who wanted to do dev work. But a nice 172??? That's supposed to make me spend more? Cmon...this is the first version of flight sim in which I even use the default aircraft. The french versions of skyhawk type performance ac are fine for now. Wanna bet dev's will not be allowed to sell me a good skyhawk either, as asobo will attempt to defend their pricing decision, poor as it is. Having said all that, this sim is the best ever for ga flying. Flew yesterday from Boeing field to Olympian at 4pm with live weather. So realistic as to be amazing, having made that flight many time in real life. Sent from my SM-A205U using Tapatalk

Regarding the hat switch and looking around...after messing around without satisfaction, I decided to use the mouse control (drag w right button depressed) for looking around. Along with the zoom control, I use this technique for looking around outside, and for cockpit access to radios, parking brake, etc. Big advantage: using the hat switch in fsx often led to an unintended movement of the stick that I'd have to correct for. Now viewing and primary ac control are separated. Sent from my SM-A205U using Tapatalk

Today flew the Robin R400 from Tunis intl to Palermo, Sicily. Used real weather, which was a bit unsettled. Had to drop down to 3000' to sneak under that system. Save landing on rwy 25 in palermo Pic is midway over the Mediterranean Sea

You are trying to future proof, which is always tempting when you are going to spend a lot more money than usual on a computer. I'll just share my experience. Me, 65 yo, retired engineer. In 2014, 7 years ago, I was moonlighting with 3ds max, and decided to build a cad machine that would last into retirement. I bought an 8 core processor, at 3ghz, with big memory, put in 64gb of ram, and bought the quatro k5200 video card. Spent around 5K. It's been a great computer for me, of course, but the real question is whether I am happy with it 7 years later. For every rational use of a computer, it's a strong performer. Still runs Cad and 3dsmax like a champ. Of course the render farm type renders take 8 hours or so, but that's not extreme. All flight simulation has run like butter, including msfs 2020, until update 5. That's when the Maxwell architecture in my GPU first showed its age. Clouds flashed making the sim only useful in clear skies. A lot less fun for me. So, there you go, 7 years later the first sign of obsolescence. Over the years I've gotten bored with gaming, so when my favorite game (half life) was refashioned with modern graphics into black mess, I got to see how my 7 year old beast handled a modern title. Smooth and sweet. So, my thought was to abandon msfs2020 and go back to pd3 as I dont even sim much and big spending without significant return is not ok. My main use now is digital recording, and thos 7 yr old beast is amazing when running a digital audio workstation software. Then this last update from asobo fixed the flashing clouds! So my old computer is totally satisfying my needs 7 yrs later. Enjoy Bob Sent from my SM-A205U using Tapatalk

I'm so happy, I have a quadro 5200k, which was a great Maxwell based card in its day. I got the flashes after update 5. Popular wisdom was Maxwell was not quite defined as minimum equipment, so it wont be fixed. I'd given up on it, but I read about the snow in this new update. On a whim I started the sim, and it worked! It's fixed! I had the best flight today, thunderstorms, rain...billowy clouds! Bob Sent from my SM-A205U using Tapatalk

Made me giggle, I also asked the ai take the controls, and did a direct "away" from my destination. I took control back before reaching n Korea. Sent from my SM-A205U using Tapatalk