IFE F-35 CtD in P3D V5

[brettt777]

I have three versions of P3D on my PC; 3.4, 4.5 and 5.3. I also have 5.4 but it isn't installed cuz none of the V5 aircraft, or VRS Tacpack, are compatible.
Anyway... I installed the IFE F-35 in all three versions. It works fine in V3.4. In V4.5, the F-35 works great... except it has no afterburner. In V5.3, it loads for about 5-10 seconds, then CtD. The OEM stripped down version of the F-35 in V5.3 works fine. But that's not the one that is Tacpack compatible. Seems to me this used to work in a previous installation, but I cannot get it to work now. I have tried it with the OEM F-35 in place and with it removed. Same thing, CtD after 5-10 seconds.
So, anyone have afterburner issues with their IFE F-35 in V4.5?
Or, anyone have CtD issues with their IFE F-35 in V5.3?

[JorgenSA]

So, have you talked to the developer in question?

And, what is in Windows Event Viewer at the time of the crashes?

Jorgen

[Martyson]

I have three versions of P3D on my PC; 3.4, 4.5 and 5.3. I also have 5.4 but it isn't installed cuz none of the V5 aircraft, or VRS Tacpack, are compatible.
Anyway... I installed the IFE F-35 in all three versions. It works fine in V3.4. In V4.5, the F-35 works great... except it has no afterburner. In V5.3, it loads for about 5-10 seconds, then CtD. The OEM stripped down version of the F-35 in V5.3 works fine. But that's not the one that is Tacpack compatible. Seems to me this used to work in a previous installation, but I cannot get it to work now. I have tried it with the OEM F-35 in place and with it removed. Same thing, CtD after 5-10 seconds.
So, anyone have afterburner issues with their IFE F-35 in V4.5?
Or, anyone have CtD issues with their IFE F-35 in V5.3?

Hello brettt777 ,

I have IFE F-35's in P3D4.5HF3 (4.5.14.34698)

No CTD.
No problems with the F-35's, TacPack or the afterburner.

[KevinKaessmann]

I have IFE F-35's in P3D4.5HF3 (4.5.14.34698)
No CTD.
No problems with the F-35's, TacPack or the afterburner.

@Martyson: maybe you have downloaded a newer version ?
At simmarket, I find a F-35 LIGHTNING II PACKAGE P3D Version 3.50 update from July 30th 2018.

If @brettt777 talks about an older FSX installer, it may explain his troubles ?!?

[Martyson]

@ KevinKaessmann ,

Do you have the IFE F-35 installed?

[Martyson]

Hello brettt777 ,

Follow up.

Today I tested the IFE F-35 (No TacPack) using P3D Academic 5.4.9.28482
No CTD
Afterburner OK.

[KevinKaessmann]

Do you have the IFE F-35 installed?

No, sorry.

But according to http://indiafoxtecho.blogspot.com/ the package is available for free and simmarket offers it for 0 $,
so it seems to me, it could be easily ordered and downloaded to compare the files.

Or maybe a version number is contained somewhere in the aircraft folder, so you two can compare it ?

[Martyson]

Ok.

The OP had mentioned:

"The OEM stripped down version of the F-35 in V5.3 works fine."

I have no idea on that one so thought you possible had some IFE F-35 product.

Your previous post:
" the package is available for free and simmarket offers it for 0 $,
so it seems to me, it could be easily ordered and downloaded to compare the files."

Are you going to download it?

[KevinKaessmann]

As my former reply vanished, I would try it more seriously.

First of all, we have to find out what it means:
Anyway... I installed the IFE F-35 in all three versions. It works fine in V3.4. In V4.5, the F-35 works great...

Does it mean "I installed the IFE F-35 in all its three [IFE F35] versions"
(the link from IFE to a Google drive leads to three F35 packages: FSX, P3DV2V3, P3DV5) ?

Or does it mean "I installed [one IFE F-35 version] in all three [P3D] versions" ?

