Leaderboard

Captains, This will serve as a formal forum announcement that we have released the version 1.2.1 update for the BN-2 Islander. All customers who have purchased the BN-2 Islander up till now have been sent an e-mail by X-Aviation with complete instructions on how to obtain your update. We have made this a very simple process! For those that purchase the BN-2 Islander from today forward, your purchased download will already be updated to version 1.2.1 for you. What if I didn't get the update e-mail? If you did not receive your update e-mail don't fret! X-Aviation has updated our system to allow all customers to update with ease, regardless of whether you received an e-mail for the update! Here's what to do: 1. Login to your X-Aviation account here: https://www.x-aviation.com/catalog/account_history.php 2. Find your original BN-2 Islander download and re-download the file. It will download as the latest version! The following is a list of additions/fixes included: Improvements / New Features: Fixed G5 displays (AFM G5 Required) Improved panel normal map Fixed gap in altimeter edge Fixed incorrectly rotating wheel Added rotation constraints to the ammeter Removed phantom glass on overhead panel Added back in the flaps placard As always, thanks for being a customer with X-Aviation. We appreciate your feedback and support! Enjoy this latest update, and stay tuned to the forum as we continually announce the latest happenings.

FYI those of you that are using G2, HP fixed this audio loss issue when using TBM 900. It doesn't matter anymore if you start WMR before X-Plane or after X-Plane. There are no more sound loss. You can download the audio fix firmware for G2 here https://support.hp.com/us-en/drivers/selfservice/hp-reverb-g2-virtual-reality-headset/33835976

The GNS430 display of nav data date is NOT static. There is currently a bug in logic and will be fixed in the next update.

It can be set using the XPlane keyboard settings... You can also set it to a joystick button (as I do)...

OFF: Turns lights OFF DIM: Enables the FLOOD R PNL knob to adjust the dimming BRT: Lights on on full power.

ah interesting. i do own the realityxp GTN750 but I currently don't have it installed. i wonder where this could be coming from. its been driving me nuts . i wonder if it could be the terrain radar plugin. ill ask in that forum

Hello all, Just getting started with this excellent airplane. Very impressed with it, but just had a few questions. TOGO button: I read in the manual the function of this button and understand it is used for taking off/go around. But how exactly do you use it? I think it said for TO you press it and it sets wings level and 10 degree pitch upwards for climb. Do you press it after you leave the runway or set it before? I guess I am a bit confused on when you would actually use it in real life. Approach speeds. I am looking for the proper approach speed in landing config (full flaps, gear down). I have read 85 KIAS, but wanted to confirm. Also do you hold the speed and throttle until after touch down and then bring it back to flight idle? Or should you pull the throttle back after flare? Interested in the method real pilots use, I want to make sure my approach procedures are correct. I am sure I will have other questions as I think of them, but so far this is what I have been wondering after my first flight with this aircraft.

As it is always good to know and understand the math behind everything to do with the performance of the aircraft you are flying. Well... Not good but should be a must. I use either this website or app (both iOS and Android) that is built for the real TBM to use in real life flight planning. They are stand alone apps and not connected to XP in anyway. But I have to tell you it's almost 100% spot on every flight I do with the TBM. Feed in all the information like fuel on board, pax weight start and destination airfields and so on and it spits out a lot of numbers. It even gives you current ATIS for both airfields you enter... Even has everyone of the TBM checklists and so on. It's a really hand app to check out.

You can use the first stage of flaps at 150 knots quite safely and then gear down at 140, at 1000 feet around 120 knots then flaps full, 500 feet 90 knots and hold that down to the threshold where you should be at about 85 as you cross, then at 30 feet then bring power lever to idle. Ideally you should be stalling just as the mains touch at around 75ish, winds permitting.

To point 1: As it only sets the FD, you can hit TOGA whenever you want. But you should do so before starting your takeoff-run. Approach 85kts is correct, according to the POH, and you Idle before touch down.

As a rule of thumb, this works quite nice: For a 3° descent path angle, subtract your target altitude from your current altitude, drop the zeros and multiply by 3. If you're flying at 27000 ft and need to descent to 3000 ft, this would be 27000 - 3000 = 24000 drop the zeros = 24 24 x 3 = 72 So you start your descent 72 nm before your target waypoint. (you can always add a few miles for safety) To figure out what vertical speed you need roughly for the 3° angle: Multiply your groundspeed in kts by 5. 280 kts would make a 1400 ft vertical speed. Quite easy and works for any plane.

I was manipulating the prop levers all flight with a hardware axis. I had just moved them to full forward on approach. I moved them backwards when I had stopped with hardware. Took my throttle out of reverse and the prop levers jumped to full forward again and the throttle became unresponsive - also locked in full forward position. Both of them were then unresponsive to hardware inputs. I waggled my hardware axes forwards and backwards and neither would catch. Airplane drove full throttle off the end of the runway and into the lake. I don't know what else to tell you. You should be able to look at the code that drives these systems and hopefully use that to reproduce the bugs. Separately, why on earth are you insulting your customers? I just bought your module for $50, and while coming to this forum to report a bug I saw you insulting people, which informed my tone in submitting my own report. I write reviews of modules and I'm a flight sim developer myself, so I am pretty willing to give you the benefit of the doubt, but I won't be buying any more of your products now, and if I do review this plane I'll make sure to note the way you berate customers. On my opinion that the module is not functional: I can't land the airplane using the same hardware I use for every other aircraft I fly in the game. As a reviewer, a plane with a throttle quadrant this unconventional to control is functionally broken as a product, especially when it has existed for years and is advertised as mature. If your response to customers was "we are sorry our custom implementation of the throttle quadrant is upsetting player experiences and we'll look at what we can do to improve that" then you wouldn't see people getting upset.