Hello,
thanks to bugmans fix in the 2018.2.1 release animated jetways are working again OOTB without using icare38s patched nas file. Thats fine so far. What I realize now is a very sensitive collision detection causing an immediate plane crash (red message "Airframe structural..." and crash sound) when approaching a jetway.
This definitly is not related to the fix. I also see this when I place eg. a vehicle model with "enable-hot" activated with Nasals "put_model" function close to the aircraft. I don't remember having seen such a behaviour before.
Maybe the model collision detection in Flightgear did change in one of the latest releases, maybe due to a change in OSG. I have no idea how crash detection in FG works, but I guess it is based on some model collision detection in OSG.
Moving through static scenery buildings and aircraft is still possible, however.
The use case i used is: Start FG in KSFO, parkpos E60 with a 777-300 , autostarting, release parking brakes, throttle up a bit, move forward. It only takes a few seconds for crashing.
Back to my basic question: If we have such a sensitive collision detection, should we set flag "enable-hot" to false for animated jetways? Or am I mistaken here?
A local test on my system with a patched jetways.nas (line 231)
- Code: Select all
var model_path = model.getPath();
model.getNode("enable-hot", 1).setValue(0);
model.getNode("path", 1).setValue(path);
solved the issue successfully.
Best Regards
Thomas