8 hours ago, sd_flyer said:

Fenix still has simbrief  lat/long parsing error. I tried several variations of simbrief generated KSEA-PHNL, but Fenix can't export simbrief flight plan giving parsing error. In contrast, PMDG does good job and have no problem exporting same simbrief flight plan. Does anyone know hot to battle this problem with Fenix?

when you use  simbrief  delete   the  lat/long  fixes  and  than import  the  plan  you will  have  no issues   than,  since  just  tried  it

9 hours ago, pete_auau said:

that will work  since  it  hasnt  got  the  lat/long  way points  included,  once you  include  them  than  the  cdu  will  bring  up  uplink error,  where  as  the pmdg aircraft will not  throw  up  any  errors

Almost every time, simbrief shows flightplans with and without lat/long waypoints. I always select the FPs without them. The FP I posted above is from simbrief, about the third or forth one down. 

30 minutes ago, Bobsk8 said:

Almost every time, simbrief shows flightplans with and without lat/long waypoints. I always select the FPs without them. The FP I posted above is from simbrief, about the third or forth one down. 

Yes you can make it so it doesn't but sometimes it is necessary to use Lat long way points when flying over big areas of water. For example I have just created a new simbrief flightplan and it came up with:

HAROB6 HQM SEDAR 43N131W 40N136W 37N140W HELOP A332 AUNTI R463 APACK INOYI1

Yes there is suggested routes down below that has some without but the point still stands that there is a bug within the way Fenix looks at these and is stated on their knowledge site. I believe you can simply change the lat/long codes to a specific format and it wouldn't have a problem. As mentioned at: https://kb.fenixsim.com/invalid-f-pln-uplink-message-when-importing-from-simbrief

TLDR: Yes there is a bug but there is a workaround. 

 

Edited September 8, 20232 yr by Zangoose