AJZip2

Let us know how it goes. Once I'd sorted out the Datalink stuff, I did have a successful and faultless flight in the E-170 (and inside and out, it's a beauty!). But then I had another go - trying to repeat exactly what I had done the first time - and this time had all sorts of problems similar to yours. So I've put it to one side at the moment and moved to something much, much easier to at least get some proper flying in. What do I class as a lot easier? The study-level iFly Boeing 737 Max (yes, I know). 3 attempts from cold & dark to final shutdown & 3 successful flights from cold and dark to final shutdown.

I had something very similar recently. In my case, it was that I had errors in my Navigraph user name/number set up. There are multiple set ups (at least 2). You have to put your u/name in the EFB settings but additionally in the MCDU somewhere in or related to the Datalink stuff. And your problem is probably linked to the Datalink setup/use in the MCDU. It's complicated and unintuitive and so reference to the user guides is strongly recommended - but I did find that those aren't fully up to date with the recent updates. Hope this helps.

I don't think for one single moment that I will be able to repeat this but: After multiple attempts to get an FPS flight of the E-170 happening at all...and that is after uninstalling everything to instruction, including the WASM clearing app, and re-installing to instruction now 6 times (!!)... I have repeated all the same steps to attempt to get this thing to fly properly at least once in 7 times of trying. But this time, it was with a vow that if/when I got an inevitable 7th failure, I would delete the E-170/175 from my system and absolutely not try to reinstall for at least another 2 years. Well, maybe it was the white heat of anger that warmed up the hot PC even more; maybe it was the multiple blows of fist against keyboard; maybe it was the increase in blood-pressure medication to the maximum allowable for an adult male; maybe it was the threat by MrsAJZip of the consequences of "one more ridiculous outburst from a grown man that ought to know better!". And, as we all know, Einstein is quoted as saying that repeating exactly the same steps and expecting a different result is the mark of insanity (or something along those lines)... Anyway - I DID repeat those same steps for a 7th time... and I DID get a different result! This time I DID complete an AP flight from EGPD to EGPH, climbing to 14000', then descending - all in line with the altitude profile - down to a perfect ILS approach, only needing to switch back to manual when at the threshold. Everything worked!! And because I wasn't looking through a red mist, and because the autopilot had everything in control, I could actually spend time switching to external view - and this aircraft is indeed a thing of beauty!!! As I said at the beginning, I don't think for one single moment that I will be able to repeat this - but it does, maybe, make the years of waiting worth it... 😁

I'm afraid I'm abandoning this for a while until there are some up to date videos of how to get the data link communicating, etc.. Can't waste any more time on it at the moment.

Re-deleted the package and purged the WASM and then did a full reload after wasting a few hours this morning with the E-170 not responding to anything. Hey presto, when I reloaded it, I spotted it was now Version 1.0+Patch1, which is what I presume @longhaul747 also refers to above. And yes - that version seems to work... I'll try another proper flight this evening...

Ah - of course. I should have thought of that. Many thanks - I'll have a look next time I'm on. 👍

Can someone remind me how I activate or brighten the Autopilot button/commands LEDs? I activate the various buttons and it shows on the main screen but the LEDs don't light up, even dimly. I'm pretty sure I've been here before and that there is a twist knob or switch to activate or brighten the LEDs. Anyone know/remember? Just did a quick flight and most everything else seemed to work OK other than poor/offset cursor focus in VR of the MCDU buttons resulting in multiple incorrect letters and numbers being chosen. I'll re-read the full procedures and systems and in the coming days will try to repeat a pretty decent flight I did in the previous incarnation and see if the odd quirks I came across then are now resolved.

Vauable information - thanks for posting. Might be worth dropping a line to the FSUIPC developers (they maybe on Discord or have a direct help line ?).

Have just remembered why I need it. I have a number of Flight Panels configs to use on my Elgato Stream Deck+ so that I can more easily adjust twist switch alt, speed, rate of climb, etc by 'feel' when I'm using VR. Flight Panels' configs all use FSUIPC as far as I know. Might be a good excuse to get a MOZA!! 😉

I'm away from my main computer at the moment and can't think why any of my peripherals need fsuipc. When I'm back on I'll delete it and see what stops. It would be good if I can do away it...

Yes - one of my addons or bits of hardware also requires FSUIPC (can't remember offhand which) and that is the only reason I still run it. If you do need it, it's certainly worth trying the updated version - I don't think it updates automatically. I don't know, but it is entirely possible that the update went in because of a change in MSFS which has caused a clash. You can always delete it again if it screws things up again.

I think you might be onto something with FSUIPC. Last week I had some unusual issues relating to differential braking. Although I was never sure what the core problem was, now I think back I ended up with having to do an unexpected FSUIPC version update amongst the other stuff. Try first turning off FSUIPC and if that solves your issue. If it does, iit would be worth uninstalling FSUIPC and loading up the latest version before trying it on again.

I have no problem participating in early releases, and have willingly and happily done so with this and a number of other products. Being pragmatic, I suppose my only concerns are: whether MSFS 2020 support ceases before a native MSFS 2024 version of the E170/175 is introduced whether even the present MSFS 2020 version comes out of Early Release before I reach my statistical full life expectancy Other than those ponderings, I look forward to 1.0 release - I found the last update quite encouraging.

OK - that's an important result. Did you try the flying the F28 itself again using the same controllers and is that still running OK?

I fly the F70 and F100 quite a bit at the moment and haven't noticed anything unusual about the controls assignments. Just to eliminate a few of the possibilities, have you tried flying the F70 but using your OK F28 profile? If so, did that work broadly OK?