Beener

It did the first time for me, the the other times it fluctuates altitude by about 2K and stabilizes and then I can start descent. But the cabin pressurization shoots up to a ridiculous 90000 altitude so I'm landing with a bunch of dead passengers......

The pause toggle with pmdg, fenix, Maddog, etc stops the fuel burn. Not so with the a310, leave it long enough and it runs out of fuel. I use Time Machine to pause and it works with all other planes except the A310. It continues to burn fuel as Aaron stated above. A fix to this issue would be great.

Thanks Bernard for confirming. Good to know at least the problem is not my setup.

I'm curious if anybody else has encountered CTD when you ignore the ATC and it cancels IFR or if you request IFR cancelation. Once I've determined it was reproduceable I just stopped using ATC. (CTD occurred when I was busy taxing to my gate and inadvertently ignored ATC therefore it canceled IFR) But then I saw that none of my takeoffs were being logged in the logbook. I've since read this is a bug if you don't request takeoff clearance. So I've started getting takeoff clearance and then just ignore ATC for the rest of the flight with no issues. Today I tuned in ATC during my descent and I thought I was going to be smart and just cancel IFR prior to landing and it immediately CTD. So I can faithfully reproduce the CTD by either letting the ATC cancel IFR if I ignore long enough or if I actually ask it to cancel IFR. I've done searches but I see no mention of this CTD anywhere so I'm curious if this is unique to my system. Otherwise I never have CTD if I don't use the ATC.

I have a PFC Cirrus II Yoke console and it has an hour gauge on it and it is currently showing 21,000 hours on it. Had it for years, I’ll have to dig up when I bought it in my records to see how many years of flightsim that is, just transitioned to MSFS from P3D5 over Xmas now that more complex airliners are coming out.

I rebuilt the shaders and all is good now. The cursor disappears about 4 secs of not moving the mouse. Norm.

You know how when you stop moving your mouse the cursor will eventually hide and not be seen on the screen. It doesn't hide it stays visible on the screen even after 1 hour of not moving the mouse. Norm.

Has anybody encountered an issue with the cursor staying visible in p3d4 after updating windows 10 to update 1809? Norm.

I did a conflict check in addon organizer and it returned this: .\CMeteoxml.dll | dll.xml.cfg as duplicate references. Anybody knows what this is? Norm.

How do you identify which one it is? I'm using the addon organizer. NOrm.

I bought the 747-8 expansion but I'm going to have to live without the rainmaker effects. Since 4.3 came out I've been unable to get P3d4 4.3 working with uninstalling the 4.2 client and installing 4.3 client. I've read everything surrounding this but it just stays stuck on the splash screen. I deleted the dll, scenery, cfg, moved the addon.xml files out of the folder, deleted shaders, moved the planes out of the airplanes folder. I've run out of options other than a fresh install and I really don't want to do that again as I did it with 4.2 and it takes forever with all my addons. Anybody have any ideas otherwise I'm stuck with no rainmaker effects. Norm.

So I've done searches on finding all the settings to disable the lock screen from appearing when I'm flying in P3D4 v4.2. I've disabled the process, i've checked all the power management settings do disable it from going to sleep and unfortunately randomly on longer flights where I haven't interacted with the PC I'll come back and the lock screen is displayed. If I key in my PIN the flight resumes but my fuel has appeared to continue burning without moving thus ruining the flight. Does anybody have any ideas what I may be missing for settings or have encountered this issue as well. I have a 4790K with an asus maximus VI extreme board with 32GB ram and a Geforce 1080TI. Regards, Norm.

Anyone?

Thanks I’ll give that a shot norm.

I think I wasn't clear enough in my original post. I understand that dynamic lighting is a hit to FPS. But I think something has changed on my system (or else I never realized how big the hit was) which make it seem the hit is larger than a month ago. I lose over 10 FPS with my test with PMDG 737 sitting at FSDT PHOG at night on runway with no AA selected, no HDR and resolution at 1900x1200x32 originally and changed just today to 1920x1800x32 with the same result over a 10 FPS drop. The reason that I suddenly noticed it was that I installed the FSLABS A320 on Wednesday last week and then this past weekend did a flight into LIML at night (Jetstream addon) and for the first time ever I saw my FPS go into single digits so I started investigating. What I'm interested in hearing is if you sit at night on an addon airport say like FSDT PHOG with no landing lights on and then turn them on how many FPS on average do you lose when you have dynamic lighting on but no HDR and no AA? If I move the P3D4 windows just to a sign monitor (I fly in windowed mode) when I turn off the lights on and off the FPS barely changes it hovers around 50 FPS with my current settings and when I turn the landing lights on it barely registers on the FPS, which is what I'm used to. But when I span it across all three screens I'm around 47 FPS with landing lights off and then I turn them on and it drops like a rock to 27 FPS I don't believe my system reacted that bad to dynamic landing lights a month ago. Other than installing scenery I've installed the FSLABS A320. I guess for myself I should uninstall A320 and rebuild the config file but I'm curious what you guys and gals think? Thanks, Norm.