pose.GetSegmentEnergyScore for out-of-range segment crashes client
|Opened on:||Tuesday, February 18, 2020 - 16:45|
|Last modified:||Sunday, April 26, 2020 - 19:43|
As Pikamander2 describes, functions like current.GetSegmentEnergyScore crash the client if the segment number specified is out of range. The poses recentbest, creditbest, and absolutebest seem to have the same issue, but I haven't exhaustively tested them.
current.GetSegmentEnergyScore ( 0 ) current.GetSegmentEnergyScore ( 999 )
both cause a crash.
The function should instead throw an error, terminating the recipe.
This happens on 20191029-32048a6a12-win_x86-devprev.