SubassemblyTargetInfo.SetTargets/CorridorExtensions.AddTargetInfoToRegion seems to set the correct targets, but when taking a look at the corridor model the elevations appear to be off by quite a bit.
Removing the target and re-adding the same target manually fixes the corridor model. When the same targets are set again with Dynamo nodes the model weirdness returns.
Attached (contents of zip file):
Subdivision4.dwg - test drawing
A4-Set Targets 2.dyn - Dynamo graph (elevation targeting portions set in orange groups)
ACM data.json - some data required by A4-Set Targets 2.dyn
Subdivision4 after script run.dwg - result after running script
unexpected elevation target behavior.mkv - video showing the odd model behaviour and how it's repaired by removing the elevation profile target and re-adding it manually.
elevation target issue.zip
SubassemblyTargetInfo.SetTargets/CorridorExtensions.AddTargetInfoToRegion seems to set the correct targets, but when taking a look at the corridor model the elevations appear to be off by quite a bit.
Removing the target and re-adding the same target manually fixes the corridor model. When the same targets are set again with Dynamo nodes the model weirdness returns.
Attached (contents of zip file):