c++ problem

[cassius]

THe code below stops the camera getting hidden behind walls in a 3rd person game.Its from an aggror c++ tutorial and works fine with walls. The problem comes in hilly terrain where it thinks a hill is a wall and makes my character disappear and re appear all the time.

Anyoe help???

EDIT thegame is ok without this code. but I just wondered.

 

 

 

 

 

 

 

 

PickInfo pick;

if (world->Pick(fpsPivot->GetPosition(), tpsPivot->GetPosition(), pick, 0, true))

{

//Store distance

float distance = fpsPivot->GetPosition().DistanceToPoint(pick.position);

printf((String(distance) + "\n").c_str());

 

//If the tps distance is to small, we switch to FPS view

if (distance < minCamOffset)

{

camera->SetPosition(fpsPivot->GetPosition());

}

else

{

camera->SetPosition(pick.position);

}

}

else

{

camera->SetPosition(tpsPivot->GetPosition());

/

[AggrorJorn]

Have you tried specifying a collisiontype so terrain gets ignored?

[cassius]

no. how do I do that?

[T0X1N]

The collision type ("collisiontype") in the Pick function is the 7th parameter. The default is set to pick all objects. You would set the "collisiontype" parameter to something that does not pick the terrain.

 

bool Pick(const Vec3& p0, const Vec3& p1, Pick& pick, float radius = 0.0, bool closest=false, bool recursive=false, int collisiontype=0)

 

http://www.leadwerks.com/werkspace/page/api-reference/_/command-reference/collision-r778

 

Unfortunately, I am not sure what collision type is set for terrain as I have not worked with terrain much.

[cassius]

I have five parameters. If I add two more I get syntax error.

What should that line look like?

 

Thanks.

[Brutile]

World pick is a bit different:

 

Pick(const Vec3& p0, const Vec3& p1, PickInfo& pickinfo, float radius=0.0, bool closest=false, int collisiontype=0)

[cassius]

not sure what value to put in last parameter. I tried 0 to 4. Choosing 4 worked for hilly terrain but then it could not detect walls either.

[Brutile]

The collisiontype refers to Collision types. So for example, if you use Collision.Scene, it will pick everything except Scene. Collision.Debris will only pick Scene and Prop, etc.

[cassius]

Thanks everyone for explanations.

[cassius]

Got it working with a 7 as the last parameter. Works with any "Scene" object.

Still don't know why but that's ok.

[macklebee]

You set the pick's collision as Collision.LineOfSight which according to this diagram will only collide with 'Collision.Scene' collision types.

 

Here is the list of the inherent collision types and responses:

List of inherent types:

Collision.Prop = 1

Collision.Scene = 2

Collision.Character = 3

Collision.Trigger = 4

Collision.Debris = 5

Collision.Projectile = 6

Collision.LineOfSight = 7

 

List of possible responses:

Collision.None = 0

Collision.Collide = 1

Collision.Trigger = 4

 

With the following warning from Josh concerning using the constants and not the numerical values: "You really should stick to using the named constants. Technically, the values of these are allowed to change at any time, without breaking the spec."

[cassius]

I was putting 6, thinking that counting began at 0.In c++ the syntax is " Collision::LineOfSight " it seems.

Thanks Mac.