ProSim737 version 2.30 & ProSim 3.00 Announcement

sedatsoft

Jul 16 2020 Release Version 2.30
======================================
- Fixed lights not working with ProSim P3D Module V1
- [SW-96] Added new ISFD_RMI module
- [SW-97] Added ATC and ALT switch mappings
- [SW-98][FMS][PERF INIT] OAT and CRUISE WIND will affect TRIP and OPT ALT calculations
- [Autopilot] Improved ILS interception
- Fixed database import issues
- [CPFlightV2] Added timers to master warning recall and GPWS SYS TEST switches due to hardware limitation
- Updated DEM url

Hello All,

Beginning next week, we will release the first public beta of our long awaited FMS update. But due to the amount and type of changes (this is actually a major overhaul), that include executables renaming and removal of applications, we decided to release the new update as a Version 3.0.

What's new about V3.0:
- ProSimMCP and ProSimPanel were removed. MCP is embedded into the system and panels are available via ProSimDisplay with full functionality, if provided by the system side.
- ProSimDisplay is now D2D only
- New file naming
- New flight model with enhanced visual features (with more updates expected soon)
- New ProSim Module for P3D
- New maint options in the CDU, like door control and W&B page with weight and CG info
- New FMS code
- New VNAV/LNAV underlaying engine
- Offset functionality
- New ILS autopilot mode
- New GA autopilot mode
- New LNAV/VNAV autopilot modes
- Improved route tracking
- Decel markers on ND

And much more...

Licensing will be the same, you just need to have an active update subscription to upgrade to V3. Upgrade will not be direct from the update manager as a lot changed regarding applications and file names.
In fact V2 and V3 will not be mixed in the update manager.

About drivers, everything will be the same, except for CPFlight where the MCP driver was removed. All connections are now done via the new CPFlight V2 driver.
MCP driver will still be available from the MCP config section.

Migrating configuration should be as simple as copying your config file from V2. Note that MCP specific configuration needs to be done now again in the System Side as it will not be migrated.