All Activity

No worries. It's okay to disagree. I wish more of us could do this. All the best.

I've also noted, that when "off', that caution light looks lit, compared with other aircraft I have. Until you look at it when it is really lit. Then it makes sense. Had me confused for a while.

I take note that you’re seeing something different from what we’re seeing. Your screenshots show it as orange, and both the developer and myself have confirmed that it’s not lit in those shots. I’m not sure what you’re seeing that makes you think otherwise, but it’s pretty clear in your screenshots that nothing is lit. We really value your long-standing relationship with us, but I’m not sure how to explain this any other way!

Okay. I give up. On my display, Nvidia 570ti, it is definitely red. I acknowledge your pic shows orange and assume this is a pic of the actual cockpit. So be it. I flew for 40 years and am familiar with a master caution. I won't waste any more time on this. I am a long term customer who has purchased many of your aircraft.

They are not the same color by design of the manufacturer. One is red, one is orange. Neither are illuminated in your screenshots.

So, problem solved. I still had an old basic profile for the HCB and can now fully operate the Glareshield with it.

With respect compare it to the master warn light to its left.

It is not illuminated. It's a bright orange, but it's definitely not lit up there.

Actually it is a master caution light that is illuminated. The fact it is red in your c525 caught me off guard as usually they are amber.

It is above the airspeed indicator.

The warning light is not turned on in those photos. What light are you referring to?

I'll revisit the topic. First of all, thank you very much that AirbusFTW has gone to so much trouble and provided users with such a comprehensive program for the HCA + HCB for the Challanger 650. Unfortunately, however, I have failed to implement the HCB in the XP12. The HBA works perfectly. I have “installed” the profiles with the configurator and the HCA also works. I have completely set the configuration of the HCB in the XP12 to “do nothing” so that there are no conflicts with the HCB profile in the HCB. But that was not successful. Unfortunately, I can't create my own profile with the HC configurator, as I don't have the necessary knowledge. That's why I tried to create something with the joystick settings of the XP12 that at least covers the core options. Of course, this also includes the implementation of the flight performance with the autopilot. Alternatively, I created a “pure” XP12 profile for the HCB, which at least enables the standard functions. Unfortunately, there is also a problem there: I can't find a solution to provide the stretch buttons on the left and right with XP12 for the C650 with valid commands. The control of the buttons in between I could provide with C650 own commands. Maybe someone from the community can help me?

I was setting up for the RNAV Y Rwy 20R at KSNA (John Wayne). As I got close I went used the DIR button to HUKEM (a point on the approach) which was basically straight ahead of me. The PFD showed the magenta line on a heading of 197 (the final approach course) but Hukem was straight ahead of me. I flipped it into heading mode based on the MFD plan view and waited until I got close before manually turning to final and then engaging the autopilot. Attached is a screenshot of the aircraft about 5 miles prior to final intercept. For some reason I have the hardest time with the approaches to KSNA. Is this because HUKEM is not an IAF? I fly into KPSP all the time and intercept at a midpoint on the approach. It seems to work in other areas. This is the only airport where the FMS goes bonkers. I flew the ILS Rwy 20R yesterday and when I intercepted final at SNAKE it started into a right 360. Since I wasn't on Pilotedge, I waited to see what it would do and it just kept flying in circles until I manually intercepted final and stepped to the then waypoint HUKEM.

