First days of the C414 there was also no livery available.
And even to this day there are not shiploads of good ones.
Only the mainstream aircraft models that everyone likes (and knows) receive lots of them.
It says something about interest maybe. If you’re only interested when everyone else already is that’s fine by me.
What defines my interest is that the aircraft is worth the money when purchased, not what others are interested in. But 40 eur now and the price only rising in the months to come, it surely will have to be study level to compete!
Don’t mind paying a lot more, but it will have to be quite good to compete with the other
aircraft that are coming this year. But time will tell.
I’m not gonna judge them harshly based on an early access version, but I’m gonna wait for the final E175 release myself. 
Finally I bought it. I let the chance to the dev to improve their product. For the moment, for my personal use, it is far to be usable. LNAV bug at each flight (turn back to previous waypoint already overfly/restart the nav), I don’t find a way to do a correct hold, ILS is a nightmare and I respect all the procedure wrote in their website. I know it is the msfs navigation system for the moment, so I don’t expect anything else than what I observed. But 40E is too much for what it is. My bet is that latter it reach the level promise by developpers and I will be happy.
The most incovenient for the moment for me is also the lack of support. I would like to have a forum/discord/anything to talk with developpers or other users to share our experience, ask question ect…
So finger crossed for this projet
well… why not ask them directly in their discord
Because I have looked for their discord and never found it.
If you have the link I will be really happy.
I hope this works:
FSS is not the friendliest name to google or find and already some other devs have been wrongly spammed about E175 stuff.
Thanks a lot.
2 days I have passed on internet/discord and never found it.
I purchased this aircraft on Tuesday, and have been enjoying learning to fly it. At first it was very frustrating because with my CH products yoke the throttle would only work with the starboard engine. Tried reinstalling, but this did not work. All my other planes, like the Boeing 737 and Cessna 414 work fine, and the throttle lever controls both engines. Resolved this by using the normal throttle lever for the left (port) engine and the central lever, normally used for the propeller RPM, for the right (starboard) engine. I made a test flight from KPDX (Portland, OR) to KSEA (Seattle, WA), which included programming the FMC. This was successful, even though the ILS is not yet functional. I could follow the localizer and adjust the heading as necessary. The glide slope did not work, but the display did show whether I was above or below the glide path, so could adjust the descent rate as necessary. Not great, but I can live with it for now. Turned off the autopilot and finished landing manually.
It would be nice to be able to adjust the map view distance, but if there is a way to do this I don’t know what it is.
Overall I am very satisfied with this plane, and am looking forward to the free updates for the 170 and 175.
Apparently there isn’t a paint kit released yet, so that might be why.
The throttle issue is a known bug which according to the developers will be fixed in the next update. They linked the physical throttle to axis 2 so axis 1 stays idle. The solution is to link both axis 1 and 2 to the throttle set as many other developers did.
For the meantime you can go to your controller settings and setup throttle axis 1 and 2 to the same input as the throttle set.
There is a touchpad with 3 knobs and 1 rotary knob. Push the middle knob of the three. Then you can use the rotary to zoom in/out of the map.
That’s how I mapped the throttle slider on my TCA Sidestick for now until throttle calibration is added in the next update.
Thank you very much for showing me how to adjust the map zoom. It works perfectly, with a separate zoom level for each display.
I’m already having a blast with this thing and am looking forward to the update next week and all the greatness which will come. I am now sure they’ll prove all naysayers wrong and it won’t take them 1-2 years to do so - like some people suggest. If you’re bug-intolerant then better stay away right now but you won’t have to wait long before you want to reconsider - i bet. 
is there an eta for vnav? i only remember them saying "soonish"™, but nothing precise.
VNAV is not the only thing that matters.
My understanding is: getting each and every system right first and then finally do VNAV.
So i‘d say: not soonish.
So for the ones that are all about ‚can i has vnav?‘ you better wait. No eta was given for that and if an eta is known you‘ll probably read it here.
from what ive gathered it was/is one of the most discussed systems, thats why im curious.
I know. Sadly the 5hings that are most discussed in public are not the most important things really.
After MUCH internal debate and research, I decided to go ahead and try the E175. My thought: the negativity is a bit overdone. It’s not a bad aircraft. It looks really nice, the displays are well-done, and it flies decently. Sounds are a little quiet for sure. There’s no getting around that the FMS is kind of a disaster right now. This is the autopilot flowchart:
ILS is simply unreliable. The plane is perfectly hand-flyable, but don’t expect it to fly itself down to the runway. It takes a little effort to figure out how the speed control for the AT and the FLCH system work together… but they do work. VNAV is absent, as is well-known. No Simbrief importing, and I don’t see how direct-to commands can be entered (if they can at all).
The bottom line is that it’s about at the same level as the stock A320 right now. Which is a perfectly decent starting point for what they (FSS) hope to achieve with this. The problem is that the most visible missing items are the most high-profile ones in the aircraft. The E175 has a lot of automation, and if you’re not triggering failures, you’d never know whether or not most of the systems are implemented or not, because they’re all “set one switch to auto and you’re done” type controls. But Simbrief and VNAV and ILS are things that users are going to interact with every time they touch the plane, so their absence is more glaring.
The main problem is the price. It’s not a bad plane, but it’s definitely bad for a $40 plane. (36 euros give or take) If it was half the price, I think the problems would be easier to overlook in the short run.
