Good you shared. They still have a lot of work to do…
They made the fatal mistake of not promting the new improved stuff while issuing a pile of warnings instead. But all worth noting non the less.
2 Likes
Yep, I was considering giving it a go over Christmas, but these are still fundamental issues. The FD take off sequence is not a minor phase of the flight. I’d rather spend my time then in other cockpits that are more realistic like the 737 or Fenix stuff.
EDIT: I just did a quick flight, a take off until climb, and man, this is still very very buggy. After all this time it still cannot compare to any of the other developers. Even the CRJ, by many considered not perfect, is still waaaaay better than this.
2 Likes
Can you elaborate a bit? I’ve had three flights with this latest public build and I haven’t noticed any major issues with the cFMS/LNAV/VNAV (which are actually main features they’ve been working on in recent months). Unlike PMDG, Fenix or even Aerosoft CRJ the whole product is still marked as experimental with bugs and limitations present, so instead of being primarily negative about it it would help to report bugs you encounter to FSS. This way we can finally reach the v1.0 eventually.
Apologies. This aircraft is so overdue of being finished. I paid I think 2 years ago with the promise it would be ready within 6 months. What wasnt working for me for example was AT, speed was going everywhere, while it was set in VNAV with speed automated set at 250 kts. It went to over 300 kts…
3 Likes
Never happened to me. Actually the AP always honours the FMS speed for me. Can you please make some screen next time? I would report that to FSS Discord if you don’t do Discord.
Also before take-off it’s necessary to activate A/T (white TO indication appears on the left side of PFD) and push the G/A button on the throttle.
2 years… and we get this? Overshooting waypoints? Aggressive and sudden descents in vnav? Overall very unstable. Wasm crashes… I hate to say it (because this could be my favourite plane) but these developers are simply not up for it. Every (major) studio can do this in half the time. I’m giving up, I guess.
7 Likes
On the real aircraft you press TOGA at the gate (to set FCP modes), on the runway arm AT then move thrust levers forward for autothrottle to engage. Pressing TOGA won’t engage the AT for take-off.
I didn’t say TOGA will activate A/T. The A/T button does. And pushing TOGA at the gate is not a law, I guess. I’ve watched a stream with IRL E-Jet pilot the other day and according to their SOP they activate TOGA right before the runway line-up.
The AT button on the FCP arms the AT, autothrottle is engaged by moving the thrustlevers forward.
Yes, I know that. I have no idea why you’re correcting me when I’ve never said that TOGA button activates A/T or makes throttles advance.
According Embraer SOPM it is done during cockpit preparation (that is how I learned it during type training).
Thanks. According to his airline SOP it was activated before the line-up.
Okay, finally got to it today (yesterday I just kept getting delayed lol), so here are my thoughts after one 175 flight more or less in order of them:
- the lack of proper
checklistprocedures guide is a bit of a pain since I have no clue how to set up all the data, plus some elements still being locked put a damper on a proper workflow - a bunch of systems pages still out, can’t check hydraulic or aircon
- I know they’re still redoing the key mapping, but I have to address that some crucial bindings do not work - heading and the yoke red being the most prominent for me
- take-off navigation is indeed very bad, but it calms down before we should begin to follow it anyways;
- the climb respects the restrictions, but still does the dumb FLCH thing where it stops the climb to get the airspeed - and way too abruptly, too
- aircraft not being shown on the chart is a small nuisance
- man it is wobbly, very sensitive to wind changes; maybe the 195 would be more stable
- some weird error where it’s decided on an “UNABLE CRZ ALT” and stopped me 7k feet lower, on previous waypoint’s altitude? likely caused by the above, can’t imagine it’s not already reported for a fix
- oh it also didn’t change over to Mach after crossing the number, another long-standing issue like the FLCH one
- okay, it captured PTH while I was still climbing, an unexpected but welcome surprise
- the calculated speeds of “290/.24M” are a bit more worrying, also I cannot change the transition level on this menu - not a problem here, but this field shouldn’t be the same as the transition altitude
- also would love to get some landing calculations on the EFB since I can’t tell what braking action to use, and the computed speeds for take-off differed between computer and tablet. Or some estimation of the landing weight to enter into the flight computer
- oh it did NOT like the direct, completely ignored any restrictions and dived to capture the path, both lateral and vertical (it didn’t treat it as a direct, but as a new line from the previous waypoint to the next one - a big no-no)
- another massive issue: it kept me on a vertical path below the ILS and did not capture it all the way down, keeping me below the slope. This is how you get a CFIT
- idle reverse seemed weak but that may be me landing with tailwind and forgetting to pop speedbrakes, need to fly more
To sum it up, I am glad that this milestone has been reached, but it is clear that there is a ton to do still in regards to the vertical/speed computation. And also, happy to be proven a pessimistic clown that did not believe FSS would have something to show by the end of this year 
Edit: one thing I forgot - I’m not sure how much of it is the lightning between night and day, but the cockpit seems different; I like it better now
6 Likes
“Also before take-off it’s necessary to activate A/T (white TO indication appears on the left side of PFD) and push the G/A button on the throttle.”
I interpreted this post as needing to ARM AT via the FCP then pressing TOGA to activate, guess that is not what you meant.
No, I was just checking @TFEV1909 did necessary steps before take-off to have AP+A/T work in his favour during take-off and climb.
1 Like
A great sum-up. Are you on Discord? It would be great if you post it there. There were some people in the beta team suggesting it’s not quite yet ready for public release but I guess FSS, after all those unfulfilled promises and many delays and postpones, were just pushed to release it. I agree there is still a lot of work to do.
Nope, I’m too busy to enroll in the beta and they did explicitly ask to not send them reports, so I’ll keep it here - but if you wish to cross-post it there, I don’t mind
I’m with FSS on this one because this would be yet another broken deadline, even if they were careful about setting it - this project already has a bad enough reputation. Plus, it’s not a full update, we still need to jump through a few hoops to get it - so anyone who cares more about the stability can still remain on 0.9.34, while the messy version goes to those that agree to get a bit dirty
2 Likes
I did. (10 char)
1 Like