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?
3 Likes