By clever programming can you:

a. Do something like find the closest vertex on a model to a identified point, if so how do you do so (what vec_... command)?
b. Must go into your model editor, like the title suggests, to identify what vertex you want to mess with?

If you want more information to why I'm asking I can elaborate, any input would be appreciated, thanks.

You could use three "main" variables. one for the shortest distance, one for the number of the vertices with the shortest distance annd one for the maximum of vertics which you can get by "ent_vertices(entity)".
The following code is just an idea:
Code:

---

var dist_pos[3];

function vertex_closest(dist_pos)
{
  var i;
  var shortest;
  var ver_pos[3];
  var ver_number; //number of the closest vertex
  var max_vertex;
  
  i = 1;
  shortest = 500; //start distance
  max_vertex = ent_vertices(my);

  while(i <= max_vertex)
  {
    vec_for_vertex(ver_pos,my,i);
    if(vec_dist(ver_pos,dist_pos) < shortest)
    {  
      shortest = vec_dist(ver_pos,dist_pos);
      ver_number = i;
    }

    wait(1);
  }  

  return(ver_number); //return the number of the closest vertex
}

//Function calling:
function getshot_event()
{
  if(event_type == event_shoot)
  {
    my.hitvertex = vertex_closest(target);
  }
}

action example_act
{
  my.enable_shoot = on;
  my.event = getshot_event;
}

---

Brilliant, as usuall I failed to notice the variables seated under ent_... thanks once again for the help Thunder, it was exactly what I needed to know.

try a c_trace

its a bit easier than cycleing though every vertex and doing a distance check

@Grimber:
as stated in his signature he is using A5, so c_trace won't work here.
Would he be using A6, i definatly would have suggested c_trace with get_hitvertex.

EDIT:
One thing about my code:
I think you can remove the wait(1); at the end of the while loop, caus it becomes invalide after checking through all vertices.
So it would take like 2000 frames for a model with 2000 vertices, so it would take some time till all vertices are checked. But I think there is no other solution for those who still use A5.

i've never heard of this get_hitvertex!
i saw in the A6 SDK that there's the hitvertex variable, but the get_hitvertex flag is not defined...
does this work in the A6.31 or only in the A6.4beta?

thanks!
Filipe

@Filipe:
Nope it's in the A6.31.4 manual about 'c_trace':

Quote:

---

GET_HITVERTEX When called with GET_HITVERTEX and c_trace intersects an MDL that object's closest vertex number will be returned in HITVERTEX

---

Check the manual for further information.

strange, in the manual i have for the 6.31.4 i can't find anything about that. the page about c_trace is the same about trace.
i found it in the 6.4 manual, but in SDK the flag isn't defined.

Did you download the latest from the download page?
Thats the version I have and its mentioned there.

hm, i guess i didn't download the updated manual when i got the update, then.
i'll download it now.

thanks!