Page 7 of 8

Re: Engine cut v1.4.3

Posted: Tue Feb 27, 2018 10:42 pm
by Peter
That's a very reasonable solution, Simon. There's likely to be some freeware equivalents of the aircraft that are affected. Simply install those freeware versions and configure the model matching to use them.

As has been described previously it looks like a problem with the anti-pirate measures employed by certain developers but is done in such a way that it breaks if you load up multiple aircraft in the simulator. Not sure what else I can try to be honest.

Peter

Re: Engine cut v1.4.3

Posted: Wed Feb 28, 2018 6:23 am
by blue_ice
Could the Scan for Models window maybe be developed further? i.e could we populate the Aircraft folder and have a check box for each Developer or maybe even further to which models we scan or not scan into Joinfs. If it does detect for example a Carenado aircraft folder its automatically unchecks "Not Recommended"? But obviously the user can still have the option to include it if they wish too. Just an idea, not sure how difficult it would be to implement.

Regards

Darren

Re: Engine cut v1.4.3

Posted: Wed Feb 28, 2018 1:30 pm
by Peter
Hi Darren,

yes, that does sound possible. Most aircraft include a tag for the developer so it should be easy enough to identify particular ones. I'll have a thing about that.

Peter

Re: Engine cut v1.4.3

Posted: Wed Feb 28, 2018 8:28 pm
by Peter
Is anyone finding that this problem is worse in 1.4.9 than 1.4.3? It's possible that the attempted fix has made it worse. Only respond if you're fairly sure there's a difference.

Thanks,
Peter

Re: Engine cut v1.4.3

Posted: Sat Mar 03, 2018 9:00 pm
by OMGEDSON
I can confirm this also happens with Milviz (310) and RealAir Duke...and a plethora of other planes such as helicopters as you saw in the clip.

This is not a Carenado problem...LM perhaps, but not Carenado specific.

-e

Re: Engine cut v1.4.3

Posted: Sat Mar 03, 2018 9:54 pm
by OMGEDSON
I ran into a vicious loop today... loaded up in the Carenado Cheyenne II...a friend joined, he was in the Milviz 310 and I model matched him into the Carenado 310R.

The 310R was triggering engine cut out, and was bouncing up and down, every time reloading and i couldn't keep my engines on for more than ~20 seconds... matched him to a UTlive AI and all was well...

Re: Engine cut v1.4.3

Posted: Sat Mar 03, 2018 10:54 pm
by briansommers
Good to see I'm not the only one.

It kills my Alabeo C207, Mooney M20R Ovation
and
Carenado CT206H, CT210M

It seems once are group are all well in the flight then all is well, but taxi out it was killing it a lot.

I'm using 1.4.9
but it began long time ago
I hope this can get fixed soon.

Re: Engine cut v1.4.3

Posted: Fri Mar 09, 2018 11:20 pm
by OMGEDSON
You're definitely not alone here. This renders it almost unusable for a large community of GA flyers. It's very unfortunate but a revert to (starts crying) FSCLOUD may be on the docket. Something changed in 4.1 that broke this for everyone. Just because you havent experienced it doesn't mean you won't. It's not all planes, its like the lottery...but when you're hit its keyboard smashing frustration because sometimes I'm on rollout and lifting off and other times on short final.

Re: Engine cut v1.4.3

Posted: Sat Mar 10, 2018 1:19 am
by skelsey
But surely the solution is as you stated yourself above: don't allow the affected (i.e. Carenado) models to be injected as AI! Ensure that they are substituted for alternative models instead. That doesn't stop anyone from flying the Carenado model, it just means that in your session they must be displayed as an alternative model.

As I say, I really think you're asking Peter to fix something which isn't his doing here. If an aircraft developer has introduced an anti-piracy method which triggers when their models are injected as AI, surely it's up to them to refine the way the DRM operates rather than other software having to effectively try and find a way around the DRM?

Have you tried contacting Carenado? What do they say?

Re: Engine cut v1.4.3

Posted: Sat Mar 10, 2018 8:13 am
by blue_ice
I've personally witnessed the engine cut problem on Fscloud on a live stream and heard it has happened on Vpilot too, so it appears its not just unique to Joinfs. I've been using 3rd party AI both freeware and payware since day one of using JFS which is why i've never experienced the engine cut issue first hand. I do feel careful model matching is the way forward for now.

Darren