Aerosoft official retail partner for Microsoft Flight Simulator !! 
Click here for more information

Jump to content

lambourne

Members
  • Content Count

    9
  • Joined

  • Last visited

Community Reputation

2 Neutral

About lambourne

  • Rank
    Flight Student - Groundwork
  1. lambourne

    Windshear

    P3D v4.5HF3, A32x professional, latest non-experimental version. Vol 4 - Systems of the Aerosoft documentation says on page 04-03-15: The FACs will try to detect windshear and will warn the pilot of this dangerous condition. Windshear detection is only active below 1300 feet AGL in configuration 1 or greater. When detected the flight director will show an optimal pitch attitude and the aural warning “WINDSHEAR” will be heard. Is this modelled? I don't think I've ever had a windshear callout from the bus.
  2. I remember in one of the early printer screenshots on here the landing printout showed the G force at touchdown rather than descent rate. Is it possible to switch it to G at touchdown, being a more realistic representation of whether you slammed it on like a ton of bricks or not?
  3. Does this mean that future updates of the A32X will support published database holding patterns rather than the 180 degrees reversal from last leg at present?
  4. It's nice to see others at least get the new livery manager to open. I just installed v1.3.1.0 and it doesn't even get that far. Installation process: I have the A318-319 and A320-321 as separate products. I uninstalled the A320-321 using the Windows Add/Remove Programs function. After doing that I then installed v1.3.1.0 and rebooted when the installer prompted me to do so. On clicking the Aerosoft Livery entry in the Start Menu I get the attached error message. Full error log from the error message follows: See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.NullReferenceException: Object reference not set to an instance of an object. at Livery_Installer.MainWindow.cbxSim_SelectedIndexChanged(Object sender, EventArgs e) at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e) at System.Windows.Forms.ComboBox.set_SelectedIndex(Int32 value) at Livery_Installer.MainWindow.MainWindow_Load(Object sender, EventArgs e) at System.Windows.Forms.Form.OnLoad(EventArgs e) at System.Windows.Forms.Form.OnCreateControl() at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible) at System.Windows.Forms.Control.CreateControl() at System.Windows.Forms.Control.WmShowWindow(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ScrollableControl.WndProc(Message& m) at System.Windows.Forms.Form.WmShowWindow(Message& m) at System.Windows.Forms.Form.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.8.4121.0 built by: NET48REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll ---------------------------------------- Livery Installer Assembly Version: 2.1.0.0 Win32 Version: 2.1.0.0 CodeBase: file:///C:/Users/($myusername-edited)/Documents/Aerosoft/LiveryInstaller/Livery%20Installer.exe ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.8.4121.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.8.4001.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.8.3752.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.8.3752.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.8.4121.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll ---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.8.3752.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.
  5. Your navdata seems to be out of date, the TIMBA 4B STAR was renamed KUNAV 1G in October 2019. Which transition ('via' in the FMGC) did you select? It looks like you didn't select one at all because from the intercept angle it seems as if you're trying to fly from TIMBA waypoint (down to the south east from EGKK) direct to the IAF. The transition takes you around from the last STAR waypoint to line up with the runway fixes in the FMGC.
  6. I have this problem with the previous version of the A318 and A319 (v 1.4.2.1). The workaround I found is to manually reinsert the pax and cargo load figures into MCDU3 after initialising the loadsheet. MCDU3 works perfectly after that. For some reason it never affects the fuel load. Originally installed the 64-bit 318 and 318 on Windows 10 18xx build when v1.4.2.1 was released to the stable channel, then updated Windows in line with the usual Microsoft schedule to 1903.
  7. Is it possible to save in mid flight and load the scenario with the same panel state and MCDU settings? I am running P3D v4.3 with the A318/319 v1.2.3.1. No environmental addons other than FSXWX 161. I have UK2000's Heathrow and Gatwick airports installed. I have tried this with a savegame starting about 15nm E of EGKK at around 3,500ft. Using the default P3D savegame option ( the ; key), when I load the saved scenario the sim shows an error saying "there was a problem deserializing the panel state". If I load the saved scenario after another flight, the left MCDU goes blank (so no init/perf/flight plan data and no waypoints on the nav display) and the autothrottle stops working. The scenario will only load with the A319 in a flyable condition if I have previously exited and restarted P3D. Obviously this is no good if I want to practice approaches, I may as well fly circuits for the amount of time it takes to restart the sim! Help gratefully received.
  8. I apologise if this is off topic but is there a way to display the G value in the printout?
×
×
  • Create New...