UPDATE: The issue (when autostarting the SAAB340) seems to happen during the Left Engine Start verification. Just sits there forever, verifying. In one test, several errors appeared on the warning display, and the master warning light was triggered. This time around, I discovered some things: -The GPU was removed during the process. Viewing the auto-start externally, the GPU is never brought in, but the chocks, etc are removed at the start. I thought maybe this was just a visual thing, but noted that the External Power indication in the overhead panel was off... so the auto-startup was occurring (supposedly) under the plane's internal power... which may explain why I would sometimes get warnings/errors (battery low?... and then other things get affected as a result?) -The infinite hold/stop that occurs when the Left Engine Start is being verified can be fixed by manually setting the throttle from GRND IDLE (which is what the autostart sets it to) to MIN. This results in the rest of the auto-startup to occur, up until you reach the Right Engine Start verification, whose pause is also then fixed by manually moving the throttle to MIN. The remainder of the auto-startup occurs, and successfully concludes (complete with Auto-Start Complete message). And, the lovely and previously absent Beta engine growl finally occurs. The only other issue I've noted so far, which I can't find a workaround/fix for, is that the windshield of the SAAB340 in XP12 appears dirty (as if covered by 'calcium stain' water drop marks). It seems begging for the windshield wipers to be used, but unfortunately they have no effect. In XP11, the same installed plane doesn't seem to have this window texture (or it's extremely faint), but instead it has a window scratch texture, which seems to be absent in the same plane in XP12. So, that's a bit of a mystery. The 'raindrop stain' texture appearing in XP12 doesn't seem 'wrong'... it just seems like rain staining after a storm, which could/should be removed by the windshield wipers (but unfortunately isn't). Maybe some 'window dirt' flag/value is (mistakenly) set to high/full on startup, compared to 'clean'. The window scratches, meanwhile, seemingly should be present and at a constant, non-increasing value... but isn't, in XP12. Not seeing any windshield rain effects currently, either... at least with a stationary, unpowered SAAB340. So, it seems the only issue as far as auto-starting is that (seemingly) the throttles have to be manually set to MIN after each engine start (verification). I'm going to have to try a manual startup again and see if I succeed that way, too.

Good news and bad news - I did get the KLN90B to integrate with the MU-2's autopilot and instruments successfully - the only changes required are in the KLN90B's code. (It needs to override the nav needles and steer the NAV1 deflection, distance, and RMI needle when you toggle NAV-GPS to GPS on the MD41 panel, basically.) Bad news is, although I am using Git to track my changes to the KLN90B as installed in my MU-2... despite my intentions the commit with the functional changes to the code are mixed into a huge amount of automatic formatting correction... so I can't cleanly make a pull request to the official KLN90B repo and get these changes upstream. It's not a seamless integration either - you need to manually adjust the HSI OBS needle to the new track at each waypoint, with precise timing. Say you're flying 090° from A to B and the next track is 120° from B to C. Around 1NM from waypoint B, the GPS ticks over to the next leg and shows you're slightly to the right of the track from B to C. The needle deflects left, so the autopilot turns you left - and then to the right as you reach the BC track. This is probably realistic behaviour but I've not combed the manuals to check!

Same issue for me... I just bought the BN-2T Islander can't fly te G500 variant. Crash as soon as the Islanders plugin loads the G500 crashes X-Plane.

...would also like to see a status update from tkyler It's been a long time since I heard anything from him

Well I for one will not be buying any of their products until this is available for X-Plane 12.....................

I've been doing a lot of flying in the latest betas of the sim. It is really shaping up to be fantastic. I'm really excited at the thought of this aircraft getting an update that fully utilizes all of the the visual and audio aspects the latest versions of X-Plane has to offer, as well as the other things that need work that were previously discussed. I know you guys are not a fan of the update question, but I'm curious if there are some details that could be shared as far as what's being worked on. I'm really finding myself wanting to fly this aircraft even more so based on where X-Plane is going. Thank you.

It is the main red warning light that you press to reset. When pressed it does not reset. The main annunciator panel is clear. Next time I have the sim running with the C525 i will take a screen shot.

SF260 Red Bull Livery View File This is a livery for the JRollon SF260D, inspired by the Red Bull Racing liveries like N26AM. The livery is baked in here, so if you wanted to use the supplied texture, you'd need to "delete" the supplied part of the texture. This livery is in 4K. If you enjoy my work, consider supporting me on Patreon to cover some of the horrendous Adobe-costs ;). Submitter pilotdeviation Submitted 05/01/2025 Category General Aviation  

Can you send a photo showing what you are referring to, showing both that and the main annunciator panel?