That’s basically what I see. Instead of another B777 I see this yellowish A330 or whatever it should be.
Hi All,
Regarding simbrief import, it doesnt appear to be importing “perfinit” it appears to be only half complete.
No ZFW for example?
Is this normal?
After you do the import, click the button next to the ZFW weight. The imported value should appear in your scratchpad line. Copy it to the ZFW field by pressing the button again.
2 Likes
Thanks Frag! Yes - it should not make any difference if FSX or MSFS - as long as it is 777 & RNAV it’s great! Will check!
Yes, that’s normal. For the ZFW you need to manually enter it or do it as @DrVenkman3876 suggested. Gross weight is then calculated, so it’s the only value you need to take care of. The rest is imported.
1 Like
Than you bery much @DrVenkman3876 and @mhron
2 Likes
not a problem at all mate, So basically, you don’t hit app, you set your alt to the final approach fix when you are on approach, set your alt to minimums 300ft etc, then when you noticed v/lnav armed on glideslope area (where you see the ils if your in ils mode) then you dial up your missed approach alt and the plane will do everything like it should on the 737.
Do this approach, this one works a nice tight one…
OK - just tested it and it worked well. I apparently forgot to update my 777 with the latest Navigraph Data - maybe this caused some issues? Not sure - anyway - this time it worked well. I just think that it might be a good idea to reduce speed early on - the SPD as per FMC might be a bit high. Instead of e.g. 240 I would dial in 210 etc. This way the plane has a bit more time to sink accordingly.
1 Like
Just have closed another nice flight 
I’ve interrupted it in middle for test. After reload all ok but as I reported, initial set DCT to next waypoint is required so LNAV can work further. Yes, after landing brakes are not functional, simply all as keyboard defined also as example. Just lovely flight from EDDM-EGLL 
aaaah forgot to say, fuel disagree message I’ve cleared in PROG page 2 or 3??? where I’ve click USE fuel value same as on left side. After this change warning message disappeared but sry if this is correct way I don’t know. Nothing else I remember as important now…
This is a known issue and is well documented.
You can try AIG which you can pick and choose a couple airlines to download models for and it’ll match up so long as you have enough to cover most vatsim traffic and not junk up your hard drive.
The downside is you may not get accurate company matching too. If you only download AAL, UAL and DAL models, the ACA 777 in front of you may show up as one of those three airlines anyway
For what it’s worth - did my first flight from EGKK-KBOS and everything worked
smooth. No problem with framerates or any other issue I could find.
Out of the box it’s full of features … that work!
This is how it should be done developers … no early releases with no features and waiting for the developer to add 1 every 6 months!
3 Likes
Quick shoutout to all 777 painters out there! Thanks for all of that beautiful work!
2 Likes
“This parking is too small for this aircraft”
Ok now for the second time im getting this voice message all the time while setting the cabin up. After 15 min working on the FMC , overhead panel etc… i start to hear:
“This parking is too small for this aircraft”
I´m on a LARGE ramp as always with plenty of space
anyone knows whats going on?
The scenery gate coding is set to the wrong size or something along those lines. If you’re using GSX, there’s a setting to ignore sizes.
1 Like
Important next news from my tests.
To my previous post to which I now answering, brakes are working after save and reload flight only at ground. This means that if I have saved flight at FL and reload this flight back, after landing are brakes not working. Now with this test it means that if I have no saved flight and land at airport, at this time on ground if I save my flight then brakes are functional. It is definitely 777 issue to my opinion. Hope all will be sorted quickly
Plenty of space? I see basically your tail behind white line so really don’t understand why you’re asking what’s going on here
4 Likes
If it helps, you can ignore the parking size warning by opening the GSX settings and hitting the checkbox to ignore gate sizes. You won’t get the text or audio warnings anymore. As DrVenkman said, the scenery has that gate configured in its metadata for a smaller supported aircraft size.
I see this approach as typical VNAV profile copy and not as expected with FAC glide path indicator.
To me, this isn’t still implemented on 777 as is expected (also working on 737) but all need say any one who has IRL experience or PMDG
The 777 doesn’t operate like the 737. RNAV/RNP approaches are flown in LNAV/VNAV, not approach mode.
The correct procedure is:
- Check all legs page waypoints to ensure the altitudes are correct and in large font. Also check Progress page 4 to ensure the Vert RNP is set to 125ft.
- Ensure LNAV & VNAV are selected.
- Once past the IAF, set the FAF altitude (or slightly lower if not an even 100ft) in the MCP.
- Approaching the FAF, (2nm is standard at my company) set the MDA/DH altitude in the MCP.
- Passing the FAF, ensure VNAV PATH is annunciated, and the RNP value on the ND is correct, eg. 0.3nm.
- After passing the FAF, and when at least 300ft below the missed approach altitude, set the missed approach altitude in the MCP.
- At MDA/DH, if a runway waypoint exists on the legs page, leave the flight directors on and continue. If a runway waypoint does not exist, both flight directors must be switched off. The PM then turns their flight directors back on, to ensure the correct modes are engaged in the event of a missed approach.
11 Likes