Irrlicht Engine

You're using "createOctTreeTriangleSelector()" and "addOctreeSceneNode()". Are you using the most up-to-date version of Irrlicht? Because it's now
"createOctreeTriangleSelector()", etc. (no double tT) Maybe there was a bug fix since. IDK.

Anyway I found some readings that tells to avoid Non-const references in constructors (without explaining why :/)
Hmm, I don't know about mingw specifically, but perhaps they are saying that --"conceptually" speaking-- constructors should just take external data for copying and not alter it.

I ...

Also, I believe addCameraSceneNodeFPS() adds a camera that already has an FPS animator on it.

In each loop, I was creating a new static text box, in a different position.

Well, Sydney got a bit slow so you could see it.

Was that because Irrlicht was handling thousands of GUI elements, or it was really because of the performance of the engine?
I think you've guessed right. Generally ...

using mesh manipulator does not work with animated mesh I did not know that :shock: Hmmm :?

The efficient way to do this is to adjust the orientation thro rotation, and then just simply add the required rotation.
Unfortunately, "adding" or accumulating rotations is not just a simple matter of ...

If you can't rotate the meshes in the mesh editing software, you could try getting a mesh manipulator from the scene manager and using its transform() method to permanently have the meshes rotated -90 degrees around the X-axis before you even start. That way, when you go to store their rotations ...

I don't know how you're doing your scaling or what bizarre results you get so I can only guess. The matrix rotation and scaling happen around the cube's local origin before translation (or, you could say it spins and scales around its absolute position after positioning it) but the unit cube is not ...

look into:

vector3df::getHorizontalAngle()
Get the rotations that would make a (0,0,1) direction vector point in the same direction as this direction vector.

It should return a "rotation" vector which can be applied to the "cuboid" node with:

cuboid->setRotation( /here'sTheReturnValueOf ...

One thing is:

double dt = then - now; /*should at some point, update the 'then' value, like so:*/ then = now;

otherwise, the " then - now value" (i.e. the "dt" value) quickly gets HUGE!! and no puny little "x" value will have a visible effect.

Also, shouldn't it be " now - then " to find the ...

The "logic" behind this behavior is that every scene node has its own transformation (position, rotation, scaling) and that that transformation is referred to as its "Relative Transformation". When drawAll() is called, the relative transformation will be offset from the transformation of its parent ...

Yes, as CuteAlien pointed out, you have your last two parameters swapped when you call "getSceneNodeAndCollisionPointFromRay()". Also, each node that you test against has to have a triangle selector set for it or that method ("getSceneNodeAndCollisionPointFromRay()") won't work for that node.

Use ...

cpp Code: Select all
u32 curTime = device->getTimer()->getTime();
world.deltaTime =curTime-world.time;
world.time = curTime;



You are defining your time variables, one after the other. This defeats the purpose. What you want to do is take the time from the current frame and subtract the time ...

Wut? Sorry if that was sloppy. I mentioned the getColorFormat() and you're right, there's a protected member which checks the desired format, not the actual one given, if I understand correctly.

I probably mentioned too much at once, but that's still just a start of what you gotta know to write to ...

//Handling Game Input

bool CQuake3EventHandler::OnEvent(const SEvent& eve)
{
/// blah, etc.
.
.
.
}

if(eve.EventType==EET_MOUSE_INPUT_EVENT&&eve.MouseInput.Event==EMIE_LMOUSE_LEFT_UP) /*<------Here is the error!*/


It would appear that your if statement is outside of the brackets of ANY ...

Basically, your last post loops through i and ii but doesn't do anything to change x or y. So, you keep setting the same pixel, possibly incorectly (see below).

Also, y should be multiplied by the pitch and x should be multiplied by the number-of-bytes-per-pixel when using u8 pointers to pixels ...