May 29, 20251 yr 6 hours ago, JRBarrett said: The official release numbering will be “2.1” not “3”. It includes all the improvements of V 2.0 released earlier this year plus a brand new flight model making use of CFD. Like 2.0, 2.1 will be a free update for all those that own the original CRJ I don’t fly the CRJ but do work on them as a mechanic and am a technical consultant, but the 3 r/w CRJ pilots on the test team report that the flight performance is now extremely close to the real aircraft in all flight regimes. One of the test pilots, “YourSimCFI” has been working extensively with the FDE developer to test and refine its performance. It works very well in MSFS 2024, but it is not yet an “official” 2024 release with 2024-specific features like working windshield wipers - that will come later and (I assume) will be numbered 3.0. Hans and the test team have been working very hard on this since last autumn when 2.0 development started. We have been through 79 beta test builds. The last two were just to nail down correct autopilot disconnect logic. (When disconnecting via the yoke disconnect button, the alert tone sounds continuously until silenced with a second press. If disconnecting by pressing the bar on the AP control panel or by accidentally actuating stabilizer trim, the alert sounds only three times). It’s a small thing that only a r/w CRJ pilot would even notice, but we are really striving for as much r/w accuracy as possible. With the new FDE, hand flying and takeoff and landing performance is superb. I saw on the video by YourSimCFI that with the new FDE update it now has the proper AOA when in approach, did Hans do anything about the HGS layout? On V1 and V2 when on Final approach the HGS is basically unusable since all of the cues go off the bottom of the HGS and are not able to be seen, unfortunately in the video he was in the right seat and not the left with the HGS down. The last post here by "amahran" shows exactly what I am talking about https://forum.aerosoft.com/index.php?/topic/172143-hud-placement/#comment-1087084 Thanks, Edited May 29, 20251 yr by jjeffreys ________________________________________________________________________________ Jeremy 9800X3D OC'd -30 +200MHZ | 64GB CL30 RAM | RTX 5080 | Windows 11 23H2| Bravo Throttle | Alpha Yoke | CH Pedals | Logitech Radio Panel | SmoothTrack | AAO
May 29, 20251 yr 3 hours ago, JRBarrett said: Yes DIR INTC has been improved also. when can we expect it roughly? Ron Hamilton "95% is half the truth, but most of it is lies, but if you read half of what is written, you'll be okay." __ Honey Boo Boo's Mom
May 30, 20251 yr 1 hour ago, fakeflyer737 said: when can we expect it roughly? I’m not sure. I think Hans is sending an update to Microsoft perhaps this week. If so, I would expect a general release shortly afterwards, but that is NOT official. Jim BarrettLicensed Airframe & Powerplant Mechanic, Avionics, Electrical & Air Data Systems Specialist. Qualified on: Falcon 900, CRJ-200, Dornier 328-100, Hawker 850XP and 1000, Lear 35, 45, 55 and 60, Gulfstream IV and 550, Embraer 135, Beech Premiere and 400A, MD-80.
May 30, 20251 yr 4 hours ago, jjeffreys said: I saw on the video by YourSimCFI that with the new FDE update it now has the proper AOA when in approach, did Hans do anything about the HGS layout? On V1 and V2 when on Final approach the HGS is basically unusable since all of the cues go off the bottom of the HGS and are not able to be seen, unfortunately in the video he was in the right seat and not the left with the HGS down. The last post here by "amahran" shows exactly what I am talking about https://forum.aerosoft.com/index.php?/topic/172143-hud-placement/#comment-1087084 Thanks, I don’t think anything was done with the HGS, but I have never used it so I can’t say if any changes were made. I can check tomorrow. Jim BarrettLicensed Airframe & Powerplant Mechanic, Avionics, Electrical & Air Data Systems Specialist. Qualified on: Falcon 900, CRJ-200, Dornier 328-100, Hawker 850XP and 1000, Lear 35, 45, 55 and 60, Gulfstream IV and 550, Embraer 135, Beech Premiere and 400A, MD-80.
May 30, 20251 yr 23 hours ago, vonmar said: I just did a quick test. I do not use GSX. Did screenshots if needed. RWY Engines running Taxi to parking APU ON during taxi APU Gens AUTO Park brake Engines shut down Auto xfer to APU powering CRJ EFB Chocks set EFB Doors / cargo Open EFB External power Avail APU OFF Ext power Auto xfer powering CRJ All ok Thanks for that! This might solve my issue, Maybe I am missing the "Auto xfer to APU powering CRJ" step. What does this entail? Do I have to press the Green "AVAIL" light to bring the EFB to life so I can Set the Chocks, start the GPU, Open Doors/Cargo etc.? OK, I believe I should be doing the following: 1. APU PWR FUEL button push once, the APU then performs a self test. 2. Push the APU START/STOP button Edited May 30, 20251 yr by TomCYYZ i913900KF (5.8GHz) | Case: Fractal PopAir RGB I Gigabyte Z790 UD AX| MSI Gaming RTX 4070Ti Super 16GB | Kingston Fury Beast 64GB DDR5 5200Mhz | SOLIDIGM P41 Plus 2TB NVMe M.2 SSD | Samsung SSD 870 EVO 2TB | Thermalright Frozen Notte 240 MM Liquid Cooling | LG EVO 42" Monitor 3840 x 2160 120Hz | Honeycomb Alpha & Bravo | Logitech G Pro pedals | Tobii EyeTracker | 850W Thermaltake 80+ GOLD |
May 30, 20251 yr 19 hours ago, vonmar said: Just checking. Have other pilots reported this with CRJ v2? Which ILS approach had the problem? Notes: I have not purchased MSFS2024. I do have CRJ v2 in MSFS2020. I use Navigraph Navdata Yes, I've seen two other reports of that. It was one of the ILS approaches to ENGM (by Aerosoft...), the actual sim-navdata of the localizer is okay, have flown there often enough with other aircraft. Also using Navigraph by the way. The CRJ v1 on MSFS 2020 never did that on a localizer, by the way. It had its own problems, but this was none of them. For transparency: I'm a community mentor at the BATC discord. However, I do not get paid for it in any way.
May 30, 20251 yr 18 hours ago, Ron Lefebvre said: I have over 30 flights and not one problem on any of my flights. (OMG, I sound like Bob). Localizer should not be turned on before 15 miles and make sure you are on a VOR setting and not gps. It was 8 miles out and it did capture the localizer actually (showing LOC green), it just did not fly it but instead flew a course 80 degrees to the right. Edited May 30, 20251 yr by Fiorentoni For transparency: I'm a community mentor at the BATC discord. However, I do not get paid for it in any way.
May 30, 20251 yr 16 hours ago, sd_flyer said: Gotta give it a shot again. Last time I was flying a long haul and CRJ started stuttering badly. Pretty much no other add on I have has this issue. I suspect it may be related to EFB map though Ah yes, so we are two then. Was it also kind of micro freezing during the whole flight for you? I've never seen that before with any other add on. I did not use the EFB map by the way For transparency: I'm a community mentor at the BATC discord. However, I do not get paid for it in any way.
May 30, 20251 yr 3 hours ago, Fiorentoni said: Ah yes, so we are two then. Was it also kind of micro freezing during the whole flight for you? I've never seen that before with any other add on. I did not use the EFB map by the way Yes exactly like that! I had few shorter flights that went uneventfully. Then, a long haul and it started stutter in midflight. If I go outside view. stutter stop! When I come back into the cockpit stutter continue.. Basically I terminated flight because I couldn't continue like that any longer Life time flight sim enthusiast, current airplane owner 172P (past C182F). FAA CP/IR ASEL/AMEL, FI ASELMy System: AMD Ryzen 9 9950X3D , MSI X870 GAMING PLUS, 64G RAM, ASUS RTX5090, 4T SSDPut my hands on (pic/dual/given)7GCAA, 8KCAB, BE24, BE76, BE35-C33, BE35, C150, C152, C172B/N/P/R/SP, 182F, M20E,M20C, M20J, AT6(SNJ4), PA28-140,PA28-151, PA28-161,PA28-181,PA28RT-201,PA28R-180/201T, PA24-250, PA32-300R, PA44, AC114, YAK-18T, YAK-52, SR22
May 30, 20251 yr That is interesting. All my flights are under 2 hours, so I have no reference for that. Ron MSFS 2024 -Too many airplanes to name. Too many airports to name.
May 30, 20251 yr 14 hours ago, JRBarrett said: I don’t think anything was done with the HGS, but I have never used it so I can’t say if any changes were made. I can check tomorrow. Side question: I notice the TO elevator trim causes the plane to rotate on its own as it were at the anticipated speed and I don't recall that w/ V1. Is that the way the plane is designed to work in the RW, or is that a bug? I don't think I'm doing anything wrong... Noel System: 9900X3D Noctua NH-D15 G2, MSI Pro 650-P WiFi, G.SKILL 64GB (2 x 32GB) 288-Pin PC RAM DDR5 6000, WD NVMe 2Tb x 1, Sabrent NVMe 2Tb x 1, RTX 4090 FE, Corsair RM1000W PSU, Win11 Home, LG Ultra Curved Gsync Ultimate 3440x1440, Phanteks Enthoo Pro Case, TCA Boeing Edition Yoke & TQ, Cessna Trim Wheel, RTSS Framerate Limiter w/ Front Edge Sync. Aircraft used in MSFS 2024: Fenix A320, Aerosoft CRJ, FBW, WT 787X, I-Fly 737 MAX 8, Citation Longitude.
June 30, 2025Jun 30 2.1 is now out Quote V2.1.10 - Updated Flight Model (all variants) - Updated Engine Model (all variants) - Improved several items in cockpit model (air outlets, seat position indicators, gear lever) - Fixed faulty gallons to pounds conversion function - Fixed LEGS page based directs turning point calculation - Removed .air files from project (after making sure they are not needed anymore) - Added elevator trim input to autopilot disconnect logic - Fixed missing waypoint symbols and labels on enroute direct legs - Flight and engine model updates - Fixed AP disengagement logic in FS2024 - Minor MCDU camera angle fix (CRJ-700) - Removed .air files from project - Fixed AP coupling indicator showing red when AP is OFF - Fixed simvars used for control input detection - Fixed FD modes resetting on disconnecting AP - Fixed crosstrack error calculation for DIRECT legs - Changed control input force detection from "LOW (75%) - MED (50%) - HIGH (33%)" to "OFF - LOW (66%) - HIGH (33%)" - Fixed ETA calculation on PERF INIT page 3/3 - Added support for DME Arc and RF legs that end with an overfly waypoint - Fixed TOD calculation when crz alt is below an altitude constraint - Fixed ATD custom waypoints - Limited direct T-P distance to maximum 10 NM - Fixed missing chime on pressing PA button - Reworked autopilot disconnect and engage logic - Changed GPWS mode 1 (sink rate) to be a bit less sensitive - Fixed VFTO calculation for landing - Takeoff and landing speeds no longer change during flight - Changed GLD deploy condition to 3 seconds below 10ft RA, but after first weight-on-wheels - Fixed GLD retract conditions (less than 45 kts and 40 seconds weight-on-wheels) - Fixed CALL button not playing chime sound - Fixed a problem with (INTC) leg immediately after takeoff - Fixed MFD VNAV window showing negative time and fuel while calculation is still invalid - Fixed waypoint symbol drawn after direct - Moved direct T-P a bit further away from the aircraft (less overshoot) - Fixed short DME arc tracking (less then 10°) - Fixed ETA calculation on MFD FPLN/PERF INIT 3 pages - Added alternate flight plan to Simbrief import - Fixed remaining distance calculation for RF legs (two consecutive RF sequencing bug) - Fixed GS indicator size - Fixed waypoint name check for ATD custom waypoints - Removed ATC2 transponder entry on MCDU RADIO page - Fixed DIR/INTC altitude entry and ALT SEL display - Fixed FIX INFO page page count logic - Fixed GLD spoilers deployment logic - Fixed distance and time to destination airport not showing in MFD if no arrival is selected - Increased distance for holding fix detection - Added GSX.cfg presets with disabled "pushbackRaise" option to the Data folder - Fixed coarse altitude selection marker artifacts - Removed wind influence on range to alt arc - Removed second transponder - Changed pedestal DSPL knob to act as master brightness knob for RTUs and MCDUs - Updated cameras for VR compatibility and smoother transitions - Updated flight dynamics and engines (all models) - Added GSX GPU support (note: due to behavior of FSDT_GSX_GPU_STATE localvar, this can not be perfectly timed) - Fixed missing aircraft outline on EICAS DOORS page - Fixed FLX N1 calculation - Fixed hholding draw function - Fixed lnav for forced turns greater than 180 degrees - Added new flex temp tables and interpolation function for all variants - Fixed an issue where the flex N1 would be recalculated with current altitude (rising FLX N1) - Fixed missing wind entries in takeoff data block - Fixed flaps not in TO config at 8 degrees - Fixed GWT not updating on PERF INIT page after FMS fuel is initialized - Fixed weather radar not changing brightness when display brightness is changed - Fixed weather radar not turning with heading changes - Fixed flaps travel times depending on framerate - Fixed aileron support spoiler extension too early - Fixed early wheel chock removal on pushback - Fixed wrong TCAS target range in MFD traffic mode Edited June 30, 2025Jun 30 by Zangoose Vote to fix transparent sun visors having no effect on the sun glare effect in MSFS at: https://forums.flightsimulator.com/t/sun-shades-sun-visors-not-influencing-light-in-cockpit/691565/
June 30, 2025Jun 30 hopefully 2.1 posts on orbx soon... 5800X3D, 4090FE, 64GB DDR4 3600C16, Gigabyte X570S MB, EVO 970 M.2's, Alienware 3821DW and 2 22" monitors, Corsair RM1000x PSU, 360MM MSI MEG, MFG Crosswind, T16000M Stick, Boeing TCA Yoke/Throttle, Skalarki MCDU and FCU, Logitech Radio Panel/Switch Panel, Spad.Next
Create an account or sign in to comment