Irrlicht Engine

Sorry if this sounds like a stupid question.

When I have a FPS camera, I can use the mouse to rotate the camera and look at my target. It feels very smooth. But on a system that has no mouse, I'd like to handle camera rotation with keys.

I got a few questions here:

1) I can catch my key event ...

Thanks, that's what I use. I use irrBullet wrapper. Otherwise, it would be a heck of a learning curve

Thanks for you guys to reply to my dumb newbie questions.

I'm learning to program with Irrlicht because I just want to have some fun on my Android device, nothing serious. But from the two-month learning experience (in the evening and weekend, that is), I found that learning a real physics engine ...

Thanks everyone for replying. I was trying to do collision detection using triangle selector because, well, this is how the Irrlicht examples introduce how collision detection is done. I learn to program with Irrlicht by studying the examples provided, and thought that these are best practice to do ...

I have created a floor, and cube. I want to add collision detection so that the cube would not fall through the floor. With the following code:


ISceneNode * cube = smgr->addCubeSceneNode();

IAnimatedMesh * movingPlane = smgr->addHillPlaneMesh("floor",
core::dimension2df(10, 10),
core ...

Thanks for explaining. So let me try to understand this.

Let's say I create 16 IAnimatedMeshSceneNode at the beginning, and stick them together by calling setPosition() for each of them, to form a 4x4 grid. Then as the camera move in one direction, I just stick more of it to the "front" of the ...

Sorry, newbie here. What does "tile it dynamically on the fly" means?

Thanks

Hi,

I create a floor plane with something like this:

SMaterial * material = new SMaterial();
material->AntiAliasing = EAAM_QUALITY | EAAM_LINE_SMOOTH | EAAM_POINT_SMOOTH;
material->Thickness = 1.0f;

IAnimatedMesh *movingPlane = smgr->addHillPlaneMesh("floor",
core::dimension2df(10, 10 ...

Ah thank you very much, you made my day. This is exactly the problem. I put a flag to check the initialization, and that' s it, no more infinite memory growth.

But then, another problem props up. After the game is stopped and resumed, the graphic is not right. It looks like there's no texture ...

I verified again with the example from the Irrlicht Android port, and it is the same code. I don't understand how memory use continues to grow like this.

Could someone give a hint on that?

Thanks

Paul

The draw loop is like this, which is copied from the tutorial:


void Java_com_test_TestIrrActivity_nativeDrawIteration( JNIEnv* env )
{
__android_log_print(ANDROID_LOG_INFO, "TestIrr", "nativeDrawIteration() called");

device->run();
if (counter == 0)
init();

driver->beginScene(true, true ...

I run my little test (as I have posted in another thread here ) on my Android, and after a while, I see that memory used by the program is growing forever.

I just let it run for 5 minutes or so, and the system shows that memory usage of this little test (which does almost nothing) is around 40MB ...

Aaahhhh, stupid me!

Thanks a lot for spotting my stupidity.

Sorry for cross-posting, I tried to create my first application on Android, and I got extremely low fps. I described my issues (and my codes) in this post here.

Could someone give me a hint on what's going on?

Thanks

Paul

And the size of the application is humongous! Even though I compiled Irrlicht Android and my test program with NDK_DEBUG = 0 , after the installation, Android shows that the size of my application is 30.58MB!!!

And the thing is, Android also shows the following flags on the program:

FLAG ...