chinjh

Would prefer the pitot+engine cover be disabled by default and it being a toggle option on the OIS instead of forcing us to walkaround at every start but this also calls for asobo to change the spawning behavior as well.

Latest GSX version 3.3.8 has some issues. Expect to use the sim and any aircrafts without gsx for the time being.

Updated Paintkit is out Hopefully painters can sort it out quick.

It has been almost 24hours since 1.0.4 came out and still no paintkit update and im sitting with multiple third party repaints that are either invisible or bugged out sharklets, even some of the official ones from INImanager have some minor errors that may or may not be fixed by unconventional workaround. If this the case i would've prefer they delayed this sharklet model update or if the other unrelated fixes are in need of quick update publishing to defer this specific thing to the next patch. At the very least the updated paintkit should come out first ahead of the actual patch or in tandem.

I noticed some issues with approach pitch. 188t gross weight. Flap 3 with 5knot tailwind -700fpm ils approach but the pitch is around 2.5degree. Flaring the plane i only need to pitch it to 3degree and it was a greaser. Meanwhile i am seeing on youtube it seems the a350 actually needs more flaring sometimes 6-7 degrees on config 3. But on ini doing that the plane will climb or either float.

This bug involving WF VHHH has been there since the days of the A300 release. Neither Asobo, ini nor the scenery maker wants to fix them each pointing fingers at each other. Only workaround is to use navigraph but that also comes with occasional missing waypoints(that usually gets addressed by navigraph quickly) but at least better than the default that has you plotting waypoints into the infinite side of the earth and costing half of your frame rates. VHHH Hong Kong SIDs/Stars Failures

Try looking at the ecam section and confirm that the clr button is not illuminated. Its the one i circled here. I noticed when double click the side stick red button too quickly would also cause the autopilot disconnect ecam warning that wont go off until it is cleared via inputting "clr" button.

This is somewhat fixed for anyone testing out MSFS SU1 Beta trial.

Its under MS/Asobo's turf now. Whatever fix has to be up to them to decide whether to push the update or not. This has been a major issue with the default aircrafts since MSFS 2020 which i recall simple patches can take months with the A310. Luckily the A350 and A300 are not in that kind of state.

Looks like they're saying its an MS/Asobo issue.

This is not really an issue with third party devs but more towards MS/Asobo's policy on encryption and file structure that prevents proper paintkit sharing. Request for the Unencryption and Full Downloadability of Default Aircraft in MSFS 2024 Topic discussion has been posted on asobo forum weeks ago. I suggest all users to vote on that topic to tell them that we're not happy with the current state of things.

This is logged by Asobo. But not sure if INI or Asobo has a fix and whether it will be incorporated in the upcoming sim update on 12 december.

Just noticed the flap 1+f position are in the wrong position with the flap trailing not sufficiently extending. Also missing flap sound when extending and retracting. This problem is currently extended to all the A330 family including the beluga XL. Also flap transition speeds seems to be slow. From the video above going from flap Config 1+f to 2 only takes 3 seconds but in the sim it took 8 seconds. It seems to be the same when going from Config 2 to 3 and 3 to 4 they mostly take between 3 to 4 seconds each flap detent. Hope this is logged for some sort of fix. Microsoft Flight Simulator 2024 2024.12.02 - 12.10.09.01.mp4 Microsoft Flight Simulator 2024 2024.12.02 - 12.10.28.02.mp4

I just noticed repeatedly since 2 days ago i cant end my flight or go into the main menu as it will result in MSFS being in jammed state or unresponsive with the only workaround is to force terminate the app. Relaunching the sim and selecting any of the streamed liveries almost highly guarantee a crashed sim desktop even on configure page. Meanwhile those that are downloaded from flightsim.appears to be working. For now i have find a little workaround but its kind of a nuisance to keep doing this now. Steps 1) identify which livery has been causing crashing Example A330-300GE Malaysia repaint always caused crash when selected. 2) Launch MSFS 2024 on the main menu select option>configure>Select A330-200. 3) Ensure A330-200 RR default Airbus livery is selected and make sure it loads the aircraft completely 4) Then select variants and select other variants like the VIP streamed liveries and select any of it and wait for the plane to load. 5) Now go back to variant that you want and res-elect the problematic livery that has been causing crashes. It should technically load without causing a crash to desktop scenario 6) if it loads now you can load up free flight. Note if end flight causes the sim to jammed its quite likely reselecting the very same livery would cause guaranteed CTD and you would have to repeat the steps above. What i am suspecting end flight causes the streamed downloaded package files associated with that livery to become corrupted in someway does not help when you prompt task manager to force terminate MSFS2024. Doing the supposed workaround steps above seems to tell MSFS 2024 to redownload the associated package files for the broken livery but it would only work if another livery or variant gets correctly loaded first.

V1 callout is equipped on most A330 out there.