richboy2307

Hi @UA124567 There have been changes implemented to the VNAV based on feedback provided by IRL operators of the type. The computed VNAV infamously imperfect and "quirky" on the A300 so it may be what you are noticing. However please submit specific examples of where you are facing this issue. In your report please include Full route including runways, SID/STAR/APP used CI, Weights (ZFW/Fuel), Cruise Alt Navdata source - Navigraph or Default Screenshots of your PFD/ND & MCDU F-PLN page & PROG PAGE (showing VDEV) in instances where you notice this issue This will allow us to reproduce the scenario and make refinements if it is not working as intended. Thanks!

Hi @markoxley No firm ETA but I wouldn't anticipate a release until next week at the latest. The team is out-of-office this weekend for the 'iniBuilds Summer Social' event. Thanks for your patience and understanding!

Just as mentioned, it is hard to say at this time. We do intend to support time accelerations, however the specifics of it, and what form it takes eventually can only discussed at a later time in future development updates. Thanks!

Hi @Dani18391 This is often a bug with the default navdata itself. However can you please list which routes / airways/waypoints you had these issues with? Example: On VHHH/25L N0486F330 OCEA2B OCEAN V3 ENVAR M750 TONGA TONG1B RCTP/23L I had issues entering OCEAN V3 ENVAR leg. Thanks!

Hi @orlando011124 While I can't speak for the fidelity of the "original" Asobo A320neo, the Cost Index certainly factors into all stages of flight in determining things like speed, rate of climb/descent and ultimately the time taken/fuel burned to complete the flight. Could you please share a video of this happening? Please note that for Managed mode to work properly, the INIT A/B pages need to be filled in with all the required data pertaining to Weights, Fuel on Board and CG. Additionally you should fill in the PERF pages as well for both TakeOff and Approach. Typically while you are in managed mode, all you need to do is dial in a lower altitude and PRESS IN the ALT SELECTOR KNOB to revert to a managed descent/climb mode. On descent, it will initially target 1000fpm vertical speed until it can intercept the calculated vertical profile and then descend accordingly on it. There are certainly improvements to be made with regards to the LNAV/VNAV which we have already incorporated into the A300, and intend to similarly work out for the A320Neo v2. However the currently implemented solution is still more than adequate and has been pretty good at observing constraints from experience. There may be rare instances of deviation, for which we appreciate screenshots/videos highlighting the issue which we can fix. So, a screenshot of scenarios where you're noticing this would be appreciated. Showing both the MCDU as well as the PFD/ND in all these instances. This is not an issue I've particularly seen in the many hours of flying this aircraft. Yes, the sequencing of next waypoint is a bit too early currently and this will be fixed in a future update to LNAV/VNAV. I'm not entirely certain what could have happened, but this is not an issue we can reproduce on our end. Nor has been reported by anyone yet in the many hours of testing internally, externally and finally publicly via the SU15 beta and since release. Thanks!

Hi @DeMBaSs The current focus is to release on PC first, same as with the A300. At later stages of development we'll also look into bringing these to Xbox. Ultimately it will come down to whether the hardware can still provide a great user experience that we'd like to provide via these complex simulations of the A350, and later A380. Thanks!

Hi @Kiwiviator As of right now, you need to point the iniManager directly to your community folder for the downloaded scenery to work automatically. If you install them to any external library/folder, then you will need to use a tool like MSFS Addon Linker to setup a symlink for them into your community folder. We will be adding the ability to define custom library/folder locations in the future with "V3" of the iniManager. For now however, having those sceneries in the community folder (directly via iniManager or through a symlink via MSFS Addon Linker) is the only way. Thanks!

Hi @Dani0100 Yes. As mentioned in the accompanying post, 3D Art Focus: Immersive Details & Dynamic Wear & Tear section, here: Also please take a look at the A350 Development FAQ here: Thanks!

Yes this Z-fighting issue is known and will be addressed next update. Thanks!

Hi @Adel Haiba That sounds like a WASM crash. Can you please share a screenshot of the page where it happens? DES FORECAST? Also is this happening consistently, every time you go to this page or only once in a while Thanks!

Thanks, will share with the team.

