Oct 20, 2018

A380 Virtual Cockpit


Edited: Oct 20, 2018



Recently, I was able to integrate a nice payware virtual cockpit from the Blackbox A340-600 into the freeware Project Airbus A380.


Overall, the integration was a success. It's really amazing to finally have a high resolution fully working VC and working MCDU when flying this aircraft. However, there are still some small issues I'm working on, such as the cargo doors not opening, incorrect performance and flight tuning, incorrect fuel consumption, and incorrect lighting effects.


I'll continue to work on it and perform test flights. I'm confident I can have most of these issues resolved this weekend.


When this project is done, I will post the steps required. Note that it will require the user to purchase the Black Box Simulations A340 in order for the integration to work. Also note that this will just be for personal use. I will not be uploading any files to help in any way. You will need to follow the steps yourself.

Oct 27, 2018

This is an update on the Project Airbus A380/Blackbox Simulations A340 cockpit integration.


Issues I've found...


1.) The tiller is hardcoded to the Toggle Tailhook key. Therefore, it overrides the ability to open the cargo doors on the Project Airbus A380 external model.




The cargo doors will not be functional until there is an update to the Blackbox Simulations A340 that allows the user to change the keybindings for the tiller.


2.) Taxi light switch in the overhead panel does nothing.




Assign a hotkey for the Toggle Taxi Lights command using FSUIPC.


3.) Landing lights cause the cockpit to illuminate at night.




This is an issue when using many FSX aircraft in P3Dv4. It has something to do with how the dynamic lighting is allowed to pass through the PA 380's external model.


One solution is to disable dynamic lighting.


Another solution is to only use the taxi lights, since they are less aggressive and illuminate the area in front of the aircraft. They are also visible on the wings as well as the front landing gear.


The last solution would be for Project Airbus to update it's A380 external to block the dynamic lighting from passing through it.


NOTE- Use the hotkey ctrl+shift+L to tell the FSAirlines client that your landing lights are on or off, so that you do not get penalized.


4.) Blackbox Simulations manager doesn't work with this aircraft.




Of course it doesn't and there are no plans to try and make it work. You will need to use the default Fuel and Payload manager instead.


5.) Poor Climb Performance




Already solved. I've already figured it out and have since adjusted the flight tuning.


6.) Fuel burn




I'm still working this one out, but I may have it done by this weekend. I'm performing different flights back to back using increased sim rate and comparing my fuel to what Simbrief and fuelplanner say it should burn during those flights.




Everything else in the cockpit works great. I've already performed several flights and CAT III autolandings. Having a full working MCDU is nice. Individual engine startup and listening to those RR engines spool up is a real joy.


I will be creating a tutorial video on how to integrate the cockpit soon. If this is something you're interested in, follow this discussion.



Nov 15, 2018

Apologies for not getting the guide put out on how to accomplish the cockpit integration. I've been a bit busy with other things. For those interested, I'll try to get to it this weekend.

New Posts
  • Just thought some of you XPlane 11 users would like some freeware. The two that caught my eye were the T-80 Falcon II and the J-3 Cub. https://forums.x-plane.org/index.php?/profile/466162-a-pilot/content/&type=downloads_file&change_section=1
  • Just wanted to request a TBM 900 added to the roster if possible. Should set us back about 4mil but I thought i'd ask. Paired with a Kodiak they would be my main stay aircraft. I do enjoy the AirKing though!
  • Members, Last night, I attempted a flight from EFHK Helsinki to UHMA Ugolny in the Airbus A380. The failed attempt at capturing the RWY 01 IKB localizer (110.30) and resulting crash left me with many questions as to how I ended up in that situation. After reviewing my live stream, the answers were clear. I'll share my experience with you, including the stressors and issue with the ILS at that location (which I've since fixed and is available for download on the Black Mill website at the bottom :) ). Flight I went through my regular procedures by booking the flight through FSAirlines, spawned my A380 aircraft at EFHK Gate 26 (heavy) at 0530 UTC (planned 0600 UTC departure), and planned my route using SimBrief. My flight plan had me cruising at FL350, and the total trip time was estimated to be 7 hours and 42 minutes. Using the SimBrief downloader and the MCDU from my newly integrated Black Box Simulations A340 cockpit, I quickly loaded the flight plan and filled out all the necessary INIT and PERF information. I checked EFHK ATIS, set my barometer, started FSXTracker and the FSAirlines tracker, loaded the correct fuel, requested clearance, and taxied to RWY 22L. The departure from EFHK was easy, and within 40 minutes, I was cruising at FL350 on my way to UHMA. 200nm from UHMA, I check the weather forecast. It's -6c, cloudy with precipitation, with from the northwest at 7 knots, and QFE is 1015. I check the charts, and I'm clear to descend to 3000' for the approach with no fear of obstacles. I anticipate descending to 2770' on final to get established on the RWY 01 IKB localizer (110.30). As I reach 3000', I am beginning my approach at 200 knots, so I activate the approach phase on my MCDU. I am flying parallel (downwind) to RWY 01, but I can barely see the lighting out my left window. I follow my flight plan to the southwest, turn to base, then turn on final. As I turn on final around 20nm from the airport, I set my speed to 130 knots for the landing. The A380 begins to slow down, and I begin dropping the flaps and set the autobrake. I press the LOC button on the autopilot, and I look at my PFD to watch for the localizer. Nothing. How could I have missed it?! It's pitch black outside, but I can make out quite a bit of snow coming down. I manage to spot the approach lighting from RWY 01 ahead, but it's too late. I'm still at 2800' with no time to descend. I fly over the runway, set my speed hold to 200, heading hold to 010, flaps up, gear up, and make my plan to go around. I turn left to heading 280, then left again to 190. I'm downwind of RWY 01 again. 10nm out, I turn left to 100, the left again to 010. I won't fail this time! I double-check my ILS freq iaw the Navigraph charts. 110.30. Check! Course 012. Check! Speed hold back to 130, flaps down, gear down. The stall siren sounds. I look up from my cockpit, but it's too late! My speed is under 100nm and there's no way to recover! My A380 plummets into the ocean south of UHMA along with 653 passengers on board! Stressors Prior to me attempting this flight, I had spent all of Saturday curled up on my couch with stomach cramps and nausea. As with any flight simulation aircraft, only one PIC is in the cockpit (unless cockpit sharing), so work load is much higher than irl. By the time I had reach my destination, I had been awake for 20 hours. Live streaming on Twitch and communicating in the chat. Night landing in inclement weather ILS Issue The default UHMA Ugolny airport does not have an ILS! It is supposed to, but for some reason it doesn't exist. My guess is that it may not have had one in 2006, or it was overlooked during development. I've since fixed it, and you can download the fix on the Black Mill website at the bottom for free! After watching the video from my crash, I've learned new things about flight simulation and myself. I have also found a new respect for real world pilots. Stressors have a large impact on our ability to perform as we normally would. Honestly, I could've made that landing any day of the week in flight sim without ILS. I've actually landed in worse conditions, but because of the reasons listed above, I became distracted, which caused pilot error and ultimately resulted in a crash. I really enjoy going back and finding out the reason why things like this happen! I look forward to seeing your feedback!