[GSX] SimBrief error: can't read the aircraft type (B788)
This is the [GSX] SimBrief error: can't read the aircraft type (B788) chat channel, created by ibrohim (ibrohim), 2025-08-05 19:11:08.288Z
Hello BravoAirspace team,
First of all, thank you for your continuous efforts in improving GSX Pro.
I would like to report an issue that occurs when I use GSX Pro with the Boeing 787-8 (B788). After generating a valid SimBrief flight plan and loading it into the simulator, I try to reload SimBrief data from the GSX menu, but I receive the following error:
"[GSX] SimBrief error: can't read the aircraft type"
Everything seems to be set up correctly in SimBrief, including the aircraft ICAO code (B788), and the SimBrief profile is linked properly in the GSX Config.
However, GSX is not recognizing the aircraft type when attempting to fetch data from SimBrief.
Could you please look into this issue and release a fix if possible? I would really appreciate your help.
Hello,
I want to try this. Do you stream it on MSFS 2024? Or did you download it? Please let me know just a bit more so I can adjust my settings before testing.
Hello Thanks for your reply!
I’m using MSFS 2020 (not 2024), and I downloaded the aircraft — I'm not streaming it.
Let me know if you need anything else from me for testing.
I am using the B787-8 aircraft. When I press the "Reload SimBrief" button in GSX, I get this error. I'm using MSFS 2020. Please help me fix this issue.
I'm going to test this today in 2020. I'll get back to you.
Even on your side, this issue appears to be caused by the aircraft.cfg file — I figured that out. However, I couldn’t find the aircraft.cfg inside the aircraft's folder. I wanted to fix the problem myself, but since the same issue appears on your side as well, I kindly ask you to please fix it as soon as possible — I’ll be waiting.
GSX is very harsh on our aircraft. We make updates to the profile very often. Very delicate software.
Which airport is this? I'm going to make a test right now.
Can you tell us in which folder is the gsx profile installed?
Hello,
First of all, let me say that the GSX profile works without issues on the B787-800 model. But what I want to point out is this: when I create a plan via SimBrief and then press the "Reload SimBrief" button in GSX, I encounter this behavior. This is not an airport-related problem, but rather an issue with the aircraft.cfg of the airplane, where the name is written incorrectly. That’s why this error happens.
I wanted to fix the problem myself, but the aircraft.cfg file does not exist inside the aircraft’s folder. So, only you can fix this issue.
To summarize: take the B788 model, create any plan from SimBrief (for example LTFM → EDDF), then open the GSX menu and press the "Reload SimBrief" button. After about 5 seconds, the button will turn from red to green. Do you know what this button does? When you press it, GSX reads the SimBrief plan and determines how much fuel, payload, and passengers are required for the flight. Then, during boarding or refueling, it loads exactly that amount into the aircraft according to the route plan.
I tested this with the free Kuro B788 downloaded from flightsim.to. When I created a plan in SimBrief and pressed "Reload SimBrief" in GSX, it worked perfectly—the button turned green.
What I mean to say is: I really love this aircraft, that’s why I bought the payware version instead of using the free one. Its quality is much better compared to the Kuro B788.
Fixing this issue should be very easy for you. Please, I kindly ask you to correct this in the next update. I am eagerly waiting for it.
PLEASE FIX IT!!!
If you look at the file, it is named incorrectly as ge/8.
It should be named B788 instead.
This mistake is the reason for the error.
PLEASE FIX IT!!!!
Hi,
Please update your package. The file was updated.
Thank you! I downloaded the GSX profile v4.1 from flightsim.to and copied the airplane file into the Virtual folder. All issues have been resolved. Many thanks to the team, and I wish you the best of luck!
Thank you for your support. We really appreciate it. Thank you for being patient.