Vector3::Project

Isn't there some kind of Device.processvertices method (Device::ProcessVertices)?

Hi there BeanDog,
How are you doing?

The Problem
Vector3.Project function alternatives.

The Solution
There are a couple of things you could do if you are finding Vector3.Project to be slow which I highly doubt as these functions are optimized to deliver good performance.

1) You could opt to write your own projection function which you can do by transforming your vectors from object space to screen space by multiplying the world, view and projection matrices by each other and doing the math behind transforming your vectors by that resulting matrix.

2) You could also implement a timer, this has a few problems though as one main concern is precision as you will not be performing the project each frame and in the event that you are using it to check collision, picking etc.. you might miss a selection/picking/collision.

I hope this helps a bit, if you can maybe supply us with some stats we might advice you as to what tolerance would be correct.

PS: Are you sure it's the Vector3.Project that's the problem,
Make sure you are using a resource friendly loop, if you are using the Application.DoEvents() loop you might want to look over at Tom Miller's blog for a resource friendly loop.

Take care bud.

Armadon: Thanks for the extra-friendly reply, but I have to give Bosh rating++ for giving me exactly the answer I was looking for.

Thanks everyone!



~BenDilts( void );