Jump to content

Dummy points createColPolygon


GhostXoP

Recommended Posts

I remember I've read something about dummy points in a topic about 3D model rendering. It's something like the points of a mesh, though I'm not sure 'cause it's been like a year or so.

You are right as far as i know, because mesh is to create polygons easier.

I tried learning about dummy points, but found nothing tho.

Edited by Guest
Link to comment
I remember I've read something about dummy points in a topic about 3D model rendering. It's something like the points of a mesh, though I'm not sure 'cause it's been like a year or so.

You are right as far as i know, because mesh is to create polygons easier.

Well, from what I've learned a mesh is a set of polygons that creates an "image" of something. E.g. a vehicle that we see in games is just a set of polygons linked, with textures.

Anyway, doesn't matter. Just wanted to tell that if these dummy points are what I think then you won't even notice anything.

Link to comment

Yes, but its easier to create a vehicle with lines and turn them into a polygon then making a vehicle from a polygon. Tho from a few polygons you have to attach them and then link with textures or else you can see your vehicle pure white or grey

Link to comment
Yes, but its easier to create a vehicle with lines and turn them into a polygon then making a vehicle from a polygon. Tho from a few polygons you have to attach them and then link with textures or else you can see your vehicle pure white or grey

Nop, model files in games ever use polygons, the game engine then interpretes the model files and load everything and create a mesh which you can then use - http://en.wikipedia.org/wiki/3D_modeling#Representation | http://en.wikipedia.org/wiki/Polygon_mesh.

Anyway, let's stop with this off-topic conversation :P

Link to comment

If you look at the source code: http://code.google.com/searchframe#KdIe ... .com&l=210

You'll see that the first two arguments are used for the position of the colshape - the x and y values returned from getElementPosition. This position would ideally be the centre of the polygon (I'm not sure why we don't calculate that automatically?), as the only real purpose is so that we can do a cheap collision check to see if you're near the colshape, before we do a more expensive check against each side of the polygon.

Link to comment

Its fine that you don't, i've never actually needed the center points to a colshape unless its for my car locking resource or zombie ai spawn/process manager, even then i just use the positions of the ped the colshape is attached to. I wouldn't calculate it automatically and only use process time like that for more important things.

As for the original problem, i set it to the first fx1 fy1 coord's

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...