iniBuilds A350 v1.0.3 with v1.0.1 Liveries - Plane Invisible

[Electr0]

Hi All,

I have the v1.0.3 of the iniBuilds A350 in MSFS 2020.

In the iniManager all the liveries for the MSFS2020 version of the plane are labelled as v1.0.1

When I load into the game with any livery from there, the entire plane is invisible, both from an internal and external view. If I use the default iniBuild or "all white" livery that is bundeled with the plane, everything loads in fine.

This occurs for both the -900 and -1000 versions.

I have tried unintalling and reinstalling the "custom" liveries as well as the plane. Neither of these things fixed the issue.

Is anyone else having the same problem?

[dhiggs92]

same here

[1980Merc]

Same for me also.

[PierreFSX]

Same for me also, 

[Top27]

Inibuilds, Please redo 1.0.2 and develop newer version in the background

[Ivan Pato]

Add me to the list, same issues since the most recent update.

[ErickPinedo]

Same problem

[Timonier6900]

5 hours ago, Electr0 said:

Hi All,

I have the v1.0.3 of the iniBuilds A350 in MSFS 2020.

In the iniManager all the liveries for the MSFS2020 version of the plane are labelled as v1.0.1

When I load into the game with any livery from there, the entire plane is invisible, both from an internal and external view. If I use the default iniBuild or "all white" livery that is bundeled with the plane, everything loads in fine.

This occurs for both the -900 and -1000 versions.

I have tried unintalling and reinstalling the "custom" liveries as well as the plane. Neither of these things fixed the issue.

Is anyone else having the same problem?

Latest version of this a/c is 1.0.4 

[ceoflight]

same issue. As me msfs2020, the original liveries(white one and iniBuilds paint) was correctly shown both internal and external. From iniManager liveries(JAL A359) and flightsim.to have visible issue nevertheless liveries update from iniManager. 

[dhiggs92]

I've managed to make the plane visible again, you need to Nuke any a350 files off of your PC, a regular uninstall in the ini manager on it's own doesn't seem to fix it.

The following worked for me:
 

• Remove all liveries from the community folder
• uninstall the plane through the ini Manager
• delete the A350 folder under the following path:
  AppData\Roaming\Microsoft Flight Simulator\Packages (The easy way to get to AppData is to do 'win+R' and then type %appdata% in the text box)
• Reinstall via the ini manager
• Launch MSFS - at this point the plane should be visible.
• Close MSFS reinstall liveries as you please
  Bare in mind I am using the Steam version of MSFS 2020 and your file location may be slightly different if you're using the windows store version for example.

Hope this helps 🙂

 

Edited March 15 by dhiggs92

[dhiggs92]

.

 

Edited March 15 by dhiggs92

[ErickPinedo]

7 hours ago, dhiggs92 said:

I've managed to make the plane visible again, you need to Nuke any a350 files off of your PC, a regular uninstall in the ini manager on it's own doesn't seem to fix it.

The following worked for me:
 

• Remove all liveries from the community folder
• uninstall the plane through the ini Manager
• delete the A350 folder under the following path:
  AppData\Roaming\Microsoft Flight Simulator\Packages (The easy way to get to AppData is to do 'win+R' and then type %appdata% in the text box)
• Reinstall via the ini manager
• Launch MSFS - at this point the plane should be visible.
• Close MSFS reinstall liveries as you please
  Bare in mind I am using the Steam version of MSFS 2020 and your file location may be slightly different if you're using the windows store version for example.

Hope this helps 🙂

 

Didnt work bruh.

[こばと 笠森]

9 hours ago, dhiggs92 said:

I've managed to make the plane visible again, you need to Nuke any a350 files off of your PC, a regular uninstall in the ini manager on it's own doesn't seem to fix it.

The following worked for me:
 

• Remove all liveries from the community folder
• uninstall the plane through the ini Manager
• delete the A350 folder under the following path:
  AppData\Roaming\Microsoft Flight Simulator\Packages (The easy way to get to AppData is to do 'win+R' and then type %appdata% in the text box)
• Reinstall via the ini manager
• Launch MSFS - at this point the plane should be visible.
• Close MSFS reinstall liveries as you please
  Bare in mind I am using the Steam version of MSFS 2020 and your file location may be slightly different if you're using the windows store version for example.

Hope this helps 🙂

 

That's not gonna work for 3rd party liveries.

They modified the model in this version, so you need to apply new model if you're painting by sub-model method with Blender, and small modify with model.cfg if you painting with old traditional way (Photoshop and DDS files).

 

I don't think inibuilds has mentioned this at all.

[Transair]

