December 26, 2025Dec 26 5 hours ago, rayharris108 said: Any help please? I too liked the E-jets in 2020 but missed VNAV. So I was pleased to see it now supposedly works in 2024. I just installed the Experimental version into 2024 and already loaded and then rebooted the sim. I just spawned at an airport for a flight and switched everything on whilst performing a start up at the gate on GPU. I calibrated my throttle and imported a Simbrief flightplan, which seemed all fine. However, the only thing that refused to work was the Honeywell FMCs. What ever I did they remained blank and inactive. I tried spawning on a runway ready for take off and what ever I did, the FMCs remained blank. My understanding is once you power up the plane the FMCs should come on automatically. Since FSS have refused to provide support for this version, Avsim is the only place I can go to. Has anyone else had this problem, or is it something I've been doing wrong? Thanks for any help and much appreciated if anyone can. Hi in MSFS2024 with the stable version, I have same issue too, FMCs are dark. With experimental version, they worked good, however I can't enter some airports for creating a flight plan, the FMC said that they are not in the database, and my Navigraph data is up to date. Another finding is the right EFB, is all white, but the left one at least is working good. Didn't have time to test another features. Alexander Colka
December 26, 2025Dec 26 I had the blank MCDUs a few weeks ago with the stable version. I noticed that Contrail had installed it into the new MSFS 2024 "Community2024" folder. By moving the aircraft back into the standard "Community" folder (Contrail provides an option to do that), the MCDUs came back to life for me.
December 26, 2025Dec 26 On 12/24/2025 at 2:42 AM, flyforever said: They've done such a great job with the 727 that making a 707 would be a natural evolution. Good point
December 26, 2025Dec 26 So has anyone figured out how to get rid of the green activation box? Seems it hangs there and the fmc also has no power. Why did they create this new bug on a version with zero support? Mind boggling but considering the source, not surprising. They refuse to answer any questions. Typical garbage customer support. I wish I had never given them a penny.
December 26, 2025Dec 26 Mine works perfectly in the new folder. I have planes in both folders and they all work.
December 26, 2025Dec 26 11 hours ago, rayharris108 said: Any help please? I too liked the E-jets in 2020 but missed VNAV. So I was pleased to see it now supposedly works in 2024. I just installed the Experimental version into 2024 and already loaded and then rebooted the sim. I just spawned at an airport for a flight and switched everything on whilst performing a start up at the gate on GPU. I calibrated my throttle and imported a Simbrief flightplan, which seemed all fine. However, the only thing that refused to work was the Honeywell FMCs. What ever I did they remained blank and inactive. I tried spawning on a runway ready for take off and what ever I did, the FMCs remained blank. My understanding is once you power up the plane the FMCs should come on automatically. Since FSS have refused to provide support for this version, Avsim is the only place I can go to. Has anyone else had this problem, or is it something I've been doing wrong? Thanks for any help and much appreciated if anyone can. Take a look @ https://docs.flightsim-studio.com/e-jet-series Happy flying Cees van der Linden
December 26, 2025Dec 26 Yep, uninstalled, reinstalled, reset EFB, everything they said. Green activation box still there, no power to FMC. By the time they get this pos working in 2024, 2028 will be out and 2020 will have hit end of life. Such good modeling and texturing it’s maddening the rest is such a miss.
December 27, 2025Dec 27 Moderator I uninstalled it first then installed the experimental version into the old community folder (not the community 2024 folder). After that I also deleted the WASM folder, which was not deleted by the uninstall. I haven’t had any crashes or WASM issues so far. Maybe this will help someone else. I9-13900K, RTX 4090, DR5-6000MHZ, CORSAIR ICUE H150I ELITE, ASUS PRIME Z790-P, THERMALTAKE TOUGHPOWER GF3 1350W, WIN 11
December 27, 2025Dec 27 11 hours ago, Twenty6 said: I haven't been able to try this in the Experimental version 0.10.27, but this worked previously. From the FSS Documentation Hub: Direct route import into the MCDU is possible via 2 ways: World Map menu Export your flightplan as msfs flightplan file (.FLT) (i.e. Simbrief, SimtoolkitPro, etc.). In MSFS World Map menu import your flightplan file (LOAD/SAVE->LOAD FROM THIS PC). The route will automatically be added to the E-Jets MCDU upon flight initialization. Simbrief MCDU import Create a flightplan in Simbrief. Start your flight at the correct departure airport. It will automatically be inserted as origin in the MCDU RTE page. On RTE page enter the destination and flight ID matching with your simbrief flightplan. The flight ID in simbrief is called Flight Number and can be found in the OFP. It is not the callsign! Click on SEND (LSK L4) and wait until you see the (SENT) promt indicating your flightplan got fetched correctly. If not, the scratchpad will show you the reason. Click on DLK FPL to open the datalink flightplan list. You should now see the fetched flight plan. Click on APPLY ACTIVE to insert the flightplan route into MCDU. Remember that it will not import any departure or arrival route, only the enroute waypoints. had i had the correct link i would have seen this but these are the current instructions for the experimental ... Setup In the MCDU, go to NAV → DATALINK → ADDRESS → FLIGHTPLAN and enter your SimBrief username as COMPANY ADDRESS. It will be saved to the work folder. Import Route: Go to the RTE page on the MCDU and select SEND REQ. This will import your latest SimBrief route, excluding the SID and STAR. Performance: Go to the PERF INIT page on the MCDU and select SEND REQ. This will import the performance data from your latest SimBrief flight plan. The imported performance data is taken from your SimBrief flight plan and may not match your actual aircraft weight. Make sure to load the aircraft accordingly.
December 27, 2025Dec 27 In the Steam version the Fsse17x folder in Community is a shortcut to an Aerosoft folder in the main user directory. Deleted that and reinstalled then everything worked. The Aerosoft folder had duplicates from previous installations, even for the CRJ. So frustrating spending hrs doing detective work in this sim. Maybe this may help someone having issues.
December 31, 2025Dec 31 On 12/24/2025 at 2:29 PM, regis9 said: I was quite excited to try this but it's going back into the hangar. Loaded up the E195, was greeted with a green box right on the pilots window telling me that the aircraft was activated. Great, except I can't get rid of the box. Then I powered up the aircraft and I can't get the FMC's to power up. Uninstalled, deleted all WASM files / work folder, reinstalled. Same deal. https://imgur.com/9VXrGV9 That's enough time wasted on this, I'm going to fly the new Maddog release instead. It's quite disappointing, I've been really patient with this project but there are just too many other good aircraft out there for me to waste time and frustration on this one. Hi regis9, I contacted FSS as I was experiencing the same issue. They suggested the following steps, which worked for me after trying several other fixes: Working fix: Close the sim completely. Uninstall all E-Jets variants (including the Freighter variant, E17X and E19X). Restart the sim. Reinstall only the variants you want (E17X and/or E19X). After doing this, the activation box disappeared and everything worked normally. Hope this helps!
December 31, 2025Dec 31 Thanks, I did get them working by making sure I didn’t have any non experimental versions installed (I had forgot about the freighter). Once I dealt with that I got them up and running. Generally it was a good flight, though I did have some oddities on descent with the aircraft climbing uncommanded. Something for me to try again and work through. Dave Current System (Running at 4k): ASUS ROG STRIX X670E-F, Ryzen 7800X3D, RTX 5090, 55" Samsung Q80T, 64GB DDR5 6000 RAM, EVGA CLC 280mm AIO Cooler, Brunner CLS-E NG Yoke, Thrustmaster Warthog HOTAS & Stick, Thrustmaster TCA Quadrant & Add-on, VirtualFly Ruddo+, TQ6+ and Yoko+, GoFlight MCP-PRO and EFIS, Skalarki FCU and MCDU
January 1Jan 1 On 12/31/2025 at 2:27 PM, regis9 said: Thanks, I did get them working by making sure I didn’t have any non experimental versions installed (I had forgot about the freighter). Once I dealt with that I got them up and running. Generally it was a good flight, though I did have some oddities on descent with the aircraft climbing uncommanded. Something for me to try again and work through. Glad you got it working! I ran into the same issue. Being an experimental build, I suppose a few surprises are to be expected 🥴😅
January 12Jan 12 does anybody know why the standard version aircraft stuck and cannot move? The chocks are removed, parking breaks off... Can GSX be the reason? Intel i9-13900K, GIGABYTE GAMING Z790, GeForce RTX4090, 32GB
April 7Apr 7 Whish they fix mouse active areas in VR... Standard version is perfect, in the experimental mouse pointing zones shifted aside so it difficult using the plane... Intel i9-13900K, GIGABYTE GAMING Z790, GeForce RTX4090, 32GB
Create an account or sign in to comment