The A21N Profile for Toliss by Rodeo314 has the base type as a A321 when it should be A21N so it’s not getting picked up correctly by Vamsys SimBrief integration when trying to add it to a A21N fleet type. It only works when selecting A321 type which is incorrect.
Back when the profile was created, Simbrief didn’t have an A21N profile which is why I went with an A321 and fuel factor altitude offset. Updating them to use an A21N base is on my to-do list, I just never got around to it.
That being said, there’s a number of airframes which exist for aircraft where Simbrief doesn’t have the corresponding base type and Vamsys would likely have the same issue for any of them. This should really also be reported to Vamsys developers as a bug.
Regards,
Tim
Hi Tim,
It’s not a bug with vamsys. The base type just needs changing.
Thanks Rob
I respectfully disagree. Let’s take for example some of the iniBuilds-provided aircraft that ship with Microsoft Flight Simulator 2024:
- A400M Atlas
- base type: A343
- ICAO code: A400
- Beluga XL
- base type: A332
- ICAO code: A337
You cannot set an A400 or A337 base type because Simbrief does not have them. Granted, these airframes are somewhat unlikely to be flown by a typical VA, but still.
What if e.g. iFly were to release a B39M before Simbrief had time to add a base airframe for it? In the meantime, people would be using B38M or B739-based airframes and encounter the same issue.
Or the default Embraer E175 profile; it was initially released with ICAO code E175 but that’s not a valid ICAO aircraft type designator so the profile was updated to use the E75L code, but the base type remains E175 as changing it too would have broken all existing airframes based on it.
vAMSYS should be ignoring the base type altogether and use the ICAO code instead. The base type is really only useful to Simbrief’s backend code.
Regards,
Tim
