FSX no longer compatible - will now purchase P3D

[udidwht 133]

The issue is with the recent Microsoft update from 1703 to 1709 Windows 10.

Roll back to the most recent version of 1703 OS build 15063.726 and then delete you shader folder and P3D.cfg folder and P3Dv3 will rebuild them upon startup.

I was having issue with P3Dv3.4.22.19868 and they were directly related to the Windows 10 updates when my OS updated to 1709 OS build 16299.64

I was experiencing flashing screen with mouse movement in 2D/3D cockpits and flashing sparkles in jet contrails and wing tip vapor trails. Once I rolled the OS back to 1703 OS build 15063.726 my issues were resolved.

Once you roll back to the 1703 build go to your 'windows services' and disable Windows update service. Leave it disabled until Microcrap gets their act together.

IMO...Microsoft employees should remain at work until the issues are resolved no exceptions.

[udidwht 133]

On 11/14/2017 at 5:45 PM, Chock said:

Windows 10, updated to the most recent version and with the most recent patches etc has no impact on how P3D V4.1 runs on my PC, and in fact doesn't have any impact on FSX-SE either, that runs just fine too. It's worth noting here that with P3D, I only updated the client, not the other stuff, might do that at some point but didn't really feel the need to since 4.1 was mainly adding VR stuff and tarting up some of the default planes a bit, neither of which bothered me too much.

Actually, the only thing Win 10 has caused an issue with for me, is a joystick I bought the other week, which I stupidly didn't check to see if it said Win 10 compatible in terms of drivers on the box, and sure enough, it only had up to Win 8 drivers available. I got it going eventually after some effort, but it doesn't list it in the hardware controller dropdown of either P3D or FSX-SE, and it doesn't receive any force feedback signals from P3D V4 (it does from FSX-SE), but I can nevertheless assign switches to it, which is why I can live with it being like that.

Unfortunately I think when we are into running flight simulators such as FSX and P3D, the problem is that it would be far better if either Lockheed Martin or Dovetail just went 'screw this, let's start from scratch' instead of hanging on to the ESP-based foundation which FSX, P3D and FSW are all built upon. Actually, as we know, that is what ACES and Microsoft should have done years ago, and would have done too if Bill Gates had stuck around since he was the aviation buff at MS, but by the time it was apparent that's what the FS franchise needed, Bill was packing his bags and MS were tightening their belts, so it never happened.

But it's patently obvious from stuff such as AeroFly FS2, DCS World and even XPlane 11, all of which ably demonstrate that a flight sim does not have to struggle to get decent frame rates and visuals on modern hardware, that souping up ESP-based sims which were built on the basis that increased CPU speeds would always solve graphic issues, is like bolting rocket engines to a Model T Ford, yup, that'll make it go faster, but it's likely gonna make the wheels fall off too. Dovetail are kind of half addressing it with some big tweaks to their fledgling FSW, but at present that makes CPUs and GPUs really struggle with it, and it remains to be seen whether they can solve that issue. Lockheed Martin are addressing some of it too, but when the big visual deal from P3D V4 to V4.1 is adding a half baked rain effect to the SDK, then you know that total reboot with a new 3D engine is never going to happen.

Sadly, this means we end up having to be 'early adopters' of hardware in order to have our ESP-based flight sims run okay, because we need a hardware sledgehammer to crack the walnut, and even in doing that, just when we think we've got it cracked, along comes some developer and makes an FSL A320 or a VFR photoreal scenery with full accurately modelled autogen on top of it, to slow us down again simply because 64 bit want give us an OOM, even though it sure as hell will give us a slideshow.

And that shiny new hardware always needs the latest operating system to get the best out of it; this is particularly true of the latest CPUs, some features of which won't even work at all unless you have Windows 10 as your operating system. This is in fact what prompted me to go to Windows 10 (from having used Win 7) and keep it fully updated. It's worth noting here incidentally, that you are actually not forced to do the updates for Win 10 as some are suggesting is the case, they can be manually approved for installation.

So, yeah, FSX-SE and P3D V4.1 run fine on the latest Win 10 in terms of stability, but it's not the magic performance bullet we really need, but if FSX-SE isn't giving you OOMs and you've got it looking good, then you'll have to think long and hard about starting again with the blank canvas of P3D, which will be expensive to paint up when you consider that most of us have been buying add-ons for FSX for about a decade, and that's a lot of money to be suddenly throwing at P3D, which isn't visually that different from FSX-SE apart from maybe the cloud shadows of P3D and airport wet aprons of FSX which are two obvious visual differences of their default look. Having said that, when in the history of flight swimming was it ever any different? We've always had to be getting our hands in our pockets in this hobby, for either hardware, software, or more often than not, both.