Hi @chaser911 There are no reported issue with steering on the A300, either internally or through the 50+ tester's systems it has gone through in testing. Common causes for steering issue include: Control Bindings Issues - Rudder/Steering Axis: Either of the two have been been bound to controls not intended. Please check your controller settings to ensure it is only assigned to buttons/hardware you want to control rudder/steering. Differential Thrust Input - In case you are using multiple axis to control each engine independently, please ensure that the thrust is being applied uniformally across both engines. Any difference in N1% between the engines can cause you to veer to the left/right. Differential Brake input - Brakes Axis/Buttons: Either of the two have been been bound to controls not intended. If you are using Rudder Pedals with toe brakes axis, please check their deadzones as erroneous triggering of brakes can also cause you to veer left/right. Noisy Control Inputs - Please check all your axis are properly calibrated and there is no "noise" in those controls that may be adding unintended control inputs. AI Assists - Please ensure all assists are disabled in the Assistance Options. These can cause conflicts with flight controls and AP functions on our planes. Thanks!

Hi @kekki The A320neo V2 does not use the sim's internal flight planner. That means any routes you type into the MCDU or import into it via simbrief are only being read by the aircraft. If you want to use the in-game ATC services, then you need to setup the plan in the World Map flight planner before the Flight. You can set this route manually, or import the plan from Simbrief (instructions: https://forum.navigraph.com/t/faq-exporting-simbrief-flight-plans-to-msfs/8112) Thanks!

Hi @castle59 Please ensure 'Bing Data World Graphics' and 'Photogrammetry' are enabled in the settings. This is an issue happens when the terrain data hasn't downloaded/updated for the area, hence the elevation of scenery objects such as lights may appear off. If you're on PC, you can also try to clear your rolling cache & scenery indexes. To clear you scenery index, see below: Thanks!

Re: Loss of ATC voices. Acknowledged bug, we're looking into it. Thanks!

Hi, We appreciate your enthusiasm for making the plane a better version of it self. However, nothing in the pipeline regarding this for now. As mentioned in the recent development deep-dive post accompanying the v1.1.2 update, we have IRL operators of the type on the team and are working with their professional insights with regards to the realism aspects of the product. In their assessment, Thanks!

There will be blog posts, FAQs along with a teaser trailer release.

You may need to add an exception to the tool. However you should contact Nool Aerosystems directly to check with them, as its their product. https://vdgs.nool.ee/contact/

Thanks for your detailed reports guys. I was able to reproduce the same issue. We'll look into it. Thanks!

Hi @markoxley Wow these caravaners are getting out of hand! 😅 But yes we're seeing this too. We anticipate an update to resolve any compatibility issues with the latest World Update. In the meanwhile if you notice any other anomalies, feel free to report. Thanks!

Hi, please ensure Photogrammetry is enabled as there may be terrain elevation issues without the right mesh data. In case you're still having an issue, please share a screenshot of the issue for issue tracking. Thanks!

Hi @Johnnyyang There are static aircraft models as part of the scenery. Due to encryption done on Marketplace, it isn't possible to configure this on the iniManager. However you could try to manually disable them by renaming the klax-scene-statics.bgl to klax-scene-statics.disabled. You will find these files in your Official Folder, under inibuilds-airport-klax-losangeles folder. If you're on PC and you purchase KLAX directly from the iniManager, then you can disable Statics via the configuration panel under 'My Products' section. Thanks!

Use your Pilot ID (Numbers only) in the EFB. Usernames will not work any longer, this was changed as some users had issues with simbrief connectivity because of the special characters in their usernames. Its not a separate slider. It is part of the SYSTEMS volume slider. Before warnings/callouts/alerts volume was not user configurable. Yes it has no bearing on functionality of the aircraft and is a by-product of the XML Interactions re-write for performance optimizations. Known issue as acknowledged here, and even replied on by you: Please avoid re-posting the same issues across multiple threads. Thanks!

Hi @village1111 Perhaps check with BATC support regarding this issue? There are multiple gate types on the scenery - Gate Small/Medium/Heavy and RAMP GA Small/Medium/Large defined already. These are also working for AI Traffic as well as for users via GSX. Thanks!