Since WU5 the models of IVAO B737, B747 and A321 aren’t visible anymore. The other models of IVAO work fine. I tried to find out if there was an difference in the cfg-files etc, but can’t find an solution to this problem.
Maybe the three named models (gltf) are outdated or contain something wrong.
Is there somebody who has a clou and is able to fix it. Or is it something Asobo has to fix, because they were working before WU5
I don’t have a specific IVAO fix, but here’s an alternative mod that you can consider. Since this will sit on the official folder, it will be used at the lowest level. So if you have an IVAO model working, your IVAO traffic will work. But otherwise, if it doesn’t have any matching or if it has any issue, it will fallback to use this model instead.
Thanks, I already did that. I only want to have my B737’s and B747’s back. Must be something in the files what isn’t compatible with MSFS WU6. Maybe recompile the gltf-files.
Don’t IVAO have some support team that can help? If it is a compatibility issue with WU6, wouldn’t everyone using IVAO be affected? In that case, someone should’ve reported it and someone should be working on it, right?
The models for these 3 aircraft are having a error withing the node hierarchy. The game finds a node that was already created and will not load the model.
It’s a problem withing the gltf model file and can only be fixed by IVAO. The question is if the game suddenly has a false positive and is seeing an error that didn’t matter before.
The problem is known by ivao and MTL devs are working on a fix. Yesterday a new version of Altitude v1.10.5b came out but hasn’t solved the problem yet. Check ivao’s forums for news.
It was reported right after WU6 and IVAO devs are aware of the issue. Unfortunately they are not very fast providing updates and they son’t communicate to users at all.
I’m not sure if I’m experiencing a variation of the same thing, but I installed IVAO 2 days ago and have run several test flights from airports on their list, ATL and LAX. After I set up the flight in MSFS and spawn the aircraft, for my test an A320neo, and click the desktop icon for IVAO Pilot Core I get the usual “allow the app” to make changes. I look around the spawned aircraft and the traffic at other gates is the same as without IVAO running. I think don’t think there is an installation problem but the install location requires “Select MSFS content directory (shall contain Community and Offical folder). The example shows F:\Flight Simulator 2020” as the “home” directory, but I have never found a file by that name after owning MSFS 2020 for more than a year. The closest to it is MicrosoftFlightSimulator_8wek…etc alphanumeric. That’s where the the IVAO installer placed the installation, and Community and Official are under that file. I tried to delete IVAO to reinstall it, but the Content Manager shows it on the list of Addons, but says “not installed.” If I click on it and open the check mark it doesn’t give me any “Uninstall” option. There is an “uninstall exe” file in the IVAO file but if I click on it, it asks for permission to make changes and I answer yes, and get a NSIS error box that says “Error launching installer.” I tried the Windows 10 list of apps but IVAO is not listed. I’m stuck with IVAO not adding any AI aircraft to my airports but it won’t allow me to uninstall and try again. Does anyone have any suggestions? Is this part of this glitch that others have described that started after Su6; I installed IVAO after Su6. Will appreciate any thoughts on this.
Some random dude proved the IVAO devs wrong, and fixed, what could not have been fixed 
check this link from flightsim.to. It seems someone has solved the issue. Downloaded it last night, but didn’t try it yet. Will do so, now
sorry, only realized after i send my post, that yours was exactly the same. My apologies
I did it, but the A321 does not appear in VATSIM, its invisible! What can I do?
Peter
Works like a charm also for live traffic. First IVAO, then the live traffic mod from simflight.to, then this fix.
If Asobo makes live traffic as it once worked again then i am happy.
What a joke this is… I literally answer to every post that is created on the IVAO forums. I’m not a Blender Developer, and there’s only one of us working on MSFS ON HIS FREE TIME.
Our team member tried to have a look into the files but all aircraft are converted using the same procedure, so we were unable to understand why some of them worked and some didn’t. Just so we are clear here: by we, I mean only one person
How exactly have we been proven wrong?
I’ve said in the forums, “We think the problem originates from the update. Although we are working on it, there isn’t much we can do.”
Naturally, if something works before an update, and then suddenly doesn’t. It’s more likely that the update has broken things.
This is what we thought the problem was at first. Still It’s not proven, although there’s a hotfix. We cannot know if that hotfix will keep working in the next update. Documentation is very poor on AI side, and we are volunteers for our network.
It’s very disrespectful of people to say such things to ivao staff members and go use our material on some other network.
Anyways,
We have received the feedback from @SquawkDirty and will continue working on the files. Then we’ll release it. Altitude updates are not connected with MTL/CSL.
I always appreciate criticism and feedback. Messages on Invisible IVAO aircraft after WU6 topic by @FewerCorn2992 helped us investigate some issues. Also some other comments too. But straight up blaming us for it… then saying we are slow and don’t communicate… I don’t think so
Thanks to everyone that tried to help with feedback and forum posts.
As you stated by yourself: “There isn’t much we can do about it”… and that has been proven wrong, by some guy, who invested 2hrs of his freetime as well, and found a very obvious error in the model structure.
And in regards of SKD documentation, it clearly states, that objects with only 1 LOD will be deleted as soon as they only occupy less than 5% of screen size. As none of those models does contain any additional LOD, this is another example of neglecting Asobo instructions.
Don’t get me wrong, I highly appreciate the effort for creating and implementing such models in order to have a more realistic experience. But blaming Asobo for errors done by yourself (or the corresponding developer) is just a cheap way out.
I don’t know about that statement. The game itself gives an error message telling you what the problem is. It clearly talks about a node duplicate. You don’t need any documentation for that. It’s possible that before the MSFS update the game has skipped / ignored errors and loaded the model anyway. After the update the game became more strict and starts to ignore models with errors.
I would say with me finding the error message and @SquawkDirty fixing it we are talking about 3 hours for the fix.
Guys, could we please all stop arguing about who is to blame and who isn‘t. It is not the fault of anyone at IVAO as I highly doubt anyone who has created those models is still working on them. They are legacy models (edited of course, and converted, imported, exported several times). This error in the model most likely was originating from a faulty export algorithm somewhere in the process, possibly years ago. It never was a problem, then it was, and now it is fixed. I got that by looking at the plain text version of the files rather than importing them and inspecting them - just because I don’t know anything about 3D models. Finding that was not „simple“ or „trivial“, it was more of a lucky stumbling upon a weird detail. I have to say that IVAO is not to blame for not finding anything, because using an importer that does not have such a Limitation might even make it impossible to find the mistake in a 3D modelling software as the duplicate node is ignored on import. We don’t know - and honestly we should not care. Please, let’s all stop fighting and ■■■■■■■■ and return to flying, is that possible?
I totally agree.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.