alx5
-
Posts
10 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Posts posted by alx5
-
-
Hello,
The v1.0.4. update has been pushed on Friday, three days ago now. During that time, iniBuilds own liveries were updated to work with the model changes even though it was the weekend. I am wondering what exactly holds the update to the paint kit back. The updated model was used for the iniManager liveries, so it was already made.
1.0.4 hit 3rd party livery creators quite hard, as our liveries didn't show up as intended, although they worked fine in previous A350 versions. Fixing the issues is out of control for most of us, as severe changes on part of the model names need to be made. Being a livery creator myself, I feel completely abandoned by iniBuilds.
In my opinion, internal model changes of this kind shouldn't happen on a release version of an addon. This belongs in beta testing. The winglet update is a rather small change; this can't be the cause of this mess with the model.
Honestly, I am a bit disappointed now by the way this update was pushed without updating the paint kit in a reasonable time after the actual aircraft add-on.
Side note on the model stuff itself:
In MSFS2020, including actual models (gltf + bin + xml files), which merge with the base model, aren't even necessary unless creators add custom 3D meshes to the plane, e.g. the cabin.
Most developers like PMDG, Fenix, TFDi, and even iniBuilds with the A300 set up their base liveries/models to include every mesh/decal area needed to create liveries. E.g. the PMDG 777 liveries only need a model folder with a model.cfg referring to the base model. The A350 is different here. The wing registration decal area is only available in the models included with the paintkit, both iniBuilds House and the white livery doesn't seem to have it, that's why the whole model merging from custom-made livery with the base model is even necessary.
If iniBuilds could just include the wing reg decal to their own liveries coming with the A350 by default this would decrease maintenance for 3rd party livery creators on future model updates as well as decrease maintenance on the actual paint kit as including models to the livery isn't needed anymore. A simple model.cfg could get the correct model on every livery automatically even after larger model changes as in 1.0.4.
The above-mentioned is mostly true for MSFS2024; if the default liveries come with every mesh/decal area needed (right now the wing registration decal area is missing there as well), creators could just copy the existing model from the included white livery to use with their own livery.
-
2
-
-
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.
-
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.
-
On 3/10/2025 at 2:50 PM, Swisspilot1986 said:
Does anyone know why the entire cabin is modelled in MSFS2024 only?
What I have heard is performance, can't believe is because of the 2024 SDK, the model files are pretty much the same and the cabin is a pretty easy model with no animation etc.
The A350 has got three different seat variants, ini added the business seat in 6 different variations, economy comes in 9 variations, premium economy in 3 different variations, all depending on their position inside the cabin. Each variation needs 3 sets of textures. All of them need to be loaded into the sim. In 2020 you see the basic cabin with floor, lavatories and galleys, all those seats implemented would probably kill performance for a larger majority of users. -
16 hours ago, David Cherrie said:
Are you getting the pink missing texture in 2024 on the wing?
Nope, probably still using the 1.00 model
-
Hi,
with the paintkit released the A350_Wing_Registration_ALBD seems to be missing information. The model included with the paintkit doesn't come with a mesh for the nose/wing registration. The wireframe for the nose gear is helpful there, the wing registration area doesn't come with one. I also would like to know where exactly the wing reg area is placed it is a bit guessing atm.
With version 1.01. the wing registration isn't shown in sim even though it is added to the textures +json updated.
-
2 hours ago, sp196 said:
Hi all,
Just discovered that the model seems missing sensors at the front cockpit windows. As you can see the real one has 3 sensors just down below the wipers. Thanks
You can add those via EFB at least in 2024 they are named AOA sensors
A350-900 with no wheels on first load.
in Modelling & Texturing
Posted
I get it something similar as well when quitting a flight with the A350. Back inside the aircraft/livery selection the currently selected livery is shown gear up quite regular. Changing to another livery solves it every time.