I've got all liveries working now (with 1.0.4. and updates to Inibuild liveries) EXCEPT Finnair OH-LWK.  (LWA is fine, but I installed not updated that one).

[alx5]

You can use the liveries from the iniManager fine. 

3rd party liveries uploaded/updated prior to Friday March 14th won't work no matter how often you try to reinstall them. Depending on the age of those uploads you see the exterior without VC or no exterior with interior or nothing at all.

Inibuids updated their liveries even during weeking, but doesn't seem to be able to fix the paintkit for v1.0.4. The new model from the paintkit is needed to get liveries from fs.to back working.

 

So if you want to use a livery from fs.to, you don't need to download it rn, subscribe to the livery so you get a notification once it got updated. The fix is rather simply done, so the update should be possible shortly after ini dropped the updated paintkit.

Edited March 16 by alx5

[chinjh]

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.

[hkrammer]

They f.cked up all third party liveries with this half-baked update, without an updated Paintkit or at least some words, how to fix the problems. My before high opinion of the good work of iniBuilds has dropped down now rapidly, this is big shit, sorry!

[haza2]

1 hour ago, hkrammer said:

They f.cked up all third party liveries with this half-baked update, without an updated Paintkit or at least some words, how to fix the problems. My before high opinion of the good work of iniBuilds has dropped down now rapidly, this is big shit, sorry!

This is not constructive, accurate or helpful. Anymore and you will be removed from the forum.

[haza2]

On 3/15/2025 at 10:22 AM, Electr0 said:

Hi All,

I have the v1.0.3 of the iniBuilds A350 in MSFS 2020.

In the iniManager all the liveries for the MSFS2020 version of the plane are labelled as v1.0.1

When I load into the game with any livery from there, the entire plane is invisible, both from an internal and external view. If I use the default iniBuild or "all white" livery that is bundeled with the plane, everything loads in fine.

This occurs for both the -900 and -1000 versions.

I have tried unintalling and reinstalling the "custom" liveries as well as the plane. Neither of these things fixed the issue.

Is anyone else having the same problem?

Have you not upgraded to v1.04?

[mseder]

Same here with version 1.0.4
Was lucky to save the previous version 1.0.3. Had it restored and everything was back to normal.

Edited March 16 by mseder

[alx5]

6 hours ago, hkrammer said:

They f.cked up all third party liveries with this half-baked update, without an updated Paintkit or at least some words, how to fix the problems. My before high opinion of the good work of iniBuilds has dropped down now rapidly, this is big shit, sorry!

Well the only real problem currently with 3rd party liveries (mine included) is the model file outdated. This need to be fixed by iniBuilds themselves. The new winglet can already be implemented, the models are all in the sim. You see some updated liveries on fs.to but they seem to use inis white livery model as a base. This one is lacking the wing registration decal. So creators would need to update the livery twice, most of us don't want to do this. 

[hkrammer]

i found a temporary solution in another thread here in the forum, from user giumanz sorry, don't know how to place a link to this), for MSFS 2020, when you have no cockpit, but outside of plane ok.

he wrote:

Hi, a temporary solution is to replace two lines in the [models] entry inside the "model.cfg" file from:

[models]
normal=A35K_EXT.xml
interior=..\..\inibuilds-aircraft-a350-900\model.900\A35K_INT.xml

to:

[models]
normal=..\..\inibuilds-aircraft-a350-900\model.white\A35K_EXT.xml
interior=..\..\inibuilds-aircraft-a350-900\model.interior\A35K_INT.xml

This while waiting for other solutions.

This worked for me.

best regards

[Quantum_MIKU]

On 3/17/2025 at 1:43 AM, hkrammer said:

i found a temporary solution in another thread here in the forum, from user giumanz sorry, don't know how to place a link to this), for MSFS 2020, when you have no cockpit, but outside of plane ok.

he wrote:

Hi, a temporary solution is to replace two lines in the [models] entry inside the "model.cfg" file from:

[models]
normal=A35K_EXT.xml
interior=..\..\inibuilds-aircraft-a350-900\model.900\A35K_INT.xml

to:

[models]
normal=..\..\inibuilds-aircraft-a350-900\model.white\A35K_EXT.xml
interior=..\..\inibuilds-aircraft-a350-900\model.interior\A35K_INT.xml

This while waiting for other solutions.

This worked for me.

best regards

Thanks, this method is useful for me. The only disadvantage is the sharklets turn to black

[chinjh]

Updated Paintkit is out 

Hopefully painters can sort it out quick.

 

[hkrammer]

They have forgotten, to update the model.cfg in the 1.0.2 paintkit files. So if you want a cockpit in Msfs2020 Version, you have to change model.900 to model.interior as described above…