Irrlicht Engine

psyco001 wrote:Hi,
is there a way to solve this error:

Code: Select all

.\IrrNewt_src\ragdoll.cpp(193) : error C2440: 'Initialisierung': 'irr::core::list<T>::ConstIterator' can not be converted to 'irr::core::list<T>::Iterator' 

the other errors are all solved

const list<ISceneNode*>& children = BoneNode->getChildren();
	for (list<ISceneNode*>::ConstIterator it = children.begin(); it != children.end(); ++it) {

Donner wrote:Thanks, white tiger

Then another question: can I disable an object (IVehicleTire) or freeze it, so that the World don't calculate any physics for this object until I enable it? Or have I to destroy it and to recreate it?

stevend wrote:Yeah well i compiled irrNewt finally on my new development machine and threw the new dll into the mix and im having new problems, with your character controller i think!

On my P3 800 the character moves and walks fine, on my 3.3 ghz its choppy and almost dosen't move at all. not framerate, but actual character movement.

I would think it has something to do with framerate independence but i use the code from your example to do so:

Code: Select all

	
		//CHARACTER CONTROLLING
		core::vector3df rigell_rotation = node->getRotation();

		//STEP 1: ROTATING
		//make node rotation frame rate indipendent by multiply it by time elasped from last update
		float rotation_to_apply = rotation_speed * fact->p_world->getTimeElapsed();

		if(right) 
			rigell_rotation.Y+=rotation_to_apply;

		if(left) 
			rigell_rotation.Y-=rotation_to_apply;

		node->setRotation(rigell_rotation);

		//STEP 2: MOVING
		core::vector3df velocity = charcontrol->getVelocity();
		velocity.X=velocity.Z=0;

		if(up) //without FRI in function name the movement is not frame rate indipendent
			velocity += charcontrol->FRIgetDirectionPositionY(core::vector3df(rigell_speed,0,0));
		if(down)
			velocity += charcontrol->FRIgetDirectionPositionY(core::vector3df(-rigell_speed,0,0));

		charcontrol->setVelocity(velocity);

any ideas?

matgaw wrote:Hi white tiger! Glad to see you back!

matgaw wrote:I think I've found a bug in IrrNewt 0.4. When I add an object, which has some relative position to another, then the Newton body shows up in very different position than the node itself (it seems that Newton interprets the relative position as absolute one).

I almost managed to fix it, but my fix works only when scales of parent body and relative body are the same - if not, then body shows up in slightly wrong position.

Could you find out how to fix this bug, please? I'm not familiar with Irrlicht transformation matrixes...

analize999 wrote:But where does the newton game dynamics sdk? In the tiger's web just only has irrNewt SDK. Would you like to give me this link?