Vatsim Model Matching
-
Myself and my friend play together on vatsim but his aircraft's engine animation, ailerons, doors etc etc mimics my plane. His engines will be running but shows off on my side. Basically everything I do mimics on his plane when I look at him. Would be cool if it could work independently.
-
I had one other report of this through my sound designer last week (perhaps that was you?). I'm not aware of anything on the developer side that could affect this, and I'm a little surprised that it would not have been brought to my attention years ago with how many of my users fly online. I'll see what I can dig up about this right now, but please let me know if you learn anything about it, or any other aircraft that are affected by it.
-
Some aircraft behave as I described, some do not. For instance the freeware WB Sim C152 is, I believe, coded so that I can see when my friend opens his side window or has his sun visors down. Other aircarft copies the user's movements so I guess it something to do with the aircraft.cfg but im just guessing from what ive read on chatgpt. And no it was not me this is the first time im reporting this. Hope you can figure it out mate
-
Some info from chat gpt for clarification:
Subject
New!
Click to editIn multiplayer, visual items like doors, windows, and sun shades on the Black Square Baron are not independently visible per aircraft. What other players see is either mirrored from their own aircraft or not shown at all, rather than the actual state of the remote aircraft.
This contrasts with aircraft like the WBSim / Asobo C152, where these visuals do sync correctly in multiplayer.
The reason appears to be that the Baron’s visual animations are driven by local L / WASM logic, which MSFS does not replicate over multiplayer. Aircraft that sync correctly drive visual-only animations from networked A via Asobo ModelBehavior templates (e.g. A:INTERACTIVE POINTS STATE bitfields).
Possible fix: decouple purely visual animations (doors, windows, sun shades) from system logic and drive them using network-replicated Asobo variables, as done in the default / WBSim C152. This would improve multiplayer immersion without affecting systems fidelity.
-
That's a surprisingly reasonable answer from ChatGPT. Thanks for sharing. While I don't know if its blanket statement about L:Vars is true, that would certainly explain the situation. Unfortunately without those L:Var driven animations, I wouldn't be able to implement 95% of the custom features my aircraft have. For instance, no wind force on the doors, or windows fluttering, or hydraulic landing gear, or wingflex, and the entire engine starting simulation. I feel bad that's the case with multiplayer, but if I couldn't override the default logic, then there would be no Black Square. I will explore this in greater detail before publishing my next round of updates, however.
