Irrlicht Engine

Hi everyone, I'm not working on IPhysics any more (I've handed the project over to Rapchik), but there is something I should really point out: It seems a lot of people are experiencing a lot of pain trying to compile IPhysics using the static lib. I would strongly advise you not to bother and just c...

Hiya all, First of all, many many thanks to RapchikProgrammer for his great work on upgrading IPhysics. Sorry I haven't been around much - new job has taken up all of my programming brainspace... Anyway, hopefully this weekend I'll try and do an official release incorporating all RapchikProgrammer's...

Ah yes - sorry for all this confusion about the .a library. Basically, the one on my website is for IPhysics 1.1, so it won't work with the current release - I really should take it down. If you are using an IDE that doesn't play well with .lib libraries built with Visual C++, then for now either co...

Hi all, glad this is still of interest. Sorry there have been no updates for a while - I've just started a new job and am just generally knackered at the end of the day. However, I have made some progress on character controllers and it well get done, slowly but surely. About debug rendering, the Ne...

Sorry all for lack of updates recently - my laptop broke 3 weeks ago, but should get it back any day now. I have started implementing character control, so shouldn't be long now. Don't worry, IPhysics is very much alive!

@y2hstar: You need to make the world size bigger - use setWorldSize(). @Baiame: There might be a library mismatch between the .a and the changes I made about a week ago, as I can't compile the .a files myself. (Well, I just need to install Code::Blocks) - I would recommend just using IPhysics from s...

Whoah! Scratch that - laptop has just exploded. Currently posting on my whizzy new mobile. At least i'm not in japan any more, where repairs take upwards of a month. Get well soon cards welcome at the usual address

@The Pie God: IPhysics should work quite happily on OSX - it's just a set of wrapper classes in C++, nothing platform specific there. I don't know if the precompiled libraries would work though (the .lib was made with MS Visual C++ - wouldn't bet on it), so probably the best way is just to include t...

@jaytea: Fixed - there was a muddle in my meshbuffer loop. Many thanks for sending me that. The download page now hosts the updated version. For anyone else having trouble using IPhysics with a mesh with multiple mesh buffers, it should be fixed now.

@jaytea, klikmaster: I really need to have a look at the meshes you're trying to load - if you could post a link to the mesh or email it to me that would be great. I have a couple of theories, but without being able to replicate the problem myself it's very difficult for me to fix it. @3ddev: I inte...

@raven_coda: Ah, that's not quite what carBodyOffset is for. Basically, you need your mesh to be built in your modeller exactly as you want it to come out in the engine. So for your monster truck, if you want it to be higher up, you need to do that in your modeller and then export it again at the ri...

@3ddev: I'm not sure about the Irrlicht SVN problems as I don't use it myself. Regarding the IPhysics linking problems, when you say you've included IPhysics.h, have you set the the include directory in Dev C++ to the IPhysics include directory? It looks like it's including IPhysics.h but can't find...

@ComputerWhiz: No .NET support planned - sorry.

One thought about example 2 going really slow and freezing: try using the UM_EVERY_FRAME update mode. (Add this line somewhere: physics.setUpdateMode(UM_EVERY_FRAME) ) - let me know if that helps.

@alogon: to get your own event receiver working, you still need to tell Irrlicht to use it, either by passing it to createDevice() or using setEventReceiver(). Also, make sure you've got the function signuature exactly the same - if you put onEvent instead of OnEvent or something like that it'll jus...

Hiya all, sorry - been crazy busy these last few days with job interviews. @klikmaster: The scene node part shouldn't be the problem; that's only used to set the scale and store for any callbacks. Looking at the code you posted earlier, I understand that it crashes when you try to create the physics...