Max

We'll ensure this is all updated in the v1.0.3 paint kit release. The updated kit will include base textures for the - New wing/winglets Exterior textures (+ markings and door outlines where applicable) Cabin Cheers.

Hello @Pionites, Thank you for your post. There is no motive to restrict users from viewing the sim package - nor do we control the final compression format on the textures, this is all automatically handled by the flight simulator engine upon compilation of our package. I understand that when making your own paints, you take control over this aspect. Upon your request as a paying customer, there is no objection for us to share the additional PBR files here. I've zipped up the PNG versions of the fuselage PBR before compression, so you can control the compression and achieve the best result. Let me know if you have any further requests. Cheers. A343_PBR_20102025.zip

Seems like a problem - we'll amend for an update we're to push soon! Cheers.

@MediocreGorilla Hey - rest assured, that the issue is resolved on our end. But we are waiting for a larger update, which breaks liveries even more (along with other fixes included) to push this out since we need to update all of our liveries to be compatible with it. Hopefully this is sooner than later. Cheers!

Hello, Are you using any third-party, or old liveries from iniManager? Likely that this is the case and they're incompatible with the latest version of the plane. Cheers.

Hi, The advice would be to paint onto the compiled .gltf model you've converted if you wish to paint such lines directly onto textures. But we will not be providing one as we intend for liveries to be created using 3D decals, and the converted .gltf is a hacky way of doing so and doesn't meet the quality standard of what we're willing to include in an official paint kit. Cheers.

Your detailed feedback on issues/bugs you are experiencing with our product is welcomed with open arms and much appreciated. Best regards,

Hi, Is 'PW' noted in the title of your livery? I believe engine detection is based on .cfg entry title. Best regards,

Is anything spiking in task manager when you experience these stutters?

Possibly, could be the cause! I'll also have our team take another look if that could cause a hiccup somewhere when using both controls on the door to close/open it.

@halfur, hello! Is your cargo door fully closed? I can't replicate this behaviour. The lever is tied to the first two keyframes of the open/close animation of the cargo door, so it would only show like this if the door isn't fully closed.

Hello, I think the best solution is to allow you to slide the seat back using the switch on the side, I think removing the seats might confuse some users as it's not a feature I've seen in any other aircraft 😅 I've added this as a future changelog item.

Hi Oldal, Xometry are making Keflavik, not Axonos. I've moved your post to the correct category. Cheers.

@Bavionic, I understand your frustration - but this is not quite true. We have used the tools and methods provided by Asobo to exclude any trees from appearing on the airport, if the game engine is not respecting such, there isn't much we can further do until Asobo fix the bug. Again, for both the ILS and Tree matters, we're doing all we can when we can to come to finding a solution since we don't disregard such issues as customers are still discussing the matter actively as being an issue. I would hope (and yes, as you've mentioned we run on hope here too when there's thus far no possible input from us to resolve the matter) that the next update compiled on the latest patch of the simulator will resolve these matters. Cheers.

Could you guys try to remove everything else from your Community folder except Heathrow? Otherwise I suggest you wait for the next update to see if we can resolve this issue since the configuration for the runway and ILS here can't be further changed or improved or else we are unable to make the approach correctly. @xChris93 - so I assume this was no resolution for you? Cheers.

@Bavionic, Sorry for the frustration caused, and I understand that it's quite a pain to deal with all these issues when all you want to do it fly. Unfortunately, the trees issue still isn't resolved by Microsoft in the latest update. As for the ILS issue, you'll have seen in previous threads that it's causes by either the aircraft the user is flying or the content.xml, that's why I echo that you should upgrade your FlyByWire A320 version to the latest stable non-development version. We're here to help, let me know if you have further questions. Cheers.

@abdulaziz 👀

Your FlyByWire A320 might need an update to the latest stable version. Cheers.

We expect this issue to be resolved for the next update that's coming soon, hang in there. Cheers.

Hello @Regis, The next update will feature decreased system resource usage, mainly on VRAM. Hopefully this will fix any freezing you encounter. Cheers.

I would surely go by @AndyM's suggestion since random third-party conflicts are to blame for issues like this. I'll assure you no default textures are used on our custom objects though 😅 Do let us know the outcome if we need to troubleshoot further @LondonLCY. Cheers.

@Slightlyreliable70, As @AndyM has mentioned, this is a potential solution. Other solutions have also been linked to aircraft themselves such as the FlyByWire where a simple update or downgrade solved the issue. The issue is isolated to a specific few customers and everything is set up for this runway as it should be during development. Cheers.

As this matter is resolved, I'll be locking this topic. Cheers.