Context: in flight, devmode, when I hit compile or enter / exit the aircraft
Bug description:
Any time I switch from inside to outside on this project, all the external interactions are disabled, and I am unable to click any covers, doors or anything I am working with… when I check the behaviors tools, the disable interactions is checked for all of them.. I clear them, things work.. but if I go inside / outside again (SHIFT+C), all the interactions are disabled again and the checkbox is back to be set
This is driving me insane, I cannot work out why is doing this for this project, others are working fine.. what would trigger this so I can inspect posible causes?
Repro steps:
As explained above, just enter / exit the aircraft and the external interactions used by ASOBO_ET_COMMON_Cover_Interaction_And_Visibility_Template for covers or ASOBO_IT_Simple_Interaction_Template just get disabled with the checkbox..
I narrowed this down to navigation_graph_preflight.cfg, somehow, it is failing to attach pins to “model 3D names” (aka model name parameter) sending the coordinates of the pin wrong, and therefore the “volume” values go wrong, the system believe you never in front of the node to activate it.
When you edit the preflight graph with the aircraft editor, and you set the model name, you see immediately the node disappearing and moving away at least 60 feet from the aircraft, instead of showing where the attachment in the 3D is.
Only way to make it work so far it has been to use manual position locations instead of the model name, no idea what is going on..
The issue with navigation graph editor showing incorrect positions when using node name is known and possibly not the cause of the issue. To my knowledge, this is only an editor display issue and does not reflect the true position in the sim.
So this happens only with this specific aircraft? No other projects of your own or Asobo aircraft.
Do you have the same problem if your aircraft is loaded from Community instead of open in edition?
We are likely going to need a version of your package to identify the problem if only your aircraft demonstrate such behavior.
Happened with another too, looks like if the door-pin node is outside of the “volume” when the flight starts, the pin is not generated at all, and the nodes from that point onwards are not showing any nodes in the sim..
Only way around is to put the pin position manually via “positions” rather than the node name, or make the volume large enough so when the pilot spawn, is withing range..
I will try to replicate with the DA-62 sample and send the changes across so you guys can replicate with that one.. so far, if I put “manual” positions, my pins show.. if I use nodes.. they don’t.. unless my pilot spawns next to the door pin (inside the volume declared).
