By FAR , As2016 , soon to be ASP4 for Prepar3D V4. :)

Ah Thank you very very much Max. :).

nice to see everyone viewing this and no answers :(

I've looked in the Prepar3D v4 folder and see there is a Waterfall.fx and Waterfall_small.fx file in there and Splash.fx. However they are absent in the scenery during flight.

Hey Devs,

for us Helicopter and CA pilots did you guys fix the waterfall effects at all in this version of Prepar3D v.4. I just flew Yosemite Valley in California and no waterfall effects.

thanks guys,
that help with the basic control issues here too. and will get me by til FSUIPC5 is in the pipe. Buttons setting are still nil. :)

hi Elaine, I have an " Under the hood" question for you that maybe you can get an answer from the Devs on. looking on the install note that you prepared { which are the best I've ever see} I notice the VS 5015 version in 14.0.23026.0.. Some of us are participant in the Windows 10 insider p...

go into you Prepa3D installation and find the redist folder. Inside you will find a simConnect folder. and install the 3 simconnects required for P3D.

Lockheed Martin,

Any upcoming patch in the works for this. Alot of folks will need one here real quick when Microsoft pushes the fall update on Everyone.

yep, this it the .net error I got in event viewer so al least we narrowed it down to the cause. Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name=".NET Runtime" /> <EventID Qualifiers="0">1026</EventID> <Level>2</Level> <Task...

Mike, and Fellow Prepar3D folks.
I attend this morning Micorsoft Windows 10 insiders Bug bash and personally gave the engineer my data and replication of this issue. hopefully it will be resolved in the next few builds,. :)

of course it would. and runs beatifully. :)

yeah I was hoping Poppet or Adam,
play with it under the Windows 10 updated core and found what the issue is by now. oh well. it's hit or miss here. sometimes it works. sometime it don't. mostly don't and is an annoying, but it doesn't prevent you from flying.

So Far so good with the registry version change to .NET.. going to do a few more flights in different aircraft/situations. Looks like we found out culprit. :) BTW the version I ended up using that worked so far is version number was 4.6.02025

.net framework setup in the Full key in the registry has to be change for 4.7 to 4.6.01586 in Windows 10. so ofar is a pill getting past the permissions. you can try to change it in Prepar3D.exe config. to use .net 4.7, but it pretty spotty when it will work or not work. Microsoft omitted .net 4.5.1...