bobterri

Will this method of moving MSFS to another drive work with the Steam edition? If not, would someone explain how to do this for the Steam edition?

I have been flying Airbuses in FSX, P3D and now, FS2020. Up to this point I haven't had this problem. I've been using this same Logitech Yoke all this time. The people over on FBW discord said they did, indeed, change the settings a view updates ago. I am trying some new settings tonight. Hopefully they will help.

Look, guys, the Logitech Yoke is what I have. I can't afford to buy anything else for now. With what I have, can anyone help me?

As I mentioned, I have the Logitech Yoke. Thanks for helping.

I did ask on their discord server and I just got an answer. They did, in fact, change the settings a couple of updates ago. Basically, I was told to play around with the settings until I find something that works.

I had been enjoying FS2020 so much, flying the excellent FBW A20N. I have the development version I had adjusted my Joystick L-Axis Y sensitivity setting to -30% per their recommended settings. My landings were wonderful. A slight tug on the yoke and a perfect flare and thus a perfect landing almost every time. But, then something changed after a FBW update. I rechecked my settings in FS2020 and nothing had changed there, but now, when landing, that slight tug (in fact, any tug) will send the airplane drastically nose up which, then of course, I try to correct and that sends the plane drastically nose down and...well...those landings, which were so wonderful are now horrible. Has anyone else experienced this? Again, I'm using the development version. Can anyone recommend any other settings? Thanks.

Calum, That is good news about the DXGI crashes. As far as your shimmering, yes, my payware airports also were worse when it came to shimmering. Sorry to hear this hasn't improved for you. What is your AA setting in the sim?

I guess I'm looking for people that had the two problems I mentioned in 5.1 but no longer have them in 5.2 HF1.

I have a 19-10900k cpu and a 1080 ti gpu running a 1440p monitor. If I ran any MSAA setting in the sim, I'd get very bad shimmering. With the sim running SSAA 6, I'd get a tolerable amount of shimmering.

I posted this over in the Prepar3d forums and thought I'd post it here too. Just trying to get some answers before giving P3D 5 another try. When P3D 5 came out, I purchased it and really enjoyed it with some caveats. I updated to 5.1 and continued to mostly enjoy it, however two problems eventually forced me to revert back to 4.5. First, the shimmering! It was much worse in 5.1 than 4.5. Has this shimmering problem been corrected in 5.2 hf1? Second, DXGI crashes. 4.5 is rock solid for me, where with 5.1 I was experiencing these crashes far too often. Has 5.2 hf1 eliminated these crashes? Thank you.

I agree that 5.1 is very close to being a decent platform. With my DXGI errors, I tried all the suggestions except going through each 3rd party scenery to diagnose the errors. That's why I went back to 4.5 for now. I'd rather fly 4.5 then go through all the headache of tracking down errors in 5.1. I suspect that a lot of the 3rd party developers are simply not putting a lot of effort into their scenery for 5.1. I could be wrong, but I believe that some of the stuff they are releasing is not really best suited for 5.1 and hence, the DXGI errors.

I, too, absolutely loved (notice past tense) 5.1. It really was so much better than earlier versions of P3D. However, I had to go back to 4.5 because of the DXGI errors. Hopefully 5.2 will deal with these errors.

Anyone?

I had to move Prepar3d 5 to a new computer. Before I did, I copied the FLAI folder which was in my appdata/roaming folder onto a thumbdrive. In the new computer, I transferred the FLAI folder to my appdata/roaming folder. Then I also added the FLAi_Model_Matching.vmr into documents/vPilot files/FLAI. The problem is, vpilot is not recognizing the models, even though I add FLAi_Model_Matching.vmr to Custom rules in vpilot. I think the problem is, I don't seem to have an addon.xml file for FLAi. If you have one, could you send it to me? Thanks.

I was afraid of that. I guess I'll just stay with my iFly 737ng on P3D 4.5 until PMDG NGXu releases on MSFS. Thanks for getting back to me on this.

I read some time ago that if you purchase the NGXu by 12/31/2019 you will get a $99.00 credit towards the purchase of the PMDG NG3 for MSFS 2020. Has that offer been extended past that 12/31/2019 cut-off? I have flown the iFly 737ng for years, but they still have not released an update for P3D 5.1. If PMDG is still offering that $99.00 credit, I'm going to make the switch. Thanks, in advance, for your help.

Bing maps represents about 2017 for my location (Davenport, IA, USA). Only three years old.

thanks

I use Windows Security. When I temporarily turn off my security to download and install software, I usually just turn off "Real-Time protection" in windows 10 settings. Is that enough, or are there other things I should be shutting down?

I, too, am waiting for SP1 to purchase this product. Hopefully soon!

77/11

BobKinSTL, My VATSIM story echoes yours, except I began flying VATSIM in 2010. The first flights were much the same as the one you describe above. Hang in there! You'll get better and flights like the one you had from KCLT to KATL will become fewer and fewer. There will be challenges from time to time but you'll adapt quicker and with more experience you'll do just fine. Most of all, remember, have fun!!!

Fantastic! Thanks, Matt.

He's just frustrated! We've all been there.

And, who would know better, Matt! The vast majority of us really do appreciate you and others who do so much for our hobby.