April 8Apr 8 **Version 0.10.36 (public experimental) available** ------------------------ 'Hi, The dev team and beta team have been busy over the past few weeks, and we’re excited to share the next experimental version of the E-Jets with you. New features include holdings and temperature compensation for RNAV approaches. You can find more details in our [documentation](https://docs.flightsim-studio.com/e-jet-series). The last major milestone left is the autopilot. It works in general, but it’s still not as accurate as we want and doesn’t meet our expectations yet. Right now, it’s still based on the default MSFS autopilot with a custom layer on top. In the future, this will be replaced with a fully custom autopilot. Stay tuned! Changelog: - Major MCDU & LNAV improvements - Improved takeoff & landing behaviour - Full missed approach implementation - FMS temperature compensation for RNAV approaches - MCDU Holdings with all entry types - MCDU flight complete phase allows multiple legs in one session - Tons of smaller fixes and improvements Release Status: Contrail: Released (experimental branch) Aerosoft One: Released (experimental branch) Source Edited April 8Apr 8 by MrLamb 'It is better to be silent and be thought a fool than to speak and remove all doubt.'
April 8Apr 8 Author As you're still unable to update AIRACs in the FSS E-Jets with a navdata subscription (You're FORCED to have a Navigraph unlimited sub), the naming of the release is pretty irrelevant to me 🙄 'It is better to be silent and be thought a fool than to speak and remove all doubt.'
April 8Apr 8 Banished to the hanger forever. AMD Ryzen 7800x3d 64gb DDR5, Sapphire 7900 GPU MSSI Tomahawk AM5 M/Board. 1x 4tb Crucial M.2 SSD, 3x 2tb Crucial M.2 SSD's
April 8Apr 8 Can't complain really....I've had some wonderful years out of this product in it's "unfinished state". The E190 Freighter is my daily aircraft. Would I purchase another FSS product in 2026? Absolutely not! Asus Maximus X Hero Z370/ Windows 10 MSI Gaming X 1080Ti (2100 mhz OC Watercooled) 8700k (4.7ghz OC Watercooled) 32GB DDR4 3000 Ram 500GB SAMSUNG 860 EVO SERIES SSD M.2
April 8Apr 8 I mean, it's going to be a great aircraft once it's finished. I think. For now though my biggest MSFS2024 purchasing regret.
April 8Apr 8 Author For me, the E-Jets are a constant reminder that I intend never again to buy software based on promises of future functionality, but only based on its current state. They do that reliably. Even in today's released version 🤔 'It is better to be silent and be thought a fool than to speak and remove all doubt.'
April 8Apr 8 Author Just noticed that FSS' CEO set a (new) release date for V1.0 on discord: Source Now...that's what I call...optimistic? Edited April 8Apr 8 by MrLamb 'It is better to be silent and be thought a fool than to speak and remove all doubt.'
April 8Apr 8 Either I'm doing something wrong or these E jets still not climbing or holding speed as should. Very disipointed. Bill McIntyre Asus StrixB650E-F Gamer, AMD Ryzen 9 7900X3D, Corsair Titanium DDR5 64GB, Samsung 990 PRO-4TB M.2, (4) 2TB SSD's, Corsair H1150i liquid cooler, RTX 2080TI Founders Edition, (2) LG 34" HD Curved Monitor, Sound Blaster Audigy X, 1Kw PC Power & Cooling Power Supply, Corsair Obsidian Full tower Case. MSFS 2024, WIN11 Pro x64
April 9Apr 9 can anybody tell if they fixed mouse point areas in VR with the new experimental update? Intel i9-13900K, GIGABYTE GAMING Z790, GeForce RTX4090, 32GB
April 9Apr 9 7 hours ago, zorro747 said: can anybody tell if they fixed mouse point areas in VR with the new experimental update? No - I'm afraid not fixed. It is still very time consuming trying to make any entries to, say, the MDCU with the mouse cursor in VR. Aircraft buttons and knobs are broadly OK, but the VR cursor on a cockpit keypad or similar is way out in either eye. The error isn't consistent either. Some letters you have to point the cursor hand around 3/4 toward the letter above and to the left or right...and then other letters or numbers are different. I have to clear and try again around 40% of every letter or number tried and so - immersion killing or not - I do as much of the MCDU programming in 2D. It breaks your immersion - but not as much as trying the same thing in VR breaks your spirit! Ryzen 7 9800x3D @5.2GHz; ASUS X670-P Motherboard; nVidia 4080 (factory o/c); 32G 5600MHz DDR5 SDRAM; Pimax Crystal Light VR Headset; Quest 3 VR Headset
April 9Apr 9 The other thing not fixed - certainly for me - is that the flight panel button on/off lights (eg NAV/AP/HDG/ALT etc etc) don't light up. I had already raised this as an issue in the pre-Experimental version. Clearly it's not on their priority list and they have made it clear that no issues can be raised with the Experimental. But on the better, hopeful, please,please,please let this be a good sign, is that the VNAV system appears to be much improved...and I have a surprising example to back this up: SCENARIO - I booted up the E-175 from Cold & Dark - I entered the Simbrief Flight plan from EBOS Ostende to EGKK London Gatwick - I took off and, during initial climb engaged the Autopilot and VNAV - then the downstairs doorbell rang and the interruption lasted 2hours!! EXPECTATION My expectation, when I eventually got back to the PC, was that the aircraft would have crashed. That expectation was fully met. Crashed in a field. SURPRISE - The surprise was when I used the external view Yes - that pair of runways just the other side of the bushes is indeed London Gatwick. And yes - this was the planned direction. I have no doubt that if I'd been around to drop the undercarriage and click the APP button it would have also landed on the runway...other than that, the whole flight totally hands-off!!! So yes - this years and years of early release stuff is HUGELY frustrating. But they do make pretty decent aircraft! Edited April 9Apr 9 by AJZip2 Ryzen 7 9800x3D @5.2GHz; ASUS X670-P Motherboard; nVidia 4080 (factory o/c); 32G 5600MHz DDR5 SDRAM; Pimax Crystal Light VR Headset; Quest 3 VR Headset
April 9Apr 9 19 hours ago, Bigmack said: Either I'm doing something wrong or these E jets still not climbing or holding speed as should. Very disipointed. what are you doing? for me it climbs as should.
April 9Apr 9 1 hour ago, AJZip2 said: The other thing not fixed - certainly for me - is that the flight panel button on/off lights (eg NAV/AP/HDG/ALT etc etc) don't light up. I had already raised this as an issue in the pre-Experimental version. Clearly it's not on their priority list and they have made it clear that no issues can be raised with the Experimental. But on the better, hopeful, please,please,please let this be a good sign, is that the VNAV system appears to be much improved...and I have a surprising example to back this up: SCENARIO - I booted up the E-175 from Cold & Dark - I entered the Simbrief Flight plan from EBOS Ostende to EGKK London Gatwick - I took off and, during initial climb engaged the Autopilot and VNAV - then the downstairs doorbell rang and the interruption lasted 2hours!! EXPECTATION My expectation, when I eventually got back to the PC, was that the aircraft would have crashed. That expectation was fully met. Crashed in a field. SURPRISE - The surprise was when I used the external view Yes - that pair of runways just the other side of the bushes is indeed London Gatwick. And yes - this was the planned direction. I have no doubt that if I'd been around to drop the undercarriage and click the APP button it would have also landed on the runway...other than that, the whole flight totally hands-off!!! So yes - this years and years of early release stuff is HUGELY frustrating. But they do make pretty decent aircraft! That the buttons don't light up is correct and realistic - most operators have disabled this (to force the pilots to look at the PFD to see which modes are actually active). Yet you can re-enable the lights in the EFB settings For transparency: I'm a community mentor at the BATC discord. However, I do not get paid for it in any way.
April 9Apr 9 19 hours ago, Bigmack said: Either I'm doing something wrong or these E jets still not climbing or holding speed as should. Very disipointed. If they don't climb you are definitely doing something wrong. As for "holding speed", that depends on whether you mean the speed target (this seems mostly correct) or the actual reached speed (this still fluctuates quite a bit) For transparency: I'm a community mentor at the BATC discord. However, I do not get paid for it in any way.
Create an account or sign in to comment