Windows updates can only be deferred for a certain number of days at which point the OS will update itself regardless. Most won't even know about it until after the OS updates itself and PC rebooted.

The only sure way....is to go into 'services' and choose to disable it.

[udidwht 133]

On ‎11‎/‎26‎/‎2017 at 0:31 AM, sillyflyer said:

 

Unless of course you Microsoft and you release an update/s that break compatibility with certain apps and/or drivers of hardware. One thing is certain....this isn't the first instance and certainly won't be the last.

Edited November 28, 2017 by n4gix
For heaven's sake don't quote the entire previous wall of text!

[Ray Proudfoot 8,942]

@udidwht, there's no need to quote an entire post when replying. Please just quote the relevant part of the post.

[Dane Watson 38]

9 hours ago, udidwht said:

Windows updates can only be deferred for a certain number of days at which point the OS will update itself regardless. Most won't even know about it until after the OS updates itself and PC rebooted.

The only sure way....is to go into 'services' and choose to disable it.

You are correct. That is what the Microsoft technician showed me to do, except I notice that after a while (maybe a day?) It turns back on and is enabled again. Not sure how to make this permanent.

So what I have done to ensure no updates whatsoever is to go into your WiFi and turn on Metered Connection, Microsoft will not update or even download any updates.

When I have read that there is a fix in place for 1709 then I will allow updates.

[udidwht 133]

1 hour ago, Dane Watson said:

You are correct. That is what the Microsoft technician showed me to do, except I notice that after a while (maybe a day?) It turns back on and is enabled again. Not sure how to make this permanent.

So what I have done to ensure no updates whatsoever is to go into your WiFi and turn on Metered Connection, Microsoft will not update or even download any updates.

When I have read that there is a fix in place for 1709 then I will allow updates.

I had mine disabled for several weeks before trying the 1709 build and at no time did it's 'disabled' setting change. After rolling back to the 1703 build I set it again to it's current state 'disabled'.

Now on 1703 OS build 15063.726

[Dane Watson 38]

2 hours ago, udidwht said:

I had mine disabled for several weeks before trying the 1709 build and at no time did it's 'disabled' setting change. After rolling back to the 1703 build I set it again to it's current state 'disabled'.

Now on 1703 OS build 15063.726

Thanks for your feedback. For some reason mine automatically changes to Manual.

I wonder if there is a different setting I need to look for?

[SierraDelta 1,341]

10 hours ago, Dane Watson said:

I wonder if there is a different setting I need to look for?

You'd need Win 10 Pro for the setting to stick.

[udidwht 133]

On 11/26/2017 at 2:20 AM, sillyflyer said:

Its called: Nutin better to do.. and very little to say

 

IntelCorei52500K//GigabyteGA-Z68XP-UD3//16GBGSkillCL7-8-8-24/XFXHDRadeon7870DD2GBDDR5

That is either a very, very old signature, or someone who needs some serious help with reality and FS hardware today

Not an old signature. The hardware is still very much up to the task. It's Intels last true milestone CPU and still a damn good one. Remember we're still dealing with what is in essence old ESP code.

[udidwht 133]

On ‎11‎/‎26‎/‎2017 at 4:18 AM, sillyflyer said:

Who said anything about Microsoft?

With the recent issues related to Microcraps updates one wouldn't need to say anything. Throwing new hardware at a possible issue is where most get it wrong right off the bat. Catch word being possible. Overclocking would be a close second when trying to resolve an issue. If one is having issues from the get go doing either of the aforementioned is akin to shooting yourself in the foot.

Edited November 28, 2017 by n4gix
Removed excessive quote. Please don't quote a "wall of text" for a one sentence reply!

[simbol 5,819]

23 hours ago, Dane Watson said:

Thanks for your feedback. For some reason mine automatically changes to Manual.

I wonder if there is a different setting I need to look for?

Some guys are using third party tools to force disable Windows updates, you can also disable the Windows 10 update service and it will have the same effect, however be aware that not updating the OS will leave your PC vulnerable to zero exploits sot at least you should put a decent antivirus on it.

Best Regards,
Simbol