IniSteve

Hi. Thanks for the feedback! to point 1 - This is correct to the reference we had (late Nov.) and as its active construction we will never be up to the day, BUT, we do have some contacts at the airport and have a copy of the masterplan so you can expect some updates regarding layout in the future. to point 2 - What are you using for AI traffic? I suspect FSLTL which we've found tend to dance to the beat of its own drum and doesn't really respect gate/airline codes. With BATC/SI we saw much more realistic assignments but even then there is still a small margin of error

fwiw, it's been discussed. The issue with A300 is it's an older codebase that would require significant rework which just isn't possible at this stage. despite that, we bring it up in discussion often so never say never.

Can't win 'em all, am I right!?? 😉 Jokes aside, we can't do anything about individual issues related to streaming or bandwidth availability. We have also seen customers who report this issue once come back and say it's resolved a week later. Despite that, we will continue to investigate these issues and provide actionable solutions when possible.

Not sure what's going on with the forum. Can a mod delete the duplicate posts?

We didn't know. This wasn't seen at any stage of development or testing until wide release, after which we deduced it was related to streaming. In the meantime, we have pushed our findings to Asobo and we are trying to find the root cause.

We didn't know. This wasn't seen at any stage of development or testing until wide release, after which we deduced it was related to streaming. In the meantime, we have pushed our findings to Asobo and we are trying to find the root cause.

We didn't know. This wasn't discovered at any stage of development and testing until wide release, after which we deduced it was related to streaming. We have pushed our findings forward to Asobo and we are trying to find the root cause.

I can. Here are some benchmark results we saw from the last build to this update. Overall performance uplift in percentage Overall frametime uptick. You'll note significant increase in smoothness and reduction in stutters. What's more these results were captured on a 7800x3D and a 2080 GPU so a pretty mid-range build. We same similar results on laptop setups as well as PC's running 4090's

The HUD is going to get a richer update in the future. The specific changelog callout regarding the HUD has to do with colour and iconography alignment.

Stay on .70 if you can. It works with .71 but something on the SAP side is causing only the FO MDCU to function. We've notified WW and they plan to issue a fix in the next SAP update.

This is a streaming related issue that we can't reproduce with any regularity. The hope is subsequent updates to the platform resolve this.

Ready in your hangar when you are! Let me know your thoughts 🙂

They just require an update. The changes made to the model necessitates it.

I'm on the edge of my seat trying to understand you mean by "amusing" 😉

I know IniBuilds pretty well and I'm hoping our future products change your thoughts regarding this. 😉 We have in fact learned quite a bit since 350 (which you should be able to see in A340, a product that gets consistent positive feedback regarding performance) and are carrying that knowledge forward. On the topic of A350, we have a large performance-minded update in the oven right now that should bring a lot of respite to those on lower tier PC's.

I'm pretty partial to the IniBuilds version 😉 Despite that to dispel any confusion, ours is only compatible in FS2024 so that should factor into your decision.

It was me! I am that guy 🙂 As discussed, this is aimed at a more casual user. The goal was to bring this product into the sim to both see what's possible with mission scripting as well as continue with KwikFlight's charter of providing well-detailed but accessible military-themed addons in the civilian simulation environment. While you won't find complex multi-crew ops with this aircraft it should still allow for a nice change of pace from time to time. On the note we discussed regarding the gear compression, the released build should better suit what you'd expect to see with this airframe.

The 2020 version of EGKK is an Origami Studios product not made by us.

Thanks for the feedback, all! We're excited for everyone to get their hands on what we consider one of the coolest aircraft ever made.

Ah aha. Indeed FSUIPC can cause a conflict. A number of our testers reported that once they migrated to the latest FSUIPC beta, the issues subsided.

Hi. Glad to hear you're all enjoying the update. As Rich noted on our discord server, we're aware of the rain FX and investigating a workaround while we wait for a more elegant solution. Additionally, the sim lockup on exit is due to how the core networking API handles certain requests. It's another area we have identified as needing a server-side fix hence why we disclosed needing to hard-kill the process in TM. Despite that, we'll continue to refine the product so it meets your expectations and offers hours of enjoyment!

Hi all. I wanted to pop in and let you know we've made another update that addresses some more cosmetic issues as well as provides the option of an alternate engine/flight model that was circulating around in various forums. You can grab the update from the manager and read more detail about the changes here - https://forum.inibuilds.com/topic/23774-inibuilds-t-33-jet-trainer-for-msfs-v102-released/ Enjoy!

Rest assured. We have heard the community's words quite loudly regarding challenges with past performance across all our product lines. We are actively working to refine performance as well as take full advantage of tools in the native sdk to keep things light and efficient. We also have a team 90+ deep of testers with all manner of PC configs, so don't think we write for i9 KF chips and 4090's exclusively. 😉 As someone earlier said. The proof will be in the pudding, and this should taste great!

Hi Avsim! Steve from Ini here (Head of QA) While I can certainly understand the frustration with feeling like it's untested I can assure you that's not the case. We put a lot of time and passion into these projects and sometimes things slip by. This particular bug is worse than we initially thought and are working intensely to identify it and fully resolve it so it doesn't impact your enjoyment. The main issue we're up against is there isn't a steady pattern in when it fails. Earlier today I tried to reproduce it over 10 short segments of which only 3 failed. 70% success is still a poor margin for failure so we're combing through the code. I know that may be frustrating to hear since it's the weekend and you want to reliably operate the aircraft in the limited free time you may have but we don't want to keep you in the dark or think we're not doing or best to resolve it as quickly as we can. Thanks for your continued support and patience!