All Activity

I reported this on the Discord and indeed, the only way I got it working was to stream the aircraft. I couldn't get it to work at all with the aircraft installed locally. Logging in while streaming and then installing locally didn't work, as I was immediately logged out. That being said, it keeps logging me out (presumably with each update..?) Now I'm struggling to log in again even while streaming the aircraft. The QR doesn't appear on first load of the aircraft. Trying to link through my browser results in an error message (The user code is expired, invalid, or already linked to an app). If I press 'Refresh Code,' the QR code appears and I can now link, but even though it's showing as linked in my Navigraph account, it just doesn't work. This really needs fixing.

Just tried again but with a Simbrief import so there's no doubt over whether the coordinates were correct. Same thing happened. The INS gets stuck on 6 > 7, when it should change to 7 > 8. Looks to be correctly positioned on the moving map display. It seems to get confused as soon as I fly over the waypoint. I get the sense the aircraft feels as if it's 'missed' GWC VOR and tries to have another go by turning back. Approaching GWC. Leg 6 > 7. Correct coordinates and positioning on the map. Aircraft turns right overhead GWC. INS stuck on leg 6 > 7. Distance starts increasing. Aircraft now off track according to the moving map.

Hi. In both 1.01 and 1.02 I've noticed that the LOC or ILS buttons do not engage. The only way for me to track the approach path is the VOR function as neither LOC/ILS would work. I know people reported funny behaviour when changing from INS to radio navigation but I've tried it in a flight between 2 nearby airports (TAPA to TFFR), without even turning on the INS, and I get the same issues. Also, I fly in VR. Could this be the problem? I'll try tomorrow in 2D in case it's a VR issue but hopefully this is fixed soon as makes approaches in tricky weather impossible.

Interesting - with this does the INS show 78 as the correct leg and does the moveable map make sense to the waypoints that you've entered?.. just incase of input error (although you've proved it twice) Waypoint N5060.0E00000.0 is a good one because even if you get E/W mixed up it's the same location. So should be fairly safe from error. However interesting that the distance is increasing with leg 78 would only indicate that it thinks the waypoint is somewhere else.

In my case, the front cargo door kept opening and closing continuously, making it impossible to load cargo, but I just tested version 3.9.2 and it has been fixed.

As I pointed out, you will not see any change in APU parameters. Going to MAX MODE fully opens the APU inlet guide vanes...you can't see that. It may raise the APU TGT as more air goes through the open inlet guide vanes to the load compressor but not necessarily. When you're starting engines, the packs are turned off, galley power is turned off, ATMs are off...the load on the APU is greatly reduced so you may actually see a decrease in TGT. The only time we ever manually used the MAX MODE spring-loaded position was if we got an INLET FLOW light (probably due to ice forming in the inlet duct) that caused an automatic APU shutdown. After 3-5 minutes and the INLET FLOW light going out, we would then start the APU in MAX MODE.

Hi, Slightly odd one. I've been doing a few practice departures and climbs up to cruise, getting a feel for the aircraft. I departed from Luton (EGGW) and set course towards Menorca (LEMH) using the following route, the first 9 waypoints entered manually (not imported through Simbrief), starting at RODNI. EGGW/25 N0480F350 RODN1B RODNI N27 ICTAM Q63 CPT UN859 SOPIL DCT BALAN DCT EVPOK DCT NARAK DCT GAI DCT LOMRA DCT ROCAN DCT GEANT N727 SARGO SARG5B LEMH/01 Upon passing GWC VOR (Waypoint 7 - N5051.3, W00045.4) The aircraft should have turned slightly left towards SITET (Waypoint 8 - N5006.0, E00000.0). Instead, it entered a right turn, almost as if it's trying to double back to GWC. This happened a few days ago. I shrugged it off as user error, perhaps a bug. I tried again today and the exact same thing happened at the exact same point. I managed to get it into heading mode to turn it back towards the next waypoint (SITET) but I noticed the distance to the next waypoint was increasing instead of decreasing. Clearly it hadn't sequenced properly. I had to do a manual track change from waypoint 7 to 8 to get it work properly. Am I doing something wrong?

Thank you for these, I'll pass it along to the team.

Are you able to upload a video of this occurring, additionally just to verify, nothing else managed to rebind or is still binded that is now causing a potential conflict.

hi there! since the new update the yoke on the cpt side shakes while on the ground. the yoke on the fo side doesnt do this.

Fuel Pumps.mp4

Hi, As requested. ACS Switch.mp4

OK thanks. Any idea of timeframe and are other users reporting the same issue?

It is still being investigated by the team from what I can see, has not been forgotten. Thank you 🙂

Hi Jamie, another update but the throttle calibration is still not working. Do you know when it's going to be fixed or looked at?

I'll pass this along to the team, thanks

Dear ini team, I’ve been recently enjoying the wonderful a340 brought by you and noticed that the Operating Empty Weight (OEW) on EFB is set at 123 t. However, after cross-referencing this with the technical data from the Aircraft Operator’s & Owner’s Guide (Issue 52) by Aircraft Commerce, there appears to be a notable discrepancy. According to the official specifications provided in the guide, A340-300 Series have a typical OEW of 287,000 lbs (130.2t). The OEW range for various -300 configurations is 290,000 to 293,000 lbs (~131.6t to 132.9t). Besides I found a real loadsheet in video (https://youtu.be/Dy5ubc9yC-A?si=101AqGczmlMnt448) 21:17, showing the OEW at 134,400 kg. But considering the fact that a340 has so many variants, it's also possible that I missed some specs due to my lack of research. Thanks again for your nice work. Best regards. ISSUE52-A340-300SPECS.pdf

Which is the correct variable for the CPT baro display value on the EFIS. I used L:INI_EFIS_L_BARO_VALUE but the SDK Behaviour Viewer only shows 0.000! Thanks.

I'll pass this along to the team, thank you

Thank you for this, I shall pass it along to the team

Has the livery been updated in the livery manager?

I shall log this for the team, thank you both 🙂

Hi, for the first two are you able to send a video over, the later just needs a screenshot if able. Thank you 🙂

Hi, The registration placard assets were added for the paint-kits, but the liveries are still awaiting their fixes for the registrations. I'll double check to make sure, thank you.

Having tested the latest versin 1.02, with the plane spawned on the runway in ready for t/o config, I still see the AP struggling with the vertical modes. IAS hold seems to work, but as soon as I change to VS or ALT hold, the wobble starts. Also, when in VS mode and retracting the flaps, the nose pitches down and the plane starts a temporary decent. Please fix the AP asap, as this current state makes the Tristar unflyable for me and I guess many others, too. Best regards, Wolfgang