August 6, 201510 yr Looking at the list of 10.40b7 changes, I see this: X-Plane no longer uses port 49002Wondering if this might have anything to do with the FMS problem??? Someone out there knows the answer. John John Wingold
August 6, 201510 yr Looking at the list of 10.40b7 changes, I see this: X-Plane no longer uses port 49002Wondering if this might have anything to do with the FMS problem??? Someone out there knows the answer. John No, they closed this port to fix some issues actually. FMC problem (fixed for upcoming b8) The XPLMSetFMSEntryLatLon() function is broken in beta 7. This causes the FMS of all FF757, FF777 and JRollon CRJ to not work, likely also the CIVA addon installed in some 737s and 727s from FlyJSim. It’s fixed for Beta 8. Manuel Merelles
August 6, 201510 yr its also Jar design Airbus 320 & 330 that FMS isn't working. So that means we have to wait until beta 8 is out to work property all these great aircraft's....Still don't understand why FlightFactor 350xwb works perfectly with out any issue... Intel Core i9-13900K | ASUS ROG STRIX GeForce RTX 4090 GAMING OC 24GB | ASUS ROG MAXIMUS Z790 HERO | DDR5 64GB 6000-30 Trident Z5 RGB | Corsair ICUE H170i Elite Capellix RGB | Corsair 7000D Airflow ASUS ROG Thor Platinum II 1200 Watt | Samsung SSD 990 Pro NVMe M.2 2TB & 1TB | Alienware AW3423DW | Asus ROG Swift PG279Q 27" Gaming Monitor | VKB-Sim Gladiator Mk.II | Thrustmaster TCA Quadrant Airbus Edition
August 6, 201510 yr its also Jar design Airbus 320 & 330 that FMS isn't working. So that means we have to wait until beta 8 is out to work property all these great aircraft's....Still don't understand why FlightFactor 350xwb works perfectly with out any issue... I don't have the A350 but I believe the current version has an MCDU / FMS with very limited functionality, thus perhaps the reason why? The aircraft that have custom FMCs seem to be the ones affected.
August 6, 201510 yr I don't have the A350 but I believe the current version has an MCDU / FMS with very limited functionality, thus perhaps the reason why? The aircraft that have custom FMCs seem to be the ones affected. yes , exactly this. A350 has still limited functionality with Sid/Stars. Intel Core i9-13900K | ASUS ROG STRIX GeForce RTX 4090 GAMING OC 24GB | ASUS ROG MAXIMUS Z790 HERO | DDR5 64GB 6000-30 Trident Z5 RGB | Corsair ICUE H170i Elite Capellix RGB | Corsair 7000D Airflow ASUS ROG Thor Platinum II 1200 Watt | Samsung SSD 990 Pro NVMe M.2 2TB & 1TB | Alienware AW3423DW | Asus ROG Swift PG279Q 27" Gaming Monitor | VKB-Sim Gladiator Mk.II | Thrustmaster TCA Quadrant Airbus Edition
August 6, 201510 yr Beta 7 breaks the XPLMSetFMSEntryLatLon function. All of CRJ, 777, 757 are effected by this problem, and very likely other airplanes with plugins. Probably every single flight planner, GPS or external navigator plugin in the world is affected, too. The problem is the dataref sim/cockpit/radios/nav_type not reflecting changes to GPS/FMS destinations. Autopilots being unable to follow a GPS/FMS route is a side effect of that. We have identified the cause of the problem and coded a fix, which will be in Beta 8.
Create an account or sign in to comment