TexasGary

No KDFW update? IMHO KDFW is one of the worst handcrafted ASOBO airports.

OK, I changed the distancetonotanimate setting from 2000 to 1 and disabled FS Traffic. And my FPS at KPHX didn't drop into the teens. I am going to add FS Traffic back in to see if I can narrow it down to the distancetonotanimate setting and I will report back here.

Hey Bob, thanks. So I guess I misunderstood what the distancetonotanimate setting does. Ill try it with a setting closer to zero. Ill also try turning off FS Traffic and see if that helps.

Starting at a gate at Bmworld/Amsim KPHX (Version 1.5.0) with the PMDG 737, FS Traffic, and GSX I initially get pretty good FPS. But after about 10 minutes or so my FPS always drops into the teens. I tried lowering graphic settings and I also increased the DistanceToNotAnimate to 200000 from the default value of 2000 but neither of these helped. This severe FPS drop happens every time I start a flight at KPHX. Is anyone else experiencing this? If so, have you figured out a way to fix it? Thanks.

OK, I just did some quick flights experimenting with some different scenarios and trim settings. Here are the results: Normal cold and dark startup. Trim left untouched at the top of the green band. Takeoff was normal (no sticking). Normal cold and dark startup. Trim adjusted to the middle of the green band. Takeoff was normal (no sticking). Start on the runway ready for takeoff. Trim left untouched in the middle of the green band. Takeoff was NOT normal (stuck to runway until about 120kts). Start on the runway ready for takeoff. Trim adjusted to approx middle of the green band. Takeoff was normal (no sticking). After this I deleted and reinstalled the CJ4. I'll try some more flights tomorrow and report back.

I was aware of this CJ4 "runway sticking" issue from reading the forums, but fortunately it never affected me. Until yesterday. I did two CJ4 flights yesterday, and both flights had the same "runway sticking" issue as described above. Just tried another flight today and had the same issue happen again. I had not changed anything or added anything to the community folder, and my CJ4 setup and loadout was the same as always (flaps 15, trim center of green band, V speeds set correctly, CG in range). Like others with this problem have said, once I got the plane in the air the rest of the flight was problem free. I agree with Leptinos that it seems to have something to do with the elevator trim. But if it's a trim bug then why doesn't it affect the rest of the flight? Why only the takeoff? And why does it just seem to appear randomly out of nowhere? Very strange. I am going to take Leptinos suggestion and try some flights without touching the trim wheel before takeoff and see what happens. Ill report back here after a few flights.

Yes, you can fly whatever plane you want and you can choose to only fly short routes. You will first need to buy a "license" to fly the A320. Then you will need to join an airline that flies the A320. Then you will generate a flight schedule, and when you do that you can select long, medium, or short flights.

Thanks John. I don't want to go down the SPAD, A&O, or FSUIPC roads. I really don't understand why SWS changed this for the PC12. It was so easy to set up on their other single engine turboprop (the Kodiak 100). I guess I am just going to live with it like it is.

Hey Johan, I am just using the default MSFS assignments for Condition Lever, Condition Lever Cut Off, and Decrease Condition Lever per Mark's excellent vid MSFS | KODIAK 100 Config Guide for the Honeycomb Bravo Throttle Quadrant (youtube.com) Page 13 of the PC12 manual says “The assignments have been modified via custom code to work the same and avoid accidental engine cut offs or light ups.” But to me it seems that if you use a Bravo TQ, with the modified CL assignment you are now MORE prone to accidental engine cut offs if you aren't careful in pulling the CL back to Ground Idle to the axis midpoint.

