When importing a flight plan from EDI-GLA into SimBrief, I am encountering several issues:
The REMARKS field from the flight plan appears under “Dispatcher Remarks” instead of “Extra FPL Info (Item 18)”.
Regarding the cargo/payload management, no matter which configuration I use:
Cargo with payload set to 0 or None
Cargo set to 0 with a custom payload value
…the requested value is never correctly applied to the cargo.
For example, if I set a custom payload value of 100 kg, this value does appear correctly in the OFP. However, when importing into the Fenix A32X, only the baggage value is imported, not the actual payload.
The current behavior is quite confusing and does not seem to follow any operational logic.
While waiting for a fix or guidance regarding the correct method to use, I would like to thank you in advance for your help.
Regarding the first part, when you click on the Simbrief button on edi-gla, the URL that opens a Simbrief plan is contructed by the edi-gla website, not Simbrief, so the fact that they assign the remarks to the wrong field is outside of Simbrief’s control.
Fixing this will require edi-gla developers to make changes to the URL they generate (but of course, if they need any assistance on how to do so, they are welcome to enquire here for guidance).
Regarding the way the cargo is applied to the Fenix payload, it is also the Fenix Simbrief importer that’s most likely at fault-- when you generate a plan, Simbrief makes the data available as XML or JSON for import by third-party aircraft, and document the format, but assigning a given field to payload in thew aircraft is controlled by the aircraft addon’s code, not Simbrief.
This could simply by a limitation or design decision by Fenix rather than a bug per se, but given a specific example (say, the way you set up the flight, plus the PDF, plus screenshots of the payload setup in the Fenix after importing) we can investigate further.
The first step (“the way you set up the flight”) can be shared as a URL here:
You would first set up the options (including cargo and freight as desired), and copy then share the URL just before you’re ready to click “Generate Flight”.
Thank you for your feedback. I have sent a message to EDI-GLA to suggest this modification idea.
Regarding the second part of the message, I think I have identified the issue.
When I create a flight with an aircraft already present in the hangar, I set the baggage weight per passenger to 0 kg in the aircraft settings. Indeed, not all passengers have baggage, and the default baggage weight was far too high compared to reality.
I therefore set this value to 0 by default and decided to manually manage the cargo section for each flight.
However, when I import an aircraft from EDI-GLA, the aircraft is set to “default” status — see screenshot. As a result, the baggage weight is automatically set to 25 kg by default.
Since the Fenix only reads the “Cargo” tab, even if a manual value is entered, it is always added to the default baggage weight calculated according to the number of passengers.
It should therefore be possible to choose the baggage weight per passenger when the aircraft is in “default” status, as it is after an import from EDI-GLA, without having to go through the hangar settings.
Wouldn’t the only real solution to this simply be for you to manually select your custom airframe after importing from edi-gla?
Not sure how exactly Simbrief would implement luggage weight controls for default airframes, but let’s say it did:
you would still have to manually adjust baggage weight somewhere
thus manually changing the selected airframe is just as easy (probably quicker, too)
any and all other customizations (empty weight, equipment, engine type, fuel bias, etc. etc. etc.) you made to your custom airframe are all absent from the default airframe as well
thus manually changing the select airframe is arguably required anyway
I agree with you, but when I load a custom airframe, it automatically changes all the values imported by EDI-GLA in the Extra FPL Info, ICAO Equipment, PBN, Transponder, Mode S, Registration, etc.
That is why I was suggesting adding an extra “Default baggage weight” field, with a small save icon to store this value — similar to what already exists for Contingency Fuel, Reserve Fuel, etc.
If a developer could give their opinion and look into whether this would be feasible, that would be great.
