Jump to content

CRJ Update 1.0.5 incoming


Recommended Posts

  • Developer

Hello everyone!

 

First, I'd like to apologize that it took so long. The simple reason is that we wanted to get it right this time!

 

After the last beta was already OK'ed by them, I uploaded version 1.0.5 to the beta testers today. As long as I didn't mess up anything with this version (cross your fingers!), it will be sent to Aerosoft for installer building tomorrow. Depending on the schedule of the Aerosoft guys it should be available for public download on Thursday or Friday.

 

Here's the readme so you can see what was fixed, changed or added:

 

Aerosoft CRJ 700/900 Update 1.0.5
=================================

*******************************************************************************************
*******************************************************************************************
*** The 64-bit version of this update requires Lockheed Martin Prepar3D v4.2 or higher! ***
*******************************************************************************************
*******************************************************************************************

Change Log
==========

1.0.5 Release
- [Fixed] Several pushbuttons have been fixed to work with the left mouse button as well
- [Fixed] External APU sound not looping properly
- [Fixed] Crackling sound issue with APU on
- [Fixed] Door positions corrected (special thanks to Eduard and Richcam for their input!) for better jetway docking
- [Fixed] Time and fuel calculations sometimes gave invalid results on the ground with an incomplete flightplan
- [Fixed] Wrong turns on (VECT) legs
- [Fixed] Removed distance and time-to-go indications for (VECT) legs on MFD
- [Fixed] Changed minimum airport distance and configuration conditions for FA landing announcements
- [Fixed] Reverser spool-up works again
- [Fixed] PFD "SYNC" message now properly disappears a few seconds after synchronizing flight director
- [Fixed] Departure runway selection disappearing after SID selection (if SID's runway is set to "ALL")
- [Fixed] ILS frequency on ARR DATA page can now be copied to scratchpad for use on RADIO page
- [Fixed] Decreased overshoot on track capture (introduced with rev 311)
- [Fixed] Sign error on wind correction during initial waypoint turn
- [Fixed] Only first letter of current and next waypoint shown on PROG page
- [Fixed] Ice detection after changing payload in DAVE now only when engines are running
- [Fixed] Single cue FD now points into the right direction
- [Fixed] Range-to-altitude ring now uses vertical speed trend instead of current vertical speed for more consistent indication
- [Fixed] Increased cabin rate change for altitudes above 20000ft
- [Fixed] Selection of Runway-SID-Transition as SID
- [Fixed] Increased the size of text buffers for PROG page
- [Changed] Changed "(P-TURN)" into "(P-T)" for PROG page
- [Fixed] HUD FPV and FD cue visibility
- [Fixed] Bleed Air source now switched to BOTH after takeoff when both throttles are pulled out of the TOGA detent
- [Fixed] Corrected begin of turn point for turns with more than 60 degrees (official FAA formula results in early turn)
- [Fixed] PFD/MFD CDI inverted with FMS as nav source
- [Fixed] CDI calculation (= cross track error) would result in off-track indication even though the aircraft is "on the line"
- [Fixed] Rounding error on MFD Data page ETE calculation
- [Fixed] CTD when selecting an arrival runway for the second time while flightplan is still empty
- [Fixed] SID data is now loaded when the selected departure procedure is a Runway-SID transition instead of a SID (U.S. style SIDs)
- [Fixed] Improved holding tracking
- [Fixed] Saving a flightplan no longer tries to save holdings
- [Fixed] Editing holdings now switches to MOD FPLN and requires EXEC to become active
- [Fixed] Bleed air auto mode logic (Thanks to Ak47e6 for the excellent description!)
- [Fixed] CTD when entering user-defined waypoint (certain circumstances only)
- [Fixed] Maximum wind speed on PERF INIT page increased from 99 to 999 knots
- [Fixed] Stopped VNAV calculation cycle from overwriting manually entered winds on LEGS WIND pages
- [Fixed] Vertical eyepoint position corrected for HGS alignment (-700 and -900)
- [Fixed] HGS glideslope symbol is no longer cut off on right side
- [Fixed] Removed HGS clickspot from the windscreen
- [Fixed] Clocks now show the proper format for CHR (":MM") and ET ("HH:MM")
- [Fixed] Thrust reversers now close when throttle is advanced while reversers are open
- [Fixed] APU START/STOP button animation and clickspot logic
- [Fixed] DIR/INTC page waypoint selection logic
- [Fixed] DIR/INTC on-fpln waypoint directs
- [Added] Automatic pressurization implemented
- [Added] EMER DEPRESS EICAS message
- [Fixed] Waypoint sequencing logic
- [Fixed] Waypoint turn calculation
- [Fixed] Service door now works again (also animation stuttering fixed)
- [Fixed] Power settings in detents now fit the calculated settings again
- [Fixed] Doors control in FSX
- [Changed] CRJ Manager: seat editor changed to "passenger" or "no passenger" selection (instead of male, female, child)
- [Added] CRJ Manager: Automatic synchronization between CRJ Manager and DAVE
- [Fixed] CRJ Manager: Missing payload update for FSX
- [Fixed] CRJ Manager: CoG and trim calculation
- [Fixed] DAVE: CoG and trim calculation
- [Fixed] Cabin announcements no longer audible when deselected in CRJ Manager
- [Fixed] Flight attendant talking on flightdeck no longer audible when deselected in CRJ Manager
- [Fixed] Reverser animation length adjusted
- [Fixed] Bug in abeam check function that would cause early waypoint sequencing

Link to comment
Share on other sites

  • Deputy Sheriffs
21 minutes ago, Cheyenne Chief Pilot said:

Huge effort, but ... why has version 1.04. been skipped?!? (Current version is v1.0.3.)

 

Version 1.0.4 had some malware in it and after that other company had some bad press about it we thought it wiser not the release it. ;)

 

