I have installed V1.1.3 of the A300-600 in both MSFS2020 and MSFS2024 using iniManager 2.4.1. No problems in 2020, but the plane is not visible to select in 2024, despite being installed to my custom Community folder.

Hello. I have installed V1.1.3 to the FS2024. Airplane is visible but liveries installed via iNiApp Manager are not visible and does not possible to choose them. Also it is not possible to go back to the sim menu after flight loading with the A300-600F in the anly airports. Sim come to the freezing.

Hi,

Apologies for delay in response. Please note below items:

On 12/15/2024 at 9:13 PM, Aleksey said:

Liveries installed via iNiApp Manager are not visible and does not possible to choose them

The liveries are not cross-compatible across versions due differences in model structure.

• Liveries made for FS2020 will work for the Compatible Edition on either sim FS20/24. These liveries will not work on the Premium Edition (FS24).
• Liveries made for Premium Edition (FS24) will only work with that specific edition in FS24 due to the new 'modular simobject' structure used. These liveries will not work on the Compatible Edition (FS20/24)

If you are downloading the liveries from the iniManager, please make sure you have installed the appropriate livery for the version of A300 you're using.

On 12/15/2024 at 9:13 PM, Aleksey said:

Also it is not possible to go back to the sim menu after flight loading with the A300-600F in the anly airports. Sim come to the freezing.

This is an acknowledged core sim issue. As mentioned in the launch forum post:

https://forum.inibuilds.com/topic/24363-lets-talk-inibuilds-a300-600r-airliner-updates-for-msfs2024-msfs2020/

Quote

PLEASE NOTE - We have discovered a current core sim issue relating to networking that prevents users  from fully closing the simulator after completion of a flight. 
While this does not affect anything related to loading or using the aircraft either offline or with Multiplayer/Online networks, you will not be able to return to the menu UI without closing the simulator process via the task manager.

Asobo is aware and have possibly fixed this already internally, however it is pending a public release: https://devsupport.flightsimulator.com/t/couldn-de-init-wasm-with-fsnetworkhttprequestget/11969/6

 

On 12/15/2024 at 7:08 PM, PeterDa said:

No problems in 2020, but the plane is not visible to select in 2024, despite being installed to my custom Community folder.

Can you please confirm that you see the ``inibuilds-aircraft-a300-600`` folder inside your custom community folder? Also ensure this custom community folder is being read as active by the sim. You can test by adding any other addon to this custom location and confirm its showing up in the sim.

Thanks!