Really enjoying the SWS PC12. But for the life of me I can't get the Condition Lever on my Bravo Throttle Quad set up the way I want it. Mark at Simhanger Flight Simulation has an excellent vid on how to set up a Condition Lever on the Bravo Throttle Quad for single engine turboprops (thanks Mark!!). In his vid he uses the Kodiak 100 as an example and using his vid I can set up the Condition Lever in the Kodiak so that when its fully forward it goes to Flight Idle, when it's at the detent it's in Ground Idle, and when it's pulled all the way down past the detent it's in Cut-Off Feather. Perfect!!! But using the exact same assignments in the SWS PC12, with the Condition Lever fully forward it goes to Flight Idle, when it's at the axis halfway point it's in Ground Idle, and when it's at the detent it's in Cut-Off Feather. Pulling the lever all the way down past the detent doesn't do anything. I also tried using the Mixture axis instead of Condition Lever, but it still didn't work. Did SWS change the way the condition lever axis works in the PC12? Has anyone figured out how to enable Cut-Off Feather when the lever is pulled all the way down past the detent?

Hey B777ER, thanks for this tip. I was using custom graphic settings, and I always experienced random flashing at night with bloom on. But I just tried your suggestion and started a night flight with the Ultra preset. And for the first time I didn't experience any flashing. None. So I am going to stay with the Ultra preset from now on. Thanks.

Hey Ian, good tip on using 105 render scaling. What anti aliasing and Fidelityfx sharpening settings are you using with 105 render scaling? Thanks.

Dave, many thanks for the quick fix. Appreciate it.

Thanks Dave. Hopefully it won't be too difficult to resolve. Maybe you can post here when you have addressed it.

I have been having an issue with the weather function today. Was working fine yesterday, but today every time I highlight an airport and hit the Wx button it just says "Not Available." I also tried using the "Sim Weather" option instead of the "NOAA Real Weather" option, but it still just says "Not Available." I am on Beta Version 6D. I also installed Beta Version 7G3, but hitting the Wx button still says "Not Available." Then I heard it was announced on the REX discord channel that In the USA the NOAA has changed some of their processes and it broke REX and likely other MSFS weather interfaces (like P2ATC) until adjustments can be made. Hopefully Dave can sort out the changes that NOAA made and get the Wx function back up and running again.

For the last several hours I have not been able to get any weather info from Pilot2ATC using the NOAA weather option. It just keeps saying "Not Available."

537.58 was just released. The release notes say "This new Game Ready Driver provides the best gaming experience for the latest new games supporting DLSS technology."

I've been running MSFS with Windows 11 Professional for about a year now. Haven't had any issues.

I just updated to SU 13 and did a couple of flights. I didn't see any runway cross hatching.

I had a 416.1 MB update in the MS Store.

All of the buildings at KBWD are also missing. There are cars in the parking lot, but where the buildings should be there are only white squares and rectangles shown on the ground. This happens every time I start from or fly to there.

Update - After I read in the forum today that others also received this 655.78 MB update yesterday, I went ahead and ran it. And all is good. It looks like my data sync issue just happened to come up at the same time the update came out and I thought they were related. Looks like they were not.

Up until today, I have been happily running version 1.33.8.0 with no issues (I am not in the BETA). But about an hour ago I launched MSFS and out of the blue I got this strange message that I haven't seen before that said the data on my device did not match the data on the sever and it asked if I wanted to use the "old data" or the "newer data." I selected the option to use the older data, and then it presented me with a 655.78 MB update. Since I didn't know what the update was, I backed out and closed MSFS. I rebooted my PC and tried going into the Xbox Game Bar app and signing out and then back into it, but that didn't do anything. I also emptied my Community Folder, and I made sure I didn't have any outstanding MS Store updates. But I still get presented with the 655.78 MB update every time I start MSFS. Anyone know why I got this or what I can do to fix it? Should I just run the 655.78 MB update? I am really hesitant to run the update if I don't know what it will do. Any and all help is appreciated. Thanks, Gary

So SU13 is now scheduled for 9/28? In previous Development Updates it said SU13 was releasing on 9/21.

I deleted all of the camera entries in my Mouse profile, but unfortunately I am still seeing the white square and dot in the PMDG 738. But thanks for the tip Jude, hopefully the next SU will fix it for the rest of us.