yeah it is 0 or 1. because i'm using float I wanted to do the most obvious check. I've had trouble in the past on gpu drivers with this being finicky about perfect equality.
I think the pos data stored by the clip plane tool doesn't have to precisely match the m_plane anymore. At init, I forget why I commented this out (and it may just be because I needed an epsilon)....