All Activity

So, -13% just about averages out. The main question I have however is, who is right and who is wrong. i.e. Why is one 13% lower, or the other 13% higher. Which one is closer to book values?

When will the Tristar become available in the Inimanager app for updates?

Whenever I perform an S/C during cruise the aircraft automatically engages the AUTO-DERATE option and it doesn't allow to change it into CLIMB mode.

This bug was introduced in V1.2.1 and still remains unfixed in the latest V1.2.6, and I have no solution to it. After entering weight data, the 90-degree right-angle turn route between AA263 and AA262 deviates during rendering, and the autopilot will follow this offset path in full managed mode. Even removing speed and altitude constraints of this waypoint cannot fix the issue. This problem exists in SID and STAR procedures at many airports.

After some experimenting I managed to find the root cause. In the MSFS Graphics Settings, if I set my Texture Resolution to Low, the engine dials are orange. If I set Texture Resolution to Medium, dials are green. Really weird bug, and although low priority, I hope it will be fixed some time in the future 🙂

Thanks issue is logged for further review. I was able to reproduce. The same axis assigned via FSUIPC or Mobiflight doesn't exhibit such behavior for me which is puzzling. Logically if the axis input was being blocked/intercepted by the aircraft code then it should not work via any external tool 😅 Anyways, for the time being assign via the sim directly to work around the issue.

Above 60 kts, tiller and nosewheel operation inhibited, which is most likely what you're experiencing. Any rudder axis input above 60 kts will only move the rudder. Tiller (Nosewheel Steering) Axis will not be operational. In v1.0.7 there is an Flight Model update coming to give more effectiveness to rudder alone but the rest appears to be by design and not a result of any hydraulics. Please verify against the 60kts threshold for what you're experiencing.

Using ZSAM DOVP7Y departure, the AM401 should be flyover point as displayed on MCDU, but the path on ND passes abeam of this point rather than overflying it.

Hello team. I noticed a small texture issue on the Inibuilds A321LR NEO. The decal from landing gear is incorrectly reads A320 mtow 79 t. A321 neo has different mtow around 93+. Please update this decal in future patch. Thanks!

Did you reinstall everything from the previous of version of windows or did you format and cleanly reinstall everything from scratch?

v1.0.3 of iniBuilds Larnaca (LCLK) for MSFS 2024 has been released. This update fixes some missing jetways at gate 47, adds the Revolut branding to jetways and adds A/B gates to 11-13. This update can be downloaded via the iniManager. v1.0.3Added missing jetway at 47 Added A/B gates to 11-13 Added Revolut branding to jetways

I am unable to connect the bridge at D1 and D1X using GSX or default method.

Has happened a few times now, line up and start thundering down the runway. Some distance down the runway the rudder will go to neutral position and stop responding to joystick inputs. If you're lucky and near/past VR you can pull back and use ailerons to correct the issue. Eventually the rudder comes back into operation. My theory is the hydraulic system. Using brakes or tiller/rudder will deplete the hydraulic pressure very quickly. The plane has 4 systems and when you dab the brakes you can see a noticeable drop in system pressure. Usually A and B, then they are slow to recover. I let the FE sort the panel out but from past experience I turn on the PTU B-A system ON as A system will deplete quickly without the help, you will also get warning messages flash up briefly about system pressure. Should he put B2 and C2 to AUTO instead of leaving them in the off position?

Can we adjust the Z please? Have a 1604nm cruise and I keep seeing the Z bleed off screen.

Got it, thanks. I'll pass this along to the team.

I’m not entirely sure how it works on the 350, but I imagine it’s the same as generic Airbus logic. FLS is a system which allows rnav approaches to b be flown with the same indications as ILS approaches. It’s often an option rather than default, and can only be used on rnav approaches with a straight approach. If you activate the LS push button and there is a straight in approach with FLS available, the final approach modes will be F-G/S and F-LOC. But for any rnav approach if you don’t activate LS you should get FINAL, APP NAV and then FINAL APP when both are captured. Similarly if you try to use LS but it’s a curved approach and FLS is not available it still should be FINAL, APP NAV, and then FINAL APP. But the a350 is currently treating all rnav approaches as FLS an it seems to be impossible to get the standard FINAL, APP NAV, and FINAL APP.

I tried to delete the streamedpackages folder but it doesn't solve the problem, at this point I hope that inibuilds will find the solution to this problem, since it is only on their airports

I don't have any other device/axis bound to the throttles as far as I know, but I'll double-check. What's even more odd is, if I bind the throttles in the sim instead of in SPAD, they work fine. Edit: Just checked and nope, no conflicting bindings.

Assuming your programming IS correct, then should you not tone down the figures of the thrust settings in the configuration file. To climb to FL 350 at MTOW with a residual vertical speed of about 1000 fpm at CL2 seems way off. AT weights of 475 000lb, the N1 cruise value @ M.84 should be in the 80's (80-85%) and NOT in the 70's. Is it not possible to choose between CL 1 and CL2 and select only 1 (eg,CL2 for the whole climb)?

This is a fantastic explanation and most probably the solution too. I'll setup accordingly and try. Thank you so much for taking the time !!

v1.0.5 of iniBuilds Southampton (EGHI) for MSFS 2024 has been released. This update addresses the runway lead-in arrow and centreline misalignment as well as adjusts some GP colouring and grass aprons. It also fixes an issue with missing grass and more. v1.0.5Fixed minor runway lead-in arrow and centreline misalignment Adjusted some GP colouring and updated grass aprons Fixed issue with missing grass Terminal and main carpark updated to SPCs with adjusted lighting for FS24

v1.2.3 of iniBuilds Honolulu (PHNL) for MSFS 20/24 has been released. This update focuses on visual and ground environment refinements, bringing improved interior rendering behaviour alongside updated clutter placement, terrain blending, markings, and jetway adjustments for a more polished airport experience. Please note: Users will need to uninstall the existing PHNL install to avoid the detail/parallax interior conflict on reinstall This update can be downloaded via the iniManager. v1.2.3Fixed issue with parallax and detail interior showing at the same time All GSE/clutter/veg placements updated Flattened road bridge on TIN to blend with model Various GP markings fixes Various jetway fixes iniBuilds Team ❤️

Hey @zbrainlezz That is odd, I do have both and I'll check as well. I've been using mine bound via FSUIPC7 at the moment so I do know it can be controlled externally, but will see if can reproduce the above issue via SPAD specifically. Based on video alone seems like while Bravo is active, its sending commands but once it stops giving commands, another device thats still at idle is then taking over perhaps? Can you confirm there isn't another connected device that is being read by the sim (or SPAD) also sending thrust commands, thereby creating a conflict with each other? Thanks!

Hi, are you able to record a video adding the issue, I am not as familiar with SLS/FLS unless I'm just mis-remembering. Thank you

Quoting you above "The way its modelled now is it will try to use calculated CL2 table values for your weight, temperature and altitude ranges. If outside the tabled parameters, it will instead use the calculated CL1 values for your current weight, temperature and altitude. It will transition back to CL2 if within tabled parameters at the next update point." Are you 100% sure this is correct?