Irrlicht Engine

so anyone know how to fix this design issue ?

If lights move map's shadows moves too. Since HL² and Doom 3 there is dynamic shadows on BSP.

for collision in game industry they using 2 mesh collision mesh and the one that rendered. since level mesh usually very complex with large amount of vertex. it's better to make second mesh with less ...

this is the code

void amhEventReceiver::generateCollision(ISceneNode* n, IMetaTriangleSelector* meta )
{
if (n->getType() == ESNT_OCT_TREE){
IAttributes* attribs = device->getFileSystem()->createEmptyAttributes();
if (attribs) {// get the mesh name out
n->serializeAttributes(attribs ...

Physix is now the property of NVidia

Hi,

Int the specialFX tutorial there is this :


IAnimatedMeshSceneNode* anode = 0;
anode->addShadowVolumeSceneNode();
smgr->setShadowColor(video::SColor(220,0,0,0));


but I'm using Octtree with this tutorial by ChristianClavet.
The collision function use ISceneNode instead of ...

Yes it is. If I add offset it don't resolve the problem.

It works better now, I change things like this :

Adding an empty node, child of the ship, wich is used as camera's target.

target = smgr->addSceneNode("empty", node);
target->setPosition(vector3df(0.0f,0.0f,100.0f));

and using it in the ...

it don't works for me.

When I rotatte the camera with the mouse it's ok, but when I move it with the keyboard the traget don't follow.

updateCamera is called every frame in the main loop

#include "amhEventReceiver.h"
#include <fstream>
#include <string>

// on event
bool amhEventReceiver ...

it's weird.

If I use KEY_LSHIFT instead of KEY_SPACE nothing happens, but if I use KEY_V it's ok.

does KEY_LSHIFT and KEY_SPACE correctly handled by irrlicht ?

EDIT ---------------

I found why !

this is because :

case EGET_BUTTON_CLICKED:
if(id == 101){
if(smgr->loadScene("media/maps/test01 ...

well, I restart from the begining.

First I try to move the camera. Everything is OK except when I release the space barr. It's used to move the camera up but when I release it the camera is replaced at origin.

I add the camera with addCameraSceneNode

then I check the keys and I move it with this ...

Weird things happens.

The camera moves but not the target and the camera rotate in weird directions.

Here is my class :


#include "amhEventReceiver.h"
#include <fstream>
#include <string>

f32 MoveSpeed = 1.0f;
f32 RotateSpeed = PI/180;
f32 JumpSpeed = MoveSpeed;
vector3df cameraOffset(0.0f, 0 ...

OK, that's expected. Camera targets are absolute, not relative, so if you want a camera to keep looking in the same direction while it's moving, you'll have to keep updating its target.

what do you mean by "updating" ?
Should I call some irrlicht function or should I build it myself and add all ...

It's ok now, but as you say, rogerborg, the target don't move.

can you post the code that attaches the camera to its parent node?

do you mean :

device->getSceneManager()->addCameraSceneNode(Game->player);

Is the camera being attached to a skinned mesh? (things are a bit different if it is)
-wyrmmage

thsi is my class (basic at this time):

#ifndef ...

Thanks, but I wont spend my time to trasnlate, rotate and scale every single node at every frame. Especially if there is an offset.

Irrlicht's doc says that the camera move with it's parent, not that I must mouve it miself.

Hi,

I create a camera attached to it's parent, a scenenode.
When I move the scene node the camera don't follow :


device->getSceneManager()->addCameraSceneNode(Game->player);


and


core::vector3df v = Game->player->getPosition();
if(keys[KEY_KEY_Z]){v.X += 1.0f;}
if(keys[KEY_KEY_S]){v.X -= 1 ...