IniSteve

Hi Mike, I'm sure you've seen a number of the issues resolved in the past few updates, but specifically wanted to follow up to confirm the emergency descent logic is resolved and working as intended. Thanks again for your reports.

Hi. This is resolved as of 1.0.5.

Hi. The model has changed, therefore, these liveries will need to be fixed by the respective creator. Please reach out to them directly.

Hi. The sound you're hearing is that of the nosewheel strut fully extending as the aircraft lifts off the ground.

Hi Tommy, This behaviour is correct to the real aircraft. Please reference the following graphic from the FCOM to better understand the limitations of this system. You can enter 12' and 59" to approximate the local time in Auckland. For values larger than that just inverse from zulu time.

Hi, as Erti mentioned, failure randomization is coming in a follow on update

Hi. Under USER EXPERIENCE in the assistance options menu, turn off "aerodynamic visualization"

Hi. We'll look into this and see what our side pulls. Thanks!

Hi TFG, Rather than turn to robots who aren't on our team, I invite you to check out the many streamers and youtube creators all over the internet who have showcased it's capability over the last 12+ hours. Hopefully they shed enough light.

The freezing on exit is something we're aware of and have communicated (quite exhaustively) over the past 24 hours since release. It relates to networking and will affect apps like FSUIPC/vpilot/Simbrief/etc. Essentially, anything that uses simconnect or the networking api. We are trying to find a workaround but in the mean time the only way to fully exit the sim is to kill the process via task manager. While this may not be the most elegant solution, we felt it was a better alternative to limiting the ability to use these applications with the A300.

All of us at IniBuilds have looked forward to Microsoft Flight Simulator 2024 with excitement and anticipation. With its enhanced visual fidelity, improved aerodynamic simulation, and the promise of an immersive flying experience supplemented by an unprecedented level of detail, the sim represents a significant leap forward in the world of flight simulation. While the title is jam-packed with countless new and improved features, we also want to keep you informed about some current issues that may affect your experience. The below is a non-exhaustive list of things to look out for while the platform grows and evolves to full maturity. Known Issues and Important Considerations with Flight Simulator 2024 User Interface: There may be some inconsistencies on the UI with products transferred from the previous sim. This can manifest as incorrect or missing thumbnails, liveries appearing out of order, and statistics displaying inaccurate or no data at all. External Lighting: Light sources and their associated effects may look over exposed under some circumstances. While we have made some edits to the default values to mitigate this effect in certain environmental conditions the "splash" of the light may appear very intense. Aircraft Registration: These may not display correctly on cockpit placards and may show the incorrect registration for custom liveries. This is a limitation of the simulator where a random registration is assigned to the aircraft at the start of every flight and the user cannot remove that registration entirely. Bright Displays & Lighting: Some emissive textures in the cockpit (Digital Displays, Annunciators, Panel lighting etc) can appear excessively bright due to the 'Eye Adaption' of the new simulator. This may be particularly notable around dawn and dusk, which is when automatic light shift will occur in the cockpit. While this is a neat effect it can cause an abrupt change in the brightness of the aforementioned items around those times. Daytime Lighting Visibility: Exterior and interior lights may seem too dim during daylight hours even though the emissive textures themselves are operational. This is a current sim limitation as tuning them for daytime visibility can lead to overexposure at night so a balance has to be struck. Enroute Map Flicker: Currently, there is a known core bug with the way js maps are read by the sim. The mapping client we and many other developers use (leaflet) is not currently compatible with the sim sdk. While we and Asobo work towards a solution, it's best to either avoid using the enroute map or understand it will flicker at times. (We have found the flickering does begin to subside after a few minutes over the duration of a flight) Disappearing Sounds: Occasionally, the simulator may eliminate certain sounds to conserve memory and enhance performance. This can lead to situations where sounds that were functioning correctly at the beginning of a flight then suddenly disappear until the scenario is exited. We have observed this in the A300, particularly with regards to the sounds of overhead switches and ambient bleed. Our team is actively working on this issue, and an update will be provided once we are confident a solution has been achieved System & Video Memory Usage: Overall RAM and VRAM consumption tends to be higher in the simulator compared to MSFS 2020. While we have made every effort to optimize VRAM usage, you may experience stutters or low frame rates, particularly when the system is unable to allocate the desired capacity. Computers with higher amounts of RAM and VRAM may mitigate some of these issues, but instances may still randomly occur. Low Resolution Textures: When switching views there may be instances where you briefly encounter lower than expected texture resolution on displays or surfaces. The sim appears to have a buffer when it comes to loading these back, where it doesn't reload full quality texture detail levels all at once. This will cause the textures to appear low-res for approximately 2-3 seconds (or more, when you have lower-end specs) to load back in the full-resolution textures. Display Clocks: We have identified various time-related issues within the simulator that can lead to inconsistencies with the clock. It’s possible that the UTC time shown on the aircraft's clock reflects your local PC time instead of the simulator's time. This can also result in discrepancies during scenarios that involve time acceleration. TCAS Alerts: Users may receive false Traffic Advisory alerts in some instances due to a sim issue that leads to erroneous targets being shown of the user aircraft. Users may change the TCAS mode to TA or STBY to silence the alerts for the moment. 3D Model Level Of Detail (LOD): The implementation of the LOD system in FS2024 can sometimes lead to unexpectedly low LODs being called at the wrong time or objects being culled at short distances. While this does not happen frequently, it's key to ensure you can reproduce the issue you're encountering, as it could be a once-off encounter as a result of this.

Hi. This isn't a "problem" as much as it is an expected byproduct of frame generation. The animation is coded to a fixed time cycle and since FG is dynamically compensating with your frametime (which is not fixed) it will inevitably have skips.

Hi John, Sometimes the back end has a hiccup and the order doesn't complete despite the app giving the impression it did. Your hunch it hasn't is likely correct but the first thing I would do is check with your payment source and see if a charge was in fact processed. If not, the order did not complete. If for some reason you do see a double charge, submit a ticket here https://inibuilds.com/pages/contact under the "direct support" link and we'll sort you out. Thanks!

Hi all. FS2024 has brought with it new and better engine and fuel management simulation which requires a more thought into how one operates their aircraft. For the T-33 ensure when you are advancing the throttle, it's being done in a slow and controlled manner. If you move it too quickly, the engine will surge and stall as per the real thing.

Hi WW! We've outlines the plan of attack for our catalogue here - Hope that clears up any confusion. Thanks.