All Activity

Hi iniBuilds Team, I’m writing to report a texture rendering issue that is exclusively affecting the A350-900ULR variant of the A350 aircraft add-on. This issue occurs with the default ULR cabin configuration. No HUES modifications are installed or enabled, and I am using only the default livery included with the base aircraft package. No third-party texture, livery, or model modifications have been applied to this variant. To rule out local file corruption as the root cause, I have completed the following troubleshooting steps: Fully re-downloaded and reinstalled the complete aircraft files（v1.2.4） Deleted the WASM files Reloaded the aircraft in the simulator and restarted the sim to confirm the issue persists After cross-testing, I can confirm that this texture error is unique to the A350-900ULR variant. All other A350 variants in the package do not exhibit this issue under identical testing conditions and simulator settings. I’d also like to ask if other players have encountered this same issue. I hope this issue can be fixed as soon as possible. Thank you for your time and support.

Hopefully this is where other corrupt shared textures are that affect so many other INI sceneries and developers can go in and piece them apart, especially for Xbox users as we no access to folders and files.

Dear Inibuilds community, I have been trying to update the AIRAC cycle for my A350 Airliner on MSFS2020. The Navigraph creditial has been successfully connected to the aircraft. However, when I click on UPDATE NAVDATA button on the OIS, the update never start (which suppose to appear the download progress bar, followed by green bar when completed). Please see the screenshot in the attachment below. Is there anyone encountering the similar problem as me? I have tried following different tutorials on different forums but all unsuccessful. Thank you in advance!

I've passed this along to the team, thank you for this 🙂

There are additional updates coming that aim to tune this exact behavior, thank you 🙂

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

Yes, it should generally be done in the flow when setting up the aircraft to provide air to the packs, and the packs should be turned on also in the same flow otherwise people start complaining. 😉

Thank you for the additional information, this issue has been logged for the team and is under review, thank you.

A friend encountered this bug on a 2 hour flight last night - Aircraft just wouldn't steer

Yes agreed. The L1011 had a noticeably high nose attitude while landing, substantially different from most other airliners. This thread from PPRUNE lists exactly what you say, it should be maintaining 7 degrees nose up and a normal flare would be to 10 degrees. 13 degrees is the attitude to strike the tail. "On the L1011, the normal deck angle is 7 degrees during the approach and ten degrees in the flare, and any more than 13 degrees and the risk of a tailscrape is apparent." https://www.pprune.org/tech-log/9509-tristar-flare.html It was one of the things I was most looking forward to with the Ini L1011 along with DLC simulation as landing this airplane is just very different to almost every other airliner where at 10 degrees nose up you're smacking the tail on the runway!

Since I flew aircraft with flight engineers, I prefer to use the virtual one in sim. For the starting engines check, the virtual engineer should open the bleed shutoff valve if they haven't done so before this time.

With trim set, the aircraft tends to rotate quickly with little input. The DC10 and other aircraft I flew took some input initially and then nose down trim as you approach V2 +10. The trim is set for V2, so as you pass V2 the nose start to rise on you requiring you to trim nose down. In the DC10, when it was heavy/near max takeoff weight, you did a two step rotation. You do an initial pump to start the rotation and then the second pump to pull it towards 10 degrees. Passing 10 degrees, she is lifting off and you are pushing sightly forward while trimming down to catch V2+10. I would assume in the real L1011, if it rotated so quickly, you would be tail strike prone. Should be easy to get a smooth 3 degrees per second rotation rate.

The approach pitch appears to be low. It should be around 7 degrees on a 3 degree slope with flaps 33. This is from the manual and landing geometry.

After flying it few times, I noticed that the IAS and Mach pitch modes can be a little slow and not consistent. For the era of the L1011, this should be solid. I flew DC1030s and planes of the era were solid. The only issues I would see, which still impacts current aircraft, is temperature inversions. This causes the speed to change and leads to the aircraft pitching to attain speed. The aircraft can easily get into porpoising, which gets worst over time. The trick is to hit vert speed and lock into a climb rate. Once the aircraft settles, you can go back to IAS or Mach pitch modes. Once you get into Mach change over in the climb, aircraft can become a little pitchy as there is some variance along the Mach scale leading to the aircraft making large pitch changes. The heavier the aircraft, the better it performs in this regard. Again, the vert speed technique is used to settle the aircraft. Other than that, these pitch modes are very stable and quick to respond. So much so that you start in vert speed and increase it until the engines reach climb power and then engage IAS or Mach pitch modes. This makes the transition to these pitch modes smooth.

It's not working properly even after the update. I've downloaded the update, uninstalled it, reinstalled it, restarted the sim. It's still not working. Please try and help otherwise I might need a refund because its unplayable. I'll upload some pictures. Let me know if you want videos. I can't upload them here because the files are too bug. To summarise: Ive setup a new control profile. Only throttle binds I'm using are: Axis 1 - left lever Axis 2 - right lever Axis 3 - right lever Calibrating using the pfb. Setting reverse full and idle doesn't sync When at Idle reverse thrust is on. Wheh I move the levers to full engine it only goes to the climb detent. Not right through to toga. Despite me starting with reverse thrust set, reverse idle set, idle set and full set to toga. None of it works. The bars on the pfb don't even move correctly. Please help.

So potentially an easy fix for INI builds, to include whatever the corrupt shared texture is, in the files installed with the affected products. redownloading all that content is a large task.

Ah yes forgot about that I've been using it with INS only and havn't had any issues 🙃 Use this binding to toggle if that helps also 🙂

For me, I feel like the spoilers are waiting for the normally listed things above (landing/flaps/Idle or reverse...) and full braking action. The only time I've made it work when doing multiple circuits and rejected takeoffs (incluidng regular flights) to try it out..is where I slam on the brakes (90-100%). Which is not a normal thing to be doing.

Just wondering, have you tried making a seperate profile with no other bindings other than throttles (to test) that the 3 axis work and/or also try assigning 1 axis for all throttles and see if it works? Also, are you launching the flight as "shut down" or "ready for takeoff"?... To troubleshoot some other issue with the aircraft, I launched the flight as "ready for takeoff" to get going faster and the engines gave up after a few minutes.. so I suspect it stuggles with that if not from cold and dark. I find that "ready for takeoff" with more complex addons causes trouble with the flow/scripts that the models have to set themselves up.

to confirm - even with the latest update, I still have this issue. can't get off the ground

Just had this after a Flight from Manchester to Orlando. I checked the settings in the EFB and it was set how it said online it should be. The steering worked fine at Manchester and after landing I followed the advise I could find online but nope this plane would not steer. I don't think I'm ever going to use this aircraft again it's been nothing but trouble with either not steering after landing or WASM crashes. Ohh well £71 wasted I guess.

I’m glad it isn’t just me! it has been like this since the first version of the aircraft. I watched a video on you tube which indicated the red lights illuminated and button pressed were to show the whole spoiler system was disarmed.

Wouldn't you need to have a separate Omega Unit though?

Good to know 😉

Can you upload this to youtube or streamable and then link it back here, please and thank you