Help from any idtech 4/TDM engine c++ coder

[HMart]

Hi guys I need help in two questions, not related to TDM so me posting here and would appreciate any help even if is only a small hint. 

1) Is how to access mesh vertices on model sprites, like the player icons in Doom 3?  I wanted that to put stuff at the corner vertices xyz positions of the "sprite" quad, in game, but failed. I only know how to do that through the model surface, using sprite->renderEntity->hModel->Surface(i) but for some reason, it always returns null, even thou the sprite/icon has a material and it renders! So you don't need a surface to render?

2) How to render a sprite above everything else? Like the player weapon that doesn't intersects anything. I looked at the weapon code but failed to see how the "weaponDepthHack" system works.  I also used the "sort     postProcess" in the material but it didn't do what i wanted.

And that's it, again any help appreciated.

Btw what I'm making right now, is a selection/frob effect based on quad "sprites" (like the Doom 3 player icons quad's) and the quad intersects the surface where the selected object is resting on. For example if the selected object is a book the selection quad intersects the table and cuts parts of the effect and that is not good.  For now I solved it by pushing the quad more away from the object, towards the player camera/view and it works more or less but there's still occasions that it intersects, there the second question.

[HMart]

Update on this, second question is solved and it was very basic, was expecting something more complicated but it was not, just set the sprite "weaponDepthHack" (despite the name works in any model) bool value to true and it works...  :Z 

Still didn't solved the first question but based on the second, perhaps I most be failing to see something basic again.  

[HMart]

Update 2 found why my sprites were not getting surfaces, I was using a nodraw material because I wanted the main sprite to be invisible but its geometry still accessible, (long story) but the code that creates surfaces, skips those mapped with invisible materials.