By Bob Donovan 833925
#520990 I have the craziest problem going on and although I'm a pretty skilled troubleshooter, this one has me stumped. Through all my searches across the internet, I only found 2 others with a similar problem and no solution or follow-up.

Connected to Vatsim, chugging along the airways, and engines quit. Red and yellow lights everywhere.
This has happened in the TFDi 717, Aerosoft CRJ, PMDG 777. Oddly, it never happens in the PMDG 737 or 747.

I've removed all mappings (including keystrokes) to mixture cutoff.
I've run without Activesky.

When I disconnect from vatsim, the problem doesn't happen. When I connect again, sometimes withing a minute - sometimes 10 minutes - it happens again.

I'm not touching any buttons or controllers.
There seems to be some sort of a bump (like turbulence) right as it happens. But I can't be sure because the autopilot usually switches off at the same time the engines quit. On the CRJ and 717, I can recover with a CTL-E, but it will happen again a few minutes later.

I've been doing this a long time and I'm really out of ideas what it could be. It's too crazy of a problem to find any good leads. This has been happening both in P3D 4.0 and after the upgrade to 4.1.

P3D 4.1, Win 10

Appreciate any help or ideas.

Bob Donovan
By Ross Carlson 887155
#520992 Does it happen if you are online but not within range of any aircraft?

Have you tried enabling the SimConnect debug log to see if there are any clues there?
By Bob Donovan 833925
#520994
Ross Carlson 887155 wrote:Does it happen if you are online but not within range of any aircraft?

Have you tried enabling the SimConnect debug log to see if there are any clues there?


Ross - I can't say 100% for sure it happens out of range of other aircraft, but I can say for sure - it seems to happen more during events when I'm in the conga line.

In the mean time, I'll enable the simconnect debug log and see what it turns up next time this happens.
Appreciate the response... BD
By Simon Kelsey 810049
#520999 Shot in the dark, but could this be essentially the same problem as some JoinFS users are experiencing with P3D v4.1?

http://pmem.uk/joinfs/forum/viewtopic.php?f=3&t=556
http://pmem.uk/joinfs/forum/viewtopic.php?f=2&t=550
http://pmem.uk/joinfs/forum/viewtopic.php?f=2&t=585

Does seem like there might be something weird going on when other aircraft are injected in to a P3D v4 session...
By Bob Donovan 833925
#521010
Simon Kelsey 810049 wrote:Shot in the dark, but could this be essentially the same problem as some JoinFS users are experiencing with P3D v4.1?

http://pmem.uk/joinfs/forum/viewtopic.php?f=3&t=556
http://pmem.uk/joinfs/forum/viewtopic.php?f=2&t=550
http://pmem.uk/joinfs/forum/viewtopic.php?f=2&t=585

Does seem like there might be something weird going on when other aircraft are injected in to a P3D v4 session...


Simon - that sounds exactly like what's happening to me.
I'm wondering if it's being caused by model matching dragging in complex or like-planes to what I'm flying rather than a much less complex AI aircraft.
It seems they still haven't solved it over at joinfs.

I went over to vPilot in my model matching and noticed I have SimObjects/Airplanes checked.
http://prntscr.com/i34k3a

I will try this unchecked and see if this stops the problem. Thanks for the lead!
By Ross Carlson 887155
#521015 Yeah, certainly seems like it. Instead of deselecting the entire SimObjects\Airplanes folder, try just deselecting the Carenado planes and see if that prevents the issue.
By Bob Donovan 833925
#521024 Simon and Ross. Thanks. I did four flights tonight in pretty heavy vatsim traffic and didn't have the problem.
This has been nagging me for months.
I'll keep testing it out, but looks like we may have found the culprit, although I'm curious what exactly is in the Carenado models that cause this. Maybe if I'm ambitious enough I'll re-enable them and turn on the simconnect error log.

Thanks again gentlemen. BD

Ross Carlson 887155 wrote:Yeah, certainly seems like it. Instead of deselecting the entire SimObjects\Airplanes folder, try just deselecting the Carenado planes and see if that prevents the issue.


Simon Kelsey 810049 wrote:Shot in the dark, but could this be essentially the same problem as some JoinFS users are experiencing with P3D v4.1?

http://pmem.uk/joinfs/forum/viewtopic.php?f=3&t=556
http://pmem.uk/joinfs/forum/viewtopic.php?f=2&t=550
http://pmem.uk/joinfs/forum/viewtopic.php?f=2&t=585

Does seem like there might be something weird going on when other aircraft are injected in to a P3D v4 session...
By Ross Carlson 887155
#521025
Bob Donovan 833925 wrote:although I'm curious what exactly is in the Carenado models that cause this.


Those threads in the joinfs forum suggest that it has to do with the copy protection in the Carenado aircraft. My guess is that when the aircraft is loaded as an AI model and not as the actual plane that you're flying, then the copy protection code doesn't work right, and thus the model cuts your engines, thinking you have a pirated copy of the software.

This is just a somewhat educated guess, though.
By George Sansom 1004791
#521224 Guys

This is a very interesting topic, it's exactly what is happening to me.

I am also using P3dv4.1 and windows 10.

The engine stall on both engines happens with Prosim and iFly 737 aircraft.

I will look into the model matching and remove the Carenado a/c to see if that helps.

Cheers

George
By Bob Donovan 833925
#521232 George: It's been over a week and the problem has not re-occurred once I took the Carenado models out of vpilot model matching.

Hope you get the same positive results.

BD


George Sansom 1004791 wrote:Guys

This is a very interesting topic, it's exactly what is happening to me.

I am also using P3dv4.1 and windows 10.

The engine stall on both engines happens with Prosim and iFly 737 aircraft.

I will look into the model matching and remove the Carenado a/c to see if that helps.

Cheers

George
By Michael Collins 811662
#521257 Hi Guys,

I have the same problem - running the iFly 737 in P3dv4.1 in Win 10. I unticked the only Carenado aircraft in my V-Pilot model matching list before I started a flight on line from EDDF to EDDM. I just got to the hold at RW 25C when I came up behind another aircraft and had a dual engine failure, exactly as described very well in the first mail in this thread.

This is about the tenth time this has happened to me, usually at take-off or arrival - in any event when I come into range of another aircraft. I reset the flight but disconnected from VPilot and flew the same route without any difficulty. I don't think I can complete a flight on line with other traffic within range. I will try tomorrow to fly on line where there are no other aircraft.

Can I ask Bob if you just deactivated the Carenado by unticking the box in the vPilot model matching set or did you actually uninstall it?

Any other advice? Anybody?

Regards,
Michael
By Bob Donovan 833925
#521258 Hi Michael.
I unticked the Carenado aircraft in the model matching. I did not uninstall the aircraft from the sim.
If this isn't working for you, maybe there's another aircraft with the same behavior as the Carenado.
It might not hurt to uncheck all complex aircraft and leave just AI models.
If the problem is solved you can start adding them back one at a time until you find the culprit .. which would be good info for everyone.
I hope you get this solved. It made me bonkers for months as search results weren't producing a lot of similar issues.

Michael Collins 811662 wrote:Hi Guys,

Can I ask Bob if you just deactivated the Carenado by unticking the box in the vPilot model matching set or did you actually uninstall it?

Regards,
Michael