sfm48

Thanks 1-Bob for the info and link

I have noticed that there is a shader cache option in the NVidia Control Panel to save CPU usage by caching the shaders on disk. Is this necessary for performance gains since P3D is already caching the shaders??

Thanks for the info!

Fixing to upgrade from a GTX 670 to a GTX 980. Should I re-install P3D or can I get by with deleting the shader cache and moving the Prepar3D.CFG out of the "C:\Users\user-name\AppData\Roaming\Lockheed Martin\Prepar3D v2\" and have the program re-build a new config? I already updated my BIOS and did not have any re-validations issues with P3D - What about upgrading the video card? will it be fine without having to do a re-install??

I had backed up my 2.2 and used the cloud.fx from it and it seems to have cured the verticle cloud issue... Yes, I plan on updating to 2.5 in the near future!!!

The link to the 2.4 vertical cloud fix (Cloud.fx) is no longer available. Can someone that still has the fix please send me the file that Ron mentioned below: "Here ya go, new file direct from LM https://drive.google...iew?usp=sharing This IS NOT a v2.2 file, it is a modified v2.4 Cloud.fx ONLY file. If you've copied your v2.2 Cloud2.fx into v2.4, replace it with the original v2.4 Cloud2.fx." Thanks! sfm

More info testing KLAS with P3D 2.4: * With the TacPack dll in the dll.xml file disabled KLAS works all the time (couatl.exe does not crash) either running Active Sky Next or not running Active Sky Next. * With TacPack dll enabled in the dll.xml, running Active Sky Next seems to mitigate the conflict between the TacPack DLL and couatl.exe AND KLAS works without coutl.exe crashing.

Update again more testing: So I disabled the Active Sky Next DLL in the dll.xml for P3D V 2.4 and KLAS disappeared as before AND couatl.exe konked out... The dll above the ASN dll in the dll.xml file was the TacPack dll, I re-enable the Active Sky Next dll and disabled the Tacpack dll - launched a flight and the KLAS works without running the ASN weather program.. So it seems there may also be a conflict with the TacPack dll? Note: I will need to test and see if KLAS works while running the ASN weather program with the tacpack dll disabled.

KLAS works now (I have not tried KPHX yet) Issue: Active Sky Next dll may be conflicting couatl.exe when it is loaded in the dll.xml and Active Sky Next is not running. When I loaded ASN before a flight I get the KLAS airport and couatl.exe does not konk out.. I will do some more testing but I think I got a work-around now (make sure ASN is running before starting P3D, if the ASN dll is being loaded in the dll.xml) Some more info: P3D V2.4 Active Sky Next for P3D SP1B couatl.exe version used for this test: 2.0.0.2378

That's what I was thinking.. (could be some files are compiled specifically for 2.5) Just upgraded from 2.2 a few days ago and decided to go with 2.4 since I had it stashed away on my secondary drive for a while and my internet connection went out about half way thru the 2.5 download of 10 gb - another reason is that I heard other folks having issues with popcorn clouds, reflections, etc and wanted to wait until those are fixed up with 2.5. Anyways, 2.4 seems more smooth that 2.2 did and I don't need to use the affinity mask tweak anymore! I guess I will eventually get around to updating to 2.5.. In the mean time , I just wanna fly :-)

A few more things that I would also mention: Problem with couatl.exe crashing with FSDT KLAS & Flight Beam KPHX occurred after installing P3D 2.4 (was working great under P3D 2.2) FSDT & Flight Beam airports are all working good under my FSX Gold installation. This Problem seems to only manifest itself with KLAS and KPHX in P3D V2.4 (KDFW works great under V 2.4) Has anyone got FSDT's KLAS or Flight Beam's KPHX working under P3D V 2.4 using couatl version 2.0.0.2378 or the couatl Beta version 3.0.0.3028 ???

I guess the fsdt payware airports Las Vegas and Phoenix or just broken for 2.4+ until they can fix up the issue with couatl crashing... Maybe it is a mismatch with the compiled code.. I notice they are installing visual studio 2013 resdist code when installing... Oh well, at least kdfw works ok!

Got a weird thing happening with couatl.exe in that when I am at KLAS or KPHX the buildings will load up and P3D V 2.4 will pause for a few seconds and the building will disappear, and not CTD (no crash to desktop) P3D keeps running fine - it's just that couatl.exe will unload itself. Note: KDFW is working fine! (KDFW also works with the public beta couatl.exe) Tried re-installing KLAS & KPHX - no worky Tried downloading the stand alone add-on manager - no joy there either! Tried using the Public Test beta Stand alone Mananger V 3.0.03 and no luck Also: No Nvidia streaming stuff running AntiVirus disabled for testing Disabled FTX Vector Here is what was reported in the event viewer Non Beta Version of couatl.exe: Faulting application name: couatl.exe, version: 2.0.0.2378, time stamp: 0x54bec650 Faulting module name: couatl.exe, version: 2.0.0.2378, time stamp: 0x54bec650 Exception code: 0xc0000005 Fault offset: 0x000028f6 Faulting process id: 0x240 Faulting application start time: 0x01d06fd201e4bf4e Faulting application path: G:\Lockheed Martin\Prepar3D v2\fsdreamteam\couatl\couatl.exe Faulting module path: G:\Lockheed Martin\Prepar3D v2\fsdreamteam\couatl\couatl.exe Report Id: 60846f29-dbc5-11e4-b2ae-180373420dbc Public Test Beta add-on mgr with updated couatl.exe: Faulting application name: couatl.exe, version: 3.0.0.3028, time stamp: 0x551be9bb Faulting module name: couatl.exe, version: 3.0.0.3028, time stamp: 0x551be9bb Exception code: 0xc0000005 Fault offset: 0x00019413 Faulting process id: 0x1a64 Faulting application start time: 0x01d06fdc12484010 Faulting application path: G:\Lockheed Martin\Prepar3D v2\fsdreamteam\couatl\couatl.exe Faulting module path: G:\Lockheed Martin\Prepar3D v2\fsdreamteam\couatl\couatl.exe Report Id: 6c74f4be-dbcf-11e4-b70d-180373420dbc

About to ditch 2.2 and install 2.5... In 2.2 and 2.1 - I have noticed a few glitches: 1.) Occasional (Intermittent) Floating autogen when flying over a large metropolitan area 2.) Carrier wake (Javier Carriers) flickers 3.) Some third party aircraft (i.e. Aerosoft) have exterior lighting issues - i.e. taxi light not illuminating ground, cannot see wingtip lights from inside cockpit, etc. Other than those mentioned above, it's been a good experience with 2.1 & 2.2!!! Have these bugs been fixed up in 2.5??? Thanks!

Steve's DX10 fixer for fsx now has the aerosoft lights working in FSX DX10 mode.. I believe he made a change in the effects files... Javier carrier lights also work in FSX DX10 mode.