The scripting command selectionVectorDirAndUp is reporting a "no point in selection x" error to the .rpt file being run on a known and existing selection, even when it properly returns the selections vectors.
This is identical behavior to what selectionPosition was doing before 2.12 (reported here: https://feedback.bistudio.com/T167265)
Run the following code to get a known selection and produce its Dir and Up vectors:
_sel = (player selectionNames 1) #28;
player selectionVectorDirAndUp [_sel,1];
Even if this returns an appropriate array of vectors, it will also log an error to the .rpt file for the session.
This bug was noticed after the 2.12 update didn't entirely fix the .rpt file bloat which my mod was creating (it relies on selectionPosition and selectionVectorDirAndUp being called at least once per frame to function). It does not seem to break anything that this logging is occurring, but as with T167265, it seems an excessive report.