Irrlicht Engine

The source code is nicely written and understandable ones you manage to understand its root.. also i don't know what kind of errors you keep getting so i can't be much of a help here. nevertheless the saying goes 'where's the will there's a way'. i advise you stick to it if you're determined to comp...

Yeah, but the official irrlicht runs by itsself, I would like my autorun on the cd to be 3D, before anything is installed, so we'd have to wait for the next official release or something, I guess. Well... If your solution creates a device using the edt_directx9 device creation flag, it means the ho...

Users obviously won't have the SDK installed so this will only work for a tempoarary solution

When you release your solution, you don't need the SDK. The needed DX source is already compiled into your solution. The user only needs the Dx runtimes, that's redistributables.

is it possible to have ... let's say ... three static meshes and add them to an IAnimatedMeshSceneNode at a different frame?! That would result in animating a character. I'm asking, because morphing isn't available in irr, and this could bridge my problem.

Thanks

you load it just as any other mesh file.

ok, so here's the whole deal (except it's lacking the Dx8 support). I have included both versions... debug and release. http://www2.arnes.si/~mhojni7/irrlicht/Irrlicht.10.NoDx8.rar Note: when you compile your irr program, the directory structure looks something like this: ProgRoot: __[Debug] __[Rele...

1. I couldn't find any .x exporters to support morphing. any ideas?
2. Has anyone tried to implement the morph channeling from .x to irr?

Thanks

hmh... with some jumps and crouches

I managed to recompile the engine, it's for Dx9 ONLY though...
anime4christ, Trouble, I hope it helps:

http://www2.arnes.si/~mhojni7/irrlicht/ ... mpiled.rar

You all must know when you use a FPS camera, apply collision response using some gravity, adjust your keyboard interface and run along your terrain node, that the camera/avatar movement is camera-look-at-a-point based. Thus looking at some angle upwards and moving forward your cam "jumps" ...

You all must know when you use a FPS camera, apply collision response using some gravity, adjust your keyboard interface and run along your terrain node, that the camera/avatar movement is camera-look-at-a-point based. Thus looking at some angle upwards and moving forward your cam "jumps" ...

try to examine the fog class(es) ?

I get the same sh*t. Anybody comes up with a solution, please post it. I'm sick of getting rid of this bug. It's like the static lib doesn't interact with the dll corectly. All linkers are set properly and still... if anybody compiled the new source code using VS8.0, please post .lib, .exp and .dll ...

First of all, it depends on how much code of the original prog you got and what's your OGL programming background. If you can separate the physics code to a stand-alone library, I don't see a point why you shouldn't try using the irr. And hey, if you're talking about real time graphing it could be d...

well first point partially solves your second problem. If you already set the line of fire, it means you have a planar (x,z component) line between them. From the enemy you calculate the angle between his line of view (x,z component of rotation) and the line that connects him to your character. If y...