Version: 1.28.00
Frequency: Consistently
Severity: Blocker
Dear SDK creators, I have a simple question for you… Is it possible to provide information about exporting models containing animations in a more understandable way for third-party developers?? I opened your example of the windsock model from the 2024 SDK. And in my opinion, you are completely misleading people who are trying to study and understand the features of SDK2024. Here’s a real example. I tried to export your model using a multi-exporter… You can see in my screenshot that the model is missing from the list of models available for export.
https://disk.yandex.ru/i/vNHcznpkRcv8VA
https://disk.yandex.ru/i/wW8QuS7wrEkrKA
https://disk.yandex.ru/i/1XGmIIkDOQ0q9g
I only see RIG. Why? Where are the models themselves? Lod 1.LOD2. and so on… Why do all windsock models contain baked animations and at the same time I see that there is an animation folder in the model folder and there is a single Windsock_animations.bin file in it?? At the same time, there are no references to this animation file in the xml file of the model. What’s it? Your indifference and inattention? You can provide information, in an expanded and detailed form, regarding animation export. I see that the simplest animated model of a flag that should be fluttering in the wind created for msfs2020 does not work in 2024. More precisely, I can’t export it using a multi-exporter. If I link the geometry of the model in the traditional way, the model simply does not appear in the list of those available for export. If the geometry of the model is not linked to the structure of animation points, it will be exported as static, without animation. Exporting via the old babylon works, but I can’t use it in 2024. When compiling, there is a conflict and a message that I am using outdated parameters.