The base type for the ToLiss A321neo profiles are all set to A321 and should instead be A21N as the FSLabs and iniBuilds A21N profiles are set.
ToLiss:
FSLabs:
This can cause problems downstream of SimBrief for programs that are matching up aircraft types with SimBrief profiles.
Hi, the ToLiss profiles are provided by Tim (@Rodeo314), and are the same as the ones as here I believe.
The A321neo profiles were created before SimBrief had a native base type to use, and Tim has not had a chance to remake them (which requires some work as he would need to re-test the fuel factors). The current profiles should still work fine as the fuel factor has been tuned to account for using the A321 as a base type.
Any downstream add-ons which are affected by this are probably reading the wrong variable from the API. They should be reading the <icao_code> variable, not the <base_type> variable to avoid this exact issue. But I acknowledge that this situation isn’t ideal, especially if the affected add-on is no longer being updated.
Could you list which add-on(s) are affected by this?
Cheers,
Vamsys is apparently one of them, as indicated here:
Regards,
Tim
Yes, vAMSYS is what prompted this post.
Just to follow up, a few weeks back we coordinated with vAMSYS on a fix for this. Presumably they will implement it on their end shortly.
For future developers who see this topic, the API now returns a <list_type> attribute, which can be used to more reliably sort airframes into the correct aircraft type (regardless of which base type was originally used).
Best regards,
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
