Irrlicht Engine

This is a killer project, it was a snap to throw together a demo to play with. Is there a good way to make an object a 'child' of another, much the way parent/children work in Irrlicht? For example, if I wanted a character object to board a boat, could I make it the child of the boat, so that any fo...

Here's wishing this forum had some kind of "thank" or "like" feature cool project RdR!

Check the projects forum, there is a decal manager project there. You could place tire tracks as decals, then remove the oldest as the vehicle moves forward.

Hey Ducky, I've noticed my memory usage shoots up when using the mesh combiner, even with meshes that have a lot of repeated textures. It looks like the project is saving copies of the same texture over and over in the bottom of PackTextures(): irr::core::stringc textureName = "PackedTexture&qu...

Very cool project. One note, scaling does not scale the leaf textures, which ends up looking weird. You have to set the Scale property of each billboard in the BillboardGroupSceneNode, like this: void CBillboardGroupSceneNode::UpdateBillboardSizes(irr::core::dimension2df _size) {         for ( u32 i...

Actually I think my problem is in this line: inputMesh->getMeshBuffer(i)->getMaterial().setTexture(0, toSet); It looks like I'm getting a const Material, then trying to use a setter. I don't think the mesh's texture pointer is getting updated, so when it goes to render it's pointing off into some pl...

Thanks for the help all! This is what I've come up with (mostly cribbed off of other posts on the forum): void RescaleTexture(irr::scene::IMesh* inputMesh, irr::core::dimension2di targetSize) {         video::IVideoDriver* vidDriver = smgr->getVideoDriver();           for (int i = 0; i < inputMesh->...

I'm noticing as I load more and more meshes into my app that I'm eating up a lot more memory than I intended; looking over the meshes I've created, it looks like I'm using too many high-resolution images for textures. Rather than go through every mesh I've created and scale down the textures, I'm ho...

could you assign the driver->getTexture call to an object, set a breakpoint, and inspect the object after the call?

Could you post a minimal block of code that reproduces the issue?

Two emitters that have identical properties except lifetime?

I would suggest using an eventing system such that player::update just raises a "player x died" event with attached info (killer, etc) then recievers can catch and interpret that event - the killfeed would scroll itself to display he info, etc.

just add something like vector3df target = camera->getPosition(); target.Y = 0; camera->setPosition(target); to your while (device->run()) loop MfG Scarabol Well that's what I'm trying now, but the camera ends up getting stuck in the geometry. I think what happens is the camera moves a bit in the Y...

Hi all, I'm working on a project where I want to lock an FPScamera on a single axis (I want no vertical movement). Turning off the vert movement bool in the constructor works to a point, but I've found that the camera can still move vertically via the collision system (for example, walking up a ramp...

get and setPosition() return co-ords relative to the node's parent - do the player node and the spawn node both have the same parent? Have you tried using the absolute positions?

Thanks, that worked great! I also had to set emissive to black and normalize normals, but hey whatever works!