Any P3D flyers come across this?

[wombat666]

It appears that this is associated with certain Alabeo releases and it is a source of much irritation.
More to the point, once moved into my quarantine folder (nothing is deleted!) the aircraft seem to be fine.
I'm running P3Dv3.4.9.18400 and when it is activated I get the 'P3D not working' message, checking the fault dialogue it indicates 'CMeteoXml.dll.intermediate.manifest' and 'CMeteoXml.dll' as the culprits.
Checking further they come up as Carenado files, no surprise there given that Alabeo appears to be a Carenado clone.
However (there's always a 'however') the same files are fine under FSX.
Any observations would be very welcome.
I might try allowing them to run via the cfg, as was possible under FS9, thoughts on a postcard perhaps.

[jmig]

Do you know what aircraft the file is associated with? I have several Alabeo aircraft and haven't had any issues. I am running 3.49, also. I have the second to last update. Never did install the last one.

[scotth6]

Do you know what aircraft the file is associated with? I have several Alabeo aircraft and haven't had any issues. I am running 3.49, also. I have the second to last update. Never did install the last one.

Hey,

Just FYI P3D V3.4.9 is actually the fourth from last update.

There have also been 3.4.14 (Hotfix 1), 3.4.18 (Hotfix 2), 3.4.22 (Hotfix 3 - SLI Update)

I am also still running V3.4.9.

Cheers,

[wombat666]

The Carenado P46T Malibu Mirage N765FG and the Alabeo Piper PA31 350 Chieftain seem to be the main culprits, and neither appears to be affected once I've quarantined the files!
Both are supposedly P3D aircraft but I think they might be suited to earlier versions.
I should run the P3D updates and hotfixes, just to keep on the edge.
Thanks for the reply team.