Irrlicht Engine

Hi Iyad.
Knowing how to use the debugger is an essential skill.
If you're using MS Visual C++ 2008, try the following:

Go to build->Configuration manager
Select at Active solution configuration:'Debug'
At Project context: select 'Debug' under Configuration
Hit 'Close'

Then, goto Debug menu and ...

copy/paste from one of my routines:
FireNode.SmokePlums .PlumColor=90;
FireNode.SmokePlums .SmokePlum->setColor(video::SColor(255,FireNode.SmokePlums .PlumColor,
FireNode.SmokePlums .PlumColor,FireNode.SmokePlums .PlumColor));
FireNode.SmokePlums .SmokePlum->setMaterialFlag(video::EMF_LIGHTING ...

I have the solution for you.
Take CuteAlien serious. He is right.

Turns out I'm wrong indeed.
The scaling only helps a little to compensate for the rounding errors.

I have fixed the whole problem by keeping the players plane at (0,Altitude,0) all the time, and use the

driver->setTransform (video::ETS_WORLD, PlayerTranslation);

for the terrain rendering, and ...

Hi, I have been fighting with this problem for some time, and have not found any solution on this forum that fixed it.

I examined what happens with the coordinates of all different scenenodes (for example, all the instruments and controls in my cockpit are different scenenodes) and unsurprisingly ...

Good. I see this guy also found out that .x is not so hot.... I'm so satisfied with b3d. No more crappy unexplainable stuff happening in my scenes.

Did you try to install the patch ? The download is on the same page. That patch fixed the same problem for me.

Finally I tried another model format, downloaded the plugins for B3d fromhttp://www.onigirl.com/pipeline/ and all the weird problems are solved. And it supports bones and helpers as well. No more .x files for me ! Give it a shot, it might suit your needs as well.

<deleted my ow blabla>

Checking the sourcecode for the importer to see what couses my problem

I'm having the same extremely anoying problems.
I'm trying basicly the same.

My system loads a .x file into a IAnimatedMeshSceneNode , using 3DsMax point helpers to define connection positions.
When I have the 'connector skeleton ' loaded, I'm hooking up IMeshSceneNodes to the connector positions ...

Holy *(, that's a fast response
Please note I edited some lines.

CurrentAngle_converted=CurrentAngle+180; // set your angle system to range from 0-360
GoalAngle_converted=GoalAngle+180; // same for the goal angle

now, if the currentangle is -179 ( 1, converted )
and the goal angle is 179, ( 359, converted )

DeltaAngleRotateRight=fabs(CurrentAngle_converted ...

Nice task. Ugly, but might work:
Start rotating A, keep track of the x position of the target atom until it reaches to wanted x position using getposition() on the target atom mesh, then stop rotating the parent ( A ).

So far for one angle, if you want to rotate the whole thing so the picked atom ...

Not sure it is actually causing the problem, but in class B you define:
string* description;

In the constructor of class B, you use:
description=new description[n] -> this is bad.. same names

I wonder what the compiler does with that...

Try to rename the new string (pointer) array, for example ...

Etcaptor, this is a brilliant piece of software !!
Thanks !

By the way I needed to download cc3260mt.dll.

http://www.dll-files.com/dllindex/dll-f ... l?cc3260mt