@scoobflight, I agree that differences in AIRAC versions between the flight plan and the aircraft may cause issues, if the waypoints, navaids, sids, stars, etc. are not the same between the different AIRAC versions. As mentioned above, when I was using the FeelThere E175 and E195 V2, I had several stored flightplans generated by Simbrief, using different AIRAC versions, and was able to select a flightplan and not get a CTD. It is only since I've upgraded to V3 that this issue has occurred.
I have compiled the attached 3 flightplans all in the current AIRAC 2001, to allow this issue to be tested by FeelThere, should they want to. After saving each flightplan, I then went into P3D and here is the sequence of events:
EGACEHAM01 created - this was the only flightplan saved in the CustomDB folder. Loaded saved flightplan successfully into FMC
EHAMEDDM01 created - now 2 flightplans in CustomDB folder. Although EHAMEDDM01 is displayed in the list of flightplans in the FMC, it cannot be selected.
CYYCCYVR01 created - now 3 flightplans in CustomDB folder. All 3 flightplans displayed in FMC. I select the 2nd entry on the list (EGACEHAM01) and the CTD occurs.
@Matty260191, if you look at the attached flightplans in a text editor, and compare the waypoints with those listed in the corresponding PDFs, you'll see the SID and STAR waypoints aren't included. Maybe this is the reason @rwalls and I are experiencing this issue and you aren't. I've checked to see if there is some option in Simbrief which controls this, but I can't find it.
For now I can workaround the issues by only having 1 flightplan stored in the CustomDB folder.
EGACEHAM_PDF_1578342435.pdf
EHAMEDDM_PDF_1578342286.pdf
CYYCCYVR_PDF_1578341615.pdf
EGACEHAM01.nz2k.fpl
EHAMEDDM01.nz2k.fpl
CYYCCYVR01.nz2k.fpl