richboy2307

Thanks I'll report these. @SiRuS T Some liveries are missing the info, but not all. In case you don't see any information whatsoever, please try a reinstall.

Hi @Fab10, thanks for your report. Can you confirm are you using Navigraph or default navdata? Seems like the issue is that they are not assigned to a specific runway so do not load as intended. We'll look into this, thanks!

Thanks this is reported already. It only SYNCs the very first METAR's data, not the updated ones. Thanks!

Thanks, this is being worked on.

Yeah that was a backend issue still pushing out the older version. Version 1.1.1 HF1 should be the update that was *actually* supposed to go out with the fixes as listed in changelog 🙂

Hi, @cu206wrc & @Vee1rot8 can you please confirm if you are still having this issue as of 1.1.1 HF1 update?

Thanks for your post. People with real world experience on the type are consulted throughout the development process. Naturally, as the product matures and the userbase expands, so does the product's exposure to even more individuals with varying real-world experience on the type to those initially consulted. The feedback naturally also evolves into more specific items and we continue to improve the product on the basis of this feedback. We're sorry if improving this product and taking action on user bug reports has brought any inconvenience to you.

Hi, @Hardy614 sorry can you confirm what product and for what sim? If this is regarding an MSFS product, then the products are downloaded and installed via the iniManager: https://inibuilds.com/pages/inimanager-v2 The manager will install the products for you inside of your simulator's "Community" folder. Thanks!

Can you confirm you have Photogrammetry enabled in settings?

What are your scenery config options? Does this also happen with items like "Terminals - People", "Landside Cars" & "Animated Airtrain" disabled? Here is a video of me floating past in drone cam with no noticeable immediate change in FPS across this area. (Specs: AMD 5800x3D. RTX 3090, 32GB RAM) Maybe if you can share similar videos with the FPS Counter (enabled in via Developer Options > Debug Menu > Display FPS). Also try to clear your scenery indexes, reduce Terrain Level of Detail settings (100 or lower) and empty you rolling cache (if using any). For clearing scenery index: 2024-04-24 18-26-39.mp4

Hi @Michele TOGA button: Clickspot has been moved for the latest update. It is by a black screw next to ATHR button. Also covered here: https://youtu.be/N4cxNccH66U?t=1412 Simbrief Import: On the EFB please confirm you are using your Simbrief Username (Letters and numbers), and not your PilotID (Numbers only)? DHL Livery Problems: Please share screenshots of the problem you notice Thanks!

Hi, the KJFK is already optimized as much as it can be for Xbox. Are you noticing this issue on other airplanes like the default a320 as well?

Thanks I'll log these. The "Flap CTL Test" one will likely not be addressed as it is indeed a minor issue and not something affecting operation.

This can only be done on the GE variant in the maintenance menu. Not an option on the PW engines. Thanks!

Sorry for your bad experience. It would help us better if you gave more information of what you did prior to each instance of crash? What you have written here is telling us what happened *after* the crash. But in order to try to resolve the issue, we need more information on what you did just *before* it crashed. For example, did you change something on the MCDU? Did you change an autopilot mode, or changed some speed/heading/alt data on the FGCP? Was there a weather update just before? etc Thanks!

Thanks for your report and constructive criticism! But I believe you misunderstood what I wrote above. We do engage in extensive testing internally, and do use a combination of internal and external testers for the same. While I can't share specific metrics regarding the testing process, rest assured that we have been taking measures to improve quality control, and do engage in testing of our products even post-release. My hiring specifically as a tester is just one such example of the measures taken. I have personally completed over 28 flights of various lengths on the latest version alone without such CTD issues (Yes I know, I am just a sample size of 1, doesn't mean much.) Unfortunately, through this process of our internal and external testing across versions we have not till date been able to reproduce these issues. We will continue to fly our planes and test future iterations, but if we cannot experience the issue across any of the systems and persons involved in testing, then how are we to even understand the cause of the issue, let alone try to fix it? We fully appreciate our users are not compensated for testing. We also do not expect them to be testers of released versions of aircraft, but due to the circumstances above, and the nature of this issue we do not have a way forward without additional user cooperation from those affected. So to that end, thank you and everyone else who puts up their valuable personal time towards using and reporting problems with this product. 🙏 Thanks, this is just the kind of information we need in order to try and recreate the issue across systems.

Ah yes that could be it, because we could have sworn the runway centerline was fixed in the latest update (v1.0.2). 😅 I'll flag the team to take a look. Thanks for your report!

Hi @AMADI can you please confirm you are on the latest version (1.0.2)? If not please update and check again. Thanks!

Thanks, logged. Most of these should be addressed in a future version already.

Thanks this is known and will be fixed in future update.

@unhinged_aviator Ok so that's simply external airport ambience that is being heard there - It's under the 'system' sound channel on the EFB as it's tied to the main cargo door operation. We could possibly change it to 'environment' sound channel so you may turn it down on the ground whilst still enjoying other system sounds. I'll pass on the feedback, thanks!

You'll see a post in the Announcement section when there is anything new to share, thanks! https://forum.inibuilds.com/forum/7-inibuilds-announcements/

As for VNAV, yes that is still a WIP and will come as part of a larger improved VNAV system. For the Autothrottle, can you confirm when you notice this that the EFB throttle calibration page is still detecting throttle input? This sounds like an issue that was addressed in v1.1.1, wherein if you accidentally clicked the clickspot on the reverser's lever (on the pedestal) in-flight, it would limit the throttles to the reverser range. However because reverser's are locked in-flight, the throttle just appears "Locked" in idle position. The fix is to toggle reversers (via hardware button or by clicking the same clickspot). In v1.1.1 the clickspot of the reverser was disabled when airborne. Should only be clickable on the ground. Please confirm, thanks!

I have been a user of this product just like you long before working for IniBuilds. Yet I have not experienced random/mid-flight issues like this even once since Day 1. The only crashes I experienced were to do with MCDU (e.g. when DIR TO/Deleting a hold froze it). A lot of which have been addressed and continued to be worked upon. This is not to say the issues you mentioned do not exist. What I'm trying to illustrate is that it is rare and difficult to reproduce. For every one of you facing such issues, there are tens of others who are not. In the absence of being able to reproduce the issue ourselves or through our testers, we need more data to try and figure out what may be the cause. That is why we take these reports seriously, but need more detail and the cooperation of users to engage in troubleshooting on their end to help resolve. What can you do? Troubleshooting such as : Do a flight without any other addons, only the A300 in your community folder, to see if there are other addon conflicts. Delete the contents of your "work" folder after a fresh re-install to ensure no corrupted data Make these flights in default "White" or "Inibuilds House" liveries to eliminate any "bad" livery files causing conflict And when you do encounter the issue, report with: Screenshots/Videos of the failed systems or anomalies you notice Write-up of the things you did just prior to the crash (e.g. what you clicked, what you interacted with, what control inputs you gave etc) Route information & navdata used (E.g. Navigraph data - KLAX/24R LADYJ4 CSTRO DCT DUCKE DCT LMT DCT MOXEE TMBRS2 KPDX/28L ) Any extra things you noticed just before to the crash (e.g. momentary sim-freeze, abrupt winds change, sudden weather update etc.) All this allows us to try and recreate your flight to see if we face the same issues or find common conditions across reports to try and nail the issue. Your patience and understanding is greatly appreciated. Thanks!

Hi, please install the product via the SIMMARKET App (https://secure.simmarket.com/app.php) After installation of the app, login to your SIMMARKET account on top right, then navigate to "My Downloads", find the A300-600R and select INSTALL. Thanks!