All Activity

HI, I will pass this along to the team. Thank you.

All good, happens to me to sometimes 😄

Its not that (I know they are lacking a bit), its more like the sounds are assigned to wrong nodes or the sound cones are configured wrong.

My bad... few moments later I saw, that there was pushed an update in the iniManager explicit for this livery, which fixed the mismatch 🙂

Good to know, It is great for reference on manual approach. I use the equivalent a lont on A306.

Hello i am wondering too

I have same problem too. Does the SAP have a logging function?

I hope they don't abandon this topic; these liveries are highly anticipated by the Xbox community, especially South Americans, since no pack from that region has been released.

Just for reference. SS3D Vol 1 is for both 2020&2024. They have no 2024 exclusive version.

What specifically does POI Models enable/disable?

The first photo I posted was of the actual JAL A350. Would you consider updating the Japanese text for ① to ⑥ to two photos? Please change the color of ④ to ⑥ from black to red. Do you know about the new satcom model? Thank you

Hi, It's possible something didn't initialize properly for the 1000 on loading that did for the 900, I recommend clearing the WASM Folder via the steps provided below and then relaunch both aircraft, return to menu after initializing both, then load back into the 1000. Let me know if this works, thanks.

Hello, i am having a problem which i have tried to fix but í cannot find a solution. When I want to use the 350-1000 with any livery including the white base livery and I spawn in at a gate(no metter if big or small, on apron or with jet bridge) I cannot enter the cockpit. I can take the engine covers and pitot covers off but neither does the "enter the cockpit" button at the bottom near the efb toggle button or the strg+c shortcut does work. This is only happening on the -1000 version, on the -900 version everything works including the strg+c shortcut. does someone know why this is happening? thanks in advance!

Hello, I appreciate you providing reference and I can admit when I am wrong so I appreciate the correction. That being said the L1011-500 being modeled is based off a real reference that we were able to obtain. Thank you.

Yes, that was me and sorry I never got back to clarifying last time you asked, at the time I was under the impression at the time that there were separate logs for Xbox and PC since the issues can vary uniquely. It turns out that the logs are one combined log with specific mentions. That one is on me and I apologize for any confusion caused by my mis-statement. They should apply to both as we are version syncing them here on out (provided no other unique breaks happen); Xbox users and PC alike will just have to read for specific mentions to PC or Xbox in regards to fixes in the main Community Log found here on the forum whenever those updates are published.

Thanks for following up; appreciated. It was only recently that one of your colleagues mentioned that the published recent update might not relate (fully) to Xbox, hence drawing attention to any update information that might or might not relate to both PC and/or Xbox. It would be good if it could be clarified going forward in any published updates that it applies to both systems (or not).

Hello, So we aren't able to include a changelog on Xbox, however whenever the community posts go out regarding major aircraft updates; e.g. A350 v1.2.3, there will be a full log since that will apply to both Xbox and PC. In this instance with Xbox v1.2.2, the lighting fix had to be addressed, ingested, and is required to have a new number even for a hotfix and as such pushed the Xbox from 1.2.1 which was shared with PC Version, onto v1.2.2 Ultimately all major changelogs will come in the form of Community Updates and any minor hotfixes/changes to Xbox require a new version number and don't get formal logs Hope this helps, Thank You.

The picture is just an example. The equipment of tapes has nothing to do with early or late or the variant. It was an airline option regardless of the production year. So you can put the tapes on any variant. LTU bought their -500 from 1981 to 1983 and they all had tapes. So it is not quite true what you say. inibuilds should be more flexible here to provide authentic combination of liveries and their avionics. Here is one from an LTU -500:

This is IniManager' JA01XJ.

Hello, I wanted to bump this thread. I experience the same issue now, and I am pretty sure it did not occur before. I've landed with low braking just like dectenor2 said BTV far at the end of the runway. I exited the runway with about 80C and when I taxi to the gate the temperature goes up really quickly and goes beyond 300C without any manual braking. And I did check my brakes, they were fully released. Hopefully you'll be able to fix this little bug.

The photos I posted are actually photos I took myself! inibuilds' door placard in Japanese is here Currently, the ones I know of are JA01XJ to JA17XJ, JA01WJ to JA10WJ

Hi, Thank you for this detailed explanation, one piece of information I do need as I presume this is a livery from the IniManager, what is the Registration of this aircraft, Thank you again 🙂

I seem to have 1.2.2 showing.

Hello, Sorry to inform you but no there won't be an option for the Taped Gauges these weren't present on L1011-500, and even for non-500s very few early builds had these tape style. The image you posted is from another variant as the -500 has the DDU as seen below. Thank you