This, and a couple of other things reported on this forum, are being investigated so I'd recommend leaving the DC-8 in the hanger for the time being.

The installers were tested on several PCs with different operating systems and in all of the compatible simulators and we didn't encounter any issues, but as ever that doesn't guarantee that it'll work for everyone. We'll get it fixed though.

Which version of Prepar3D and SimConnect are you using? After launching a flight, go to Help > About Lockheed Martin Prepar3D on the top menu bar. We need to know the Prepar3D and SimConnect version numbers.

It's a lot easier to investigate this over email, allowing us to collect data which might pinpoint the issue, so please submit a support ticket if you haven't already.

I could not get P3Dv4 to launch when I selected the Tr-Star 500 model, but had no issues with the Pro model other than a very distracting cockpit lighting reflection in the glareshield with night time lighting, albeit on a very short circuit around the default airfield, Elgin AFB.

I'm not sure what the difference is between the 500 and Pro models? All of the variants should be labelled as JF Tristar 500 Pro and then the airline name. There should be two variants for each livery, one ends in 'FMC' and the other 'INS'.

If the ones ending in 'INS' load OK then that might indicate an issue with loading the FMC gauge.

The P3Dv4 'Select Vehicles' option listed Tri-Stars as a 500s with the relevant livery, as well as further down the list Tri-Star Pro models with relevant liveries again. I will send the screenshots later as I'm at work.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot delete your posts in this forumYou cannot edit your posts in this forumYou cannot create polls in this forumYou cannot vote in polls in this forum