This is the modified setting demonstrated in the video:
Even with 100% vanilla game, the PIP scope has inaccuracy in the nametags:
The nametag positions are not (exactly) the same as unscoped nametag positions.
//int camID = m_PIPSightsComp.GetPIPCamera().GetCameraIndex(); // returns 0 for now (buge), TODO int camID = m_PIPSightsComp.GetPIPCameraIndex(); //camID = 8; data.m_vTagScreenPos = m_Workspace.ProjWorldToScreen( data.m_vTagWorldPos, m_World, camID);
The codeblock responsible for gettting the World To Screen pos in nametag code ^^^
ProjWorldToScreen
this seems to be the function providing inaccurate results when using pip scopes with variable settings, this is what has errors from my understanding.