Irrlicht Engine

Try it with a texture that is not a solid color. When it is selected, no lighting is calculated (as part of the tutorial), so you won't see any depth.

EDIT: I just tested this and was able to reproduce exactly the phenomenon you described.

I just went through this myself. Try adding Make sure you apply the material before calling this.

@Master Absolutely! Just add water.

Which version of irrlicht are you using? It looks like that function was added in version 1.3

what is "MAX_CONCEIVABLE_DISTANCE_FROM_GROUND"?


That would be the length of the line you are using to check where the ground is. If the line is 10 units long, then you won't "find" the ground if you are further than 10 units away. Basically, you just want to replace that with a really high ...

I'm not familiar enough with the Irrlicht API to write the actual code, but hopefully you can get the idea from this pseudocode:


//Create a line going straight down from the camera
line.start = line.end = camera->getPosition();
line.end.y -= MAX_CONCEIVABLE_DISTANCE_FROM_GROUND;

//See where it ...

then make debuginput global (global variables are declared outside of any function)

First the selector is initialized:

scene::ITriangleSelector* selector = 0;

if (q3node)
{
q3node->setPosition(core::vector3df(-1350,-130,-1400));

selector = smgr->createOctTreeTriangleSelector(q3levelmesh->getMesh(0), q3node, 128);
q3node->setTriangleSelector(selector);
}


Then it is ...

What is a singleton?

Here is how it is outlined in Design Patterns by Gamma, Helm, Johnson, and Vlissides (the "Gang of Four"):


class GameInfo {
public:
static GameInfo* Instance();
virtual void DoSomething();
//Public members here
protected:
GameInfo();
//Protected members here
private ...

You can't declare a variable inside a code block and then use it outside of the block (it's out of scope). Think about it this way: What if the condition of the if statement is false? Declare the variable before you enter the if block.

This should be on the tutorial page because there are samples for other physics engines but I didn't see one for Bullet.

I think this has already been covered but I just wanted to clarify that the up-vector is not handled by the fpscamera to suit your needs.

I played around with it a bit and it looks like moving your mouse up rotates the camera in the original "up" direction (what would now be "left" or something ...

maybe you can add properties under the logic tab (f4) (in Blender) and export the data using a python script. I don't know if this is possible or not but I just thought I'd throw it out there.

Do a search for "Singelton pattern". Basically, you will probably only ever want one instance of your gamedata and can guarantee this programatically and not worry about when it is instantiated.

Basically, you'll want a public static Instance() function and a private static pointer to the instance ...

I got the error about MyEventHandler being an abstract class as well. I changed


//EventReceiver.h
virtual bool OnEvent(SEvent event)


to


virtual bool OnEvent(const SEvent& event)


Which seemed to fix the problem.

I also had to remove the line:


//3rdPersonCam.cpp
case 'e': driverType ...