I had this problem because I entered my user name instead of Simbrief ID (numbers).
Alternatively you can set up Simbrief downloader like shown below, if you have Steam version of FS2024. The plane will read local files instead of downloading flightplan from Simbrief servers.
I have had a similar problem (could not remember if it was with the 737max) which was solved after taking a look at my anti virus/ firewall software quarantine folder and reinstall the blocked file.
Just a quick reminder - Zibo 737 is developed specifically for X-Plane and that alone makes direct comparison a bit problematic. The flight models, physics engines and system implementations are fundamentally different between X-Plane and MSFS so any similarities or differences in hand-flying behavior may not translate accurately.
If you’re really keen on comparing the Zibo with something in MSFS, it would make much more sense to join the discussion about the PMDG 737-800. That way, you’re comparing two study-level addons of the same aircraft model within their respective platforms.
Well, this is the whole point of my post. Why two study level planes feel so much different? I don’t feel it when switching between Toliss A32N and Fenix A320. They are also two different generations in two different simulator platforms but hand flying them is exactly the same.
I understand your point, but since you’re comparing the Zibo 737 to another 737 in MSFS, it would be more appropriate to bring this up in the PMDG 737 thread rather than the iFly one.
PMDG staff are active in their discussion topics, so there’s a good chance someone could explain the differences in more detail - including aspects beyond just hand flying.
Hey, yeah, that’s what I did. This didn’t work and than I tried reinstalling and adding an exception to the antivirus programm. The file wasn’t send into quarantine again but the problem still persists. And I’m using my Simbrief ID, not my Simbrief username, so this can’t be the problem.
What’s worth mentioning about X-Plane and Zibo…? (If there is anything worth mentioning) Just in comparison to the team behind each project… In my humble opinion, X-Plane and any aircraft… in this case, Zibo move extremely, too much… fun, yes… not realistic (it depends, of course, on the conditions) but in normal conditions it’s almost impossible to land (Imagine with a 1kt crosswind gust :)…) No real-life pilot could handle those out-of-nowhere and extremely exaggerated movements.
I’ve run into this problem twice with after updates with the iFly Max. When you enter your Simbrief info, you’re supposed to get a browser window popup directing you to the Navigraph site to approve the connection. If that does not occur, you won’t get the approval and you will get the route uplink error message you’re receiving.
The solution I found was to dig around into the file structure of the iFly installation and find the application that was supposed to trigger the authentication popup:
\Community\ifly-aircraft-737max8\Data\Tool
The actual file is called something like navigraph_new.exe - I had to specifically add this program as an exclusion to Windows Defender. (NOTE: I am going from memory here - not at my PC and it’s been a few months since I ran into the issue).
Not 100% sure on this, but isn’t there a tube above the front windows, which if you click on, a removable visor will appear that you can slide from side to side?
Maybe this is the Fenix Airbus, but pretty sure the 737 has this
Having an issue with the fuel load not populating to the aircraft I enter all the data in the EFB as normal including the fuel calculated by Sim Brief but the fuel load the jet loaded with remains unchanged (and the jet loads with a “Fuel Disagree” warning on the FMC). The weird part is that this is a brand new livery (from the iFly Manager), it’s the JVation American livery. All my other liveries (which are also all from JVatiion) don’t have this problem. Am I doing something wrong is it possible this livery is somehow corrupted?
Since updating to v4.1 today the ZFW on the PERF INIT page in the FMS does not auto populate the weight when clicking on it, and on the next page where you enter CG it no longer auto populates the CG either.
The performance seems better though which is nice. Smoother overall esp at busy airports where the MAX used to lag just a little compared to the PMDGs. So far it seems on par now with the PMDG 737 performance.
That’s how they work in the PMDG 737NG line. In the iFly, you have to right-click on the LSK next to the field, which should put the value into the scratchpad line. You can then edit that data or left-click on the LSK to enter it. This procedure is straight from the iFly Discord (where I had to look it up myself, lol) and it does work.
However, if you’ve got your right mouse button bound to Camera Free Look (which I believe may be a default) it doesn’t work. You have to unbind the right mouse button from camera view controls.
I uninstalled and reinstalled the aircraft and it fixed it. The iFly installer used to delete the aircraft and then install the updated version, but the new installer just overrides the current aircraft which I suspect caused an issue. All good now.
We have made revisions to the ZFW and CG click system in version 1.0.4.2 for MSFS 2020/2024. Here is how it works now:
If the ZFW or CG LSK field is empty/blank and you left click it, the auto-sensed value will appear in the scratchpad. Left Click the LSK again and the value will be copied from the scratchpad and applied to the LSK field.
You can at anytime edit/modify the value on the scratchpad and apply it to the LSK Field again by left click.
If the ZFW or CG LSK Field is NOT empty/blank, but occupied by a value, when you left click the LSK, that value will be copied to the scratchpad. You can then edit/modify it, and left click the LSK again and the value from the scratchpad will be applied to the LSK field.
The auto sensed ZFW and CG values will only appear on the scratchpad if/when the LSK field is empty/blank and you left click the LSK.
If you modified the ZFW or CG Field values, the auto-sensed value cannot be sensed and applied. So, if you made a mistake with the modification of the value, you will have to consult your load sheet for the correct ZFW value.
The auto-sensed CG value can be located from the PERF INIT page @ LSK 1L (GW / CRZ CG Entry field) or by deleting the CG field value. The ZFW LSK field entry cannot be deleted.
See the previous PDF for other changes that carryover to this 1.0.4.2 update.