Link to comment
Share on other sites

  • Deputy Sheriffs
6 minutes ago, Wise87 said:

Will this work on P3Dv4 4.1? I guess we have no choice. Many of use are in no rush to move to 4.2.

 

42 minutes ago, Hans Hartmann said:

*** The 64-bit version of this update requires Lockheed Martin Prepar3D v4.2 or higher! ***

 

Link to comment
Share on other sites

  • Deputy Sheriffs
27 minutes ago, Wise87 said:

I did read the above. Maybe I should have been more specific with my question but thanks anyways.

 

The answer is no, and that's exactly what Hans wrote already in his initial post.

Link to comment
Share on other sites

  • Developer
vor 3 Stunden , Cheyenne Chief Pilot sagte:

Da pesky Aerosoft launcher reared its ugly head again?   :lol::ph34r::P

No. I thought about going with the trend in flight simulation and add some really nasty malware on all your computers, but I wouldn't go so far to install a program written in Java :D

 

(Hint @everyone about to start a shitstorm: this is sarcasm!)

Link to comment
Share on other sites

I've been on the sidelines observing this product, but I think I'm ready to dive in and buy it in a few days.  My thanks to all the beta testers and early adopters for working out the bugs.

Link to comment
Share on other sites

On 27/2/2018 at 3:53 PM, Frank Docter said:

 

Version 1.0.4 had some malware in it and after that other company had some bad press about it we thought it wiser not the release it. ;)

 

Why?  bad press is because all the huge mass of pirates get´s angry. I as a user and as a worker of cinema industry see very very well the malware on the software installer.  people need to learn by hook or by crook that piracy and pirates heart a lot the entertainment industry, not heart, they kill it. for their fault, I can´t work in the music industry because in Spain is death due the piracy. If the justice institutions of the European Union do little to solve the issue, maybe it's time for companies to take justice into their own hands.  

that's why i see with a very goods eyes some malware like that.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use