The first is a tough nut as IFE according to their website has dropped its P3D support.
Maybe comparing the installed version against their last package (see below) may lead further ?

The second may lead to the P3D V5 CTDs (or the missing afterburner in P3D V4.5 because of a nonworking 32bit module).
So uninstalling the IFE FSX package from P3D V4/V5 and installing their packages:
http://indiafoxtecho.blogspot.com/ --> paragraph "Projects:" --> F-35 FOR P3D V4 and V5 (64bit version 3.70) --> F35P3Dv370_P3Dv5.exe
in both P3D V4 and V5 may resolve the issue.

But as I'm neither a LM nor an IFE representative/technician, it's a decision and job of the OP.

[KevinKaessmann]

The OP had mentioned:

"The OEM stripped down version of the F-35 in V5.3 works fine."

As far as I understand, the OP compared the P3D included F35 ("stripped down") with the payware IFE F35.
Maybe I misunderstood ?

If not, I assume the nonworking F35 is the former payware, now freeware (and support dropped) "full package" IFE F35.

[JorgenSA]

And if the CTDs continue, then we will need to see what the "Error" entries in Windows Event Viewer are.

Jorgen

[Rogen]

In V4.5, the F-35 works great... except it has no afterburner. In V5.3, it loads for about 5-10 seconds, then CtD. The OEM stripped down version of the F-35 in V5.3 works fine.

But that's not the one that is Tacpack compatible. Seems to me this used to work in a previous installation, but I cannot get it to work now. I have tried it with the OEM F-35 in place and with it removed. Same thing, CtD after 5-10 seconds.

So, anyone have afterburner issues with their IFE F-35 in V4.5?

Or, anyone have CtD issues with their IFE F-35 in V5.3?

No problems with the afterburner in my p3D v4.5 with the IFE F-35 (as pics show).

I do have a bit of a mixed install with it placed into an xml discovery path.

In P3D v4.5 try enabling content logging, load the plane, go to afterburner and then review the logging looking for anything relating to the F-35.

Also no point in raising any issues with the developer as he's moved on to MSFS, I'd actually raised a selection of issues with him regarding bugs when P3D v5 arrived and he basicly acknowledged and said that's the way it will stay.

If LM were a little more on the ball they should have licensed all these (now) giveaways, updated/fixed them and added into their base P3D.

Would be very attractive to have the (now dumped by their devs) collections installed and updated in the sim by LM which I'm sure LM could certainly afford to do.

Cheers

[Martyson]

Hi Rogen ,

You mentioned:
“If LM were a little more on the ball they should have licensed all these (now) giveaways, updated/fixed them and added into their base P3D.

Would be very attractive to have the (now dumped by their devs) collections installed and updated in the sim by LM which I'm sure LM could certainly afford to do.”

What is missing from LM’s current F-35-A , B , C ?

[Rogen]

Hi,

I meant from a persective of all the DEVs now dropping P3D development completely and making their catalogs available for free (with no support).

e.g. IFE's F-35 & other planes, Aeroplane Heaven's collection, MilViz's and Sim Skunk Works for example.

Additionally there are those Devs who have publicly stated they will no longer release anything new nor update their existing collections, like A2A, FlySimWare and Aerosoft for example.

If LM negotiated with these Devs for even just one or two cherry picked items P3D could be a more attractive sim.

It's not as though LM have not done it previously.

Although the general enthousiast commercial sale is not the target of LM's focus, they do need to keep as wide a viable dev base as possible (i.e. general commercial 3rd party sales) so that there is a larger available pool of dev resources for said contracted work.

Alternately make a clean cut with a final P3D release targeting bugs only and go the UnReal way to take advantage of the large number of Devs already familiar with UnReal.

Plus with UnReal there are tools like...
https://youtu.be/czjczrxElkU?si=Rk3mZ5-aBFCAndu5
https://youtu.be/z2_SODMTwhM?si=iof2soVxd31sJ0sP
https://youtu.be/TbHCvAo-aGg?si=U9Spi8TRqfHCGWKB

Cheers