Irrlicht Engine

Vista, using Visual C++ Express.

The joystick and mouse example included in the download for Irrlicht 1.5 doesn't check to see whether or not a joystick hat exists when it determines the direction to move the cursor.

Code here:

const u16 povDegrees = joystickData.POV / 100;
if(povDegrees < 360)
{
if(povDegrees > 0 ...

Parent the blade to the engine and have the blade rotate. Whatever happens to the engine will also happen to the blade (if you move the engine, the blade will be attached still), but the blade will be able to spin on it's own.


So make the engine the parent of the spinning blade.

This is awesome. Vote yes on prop. Stickthis.

Just a quick glance over and you can already see this tutorial answers the most basic questions in a rather nice order of what someone jumping into the creating-a-game-with-irrlicht world thinks sequentially. Why isn't this stickied?

I tested this out in my map-editor. At a grid size greater than 1,200 and a grid spacing of 4, I still have no drop in frame rate at all. Changeable colors, simple to implement, and fully compatible as a scene node. It's so easy, no wonder it's #1. Err, wrong commercial.

Anyway, I benchmarked this ...

Yes it's do-able, in fact it's not very hard to do at all.

Care to revise that answer?

I've done it so far, but it required so many rewrites I can't recall all the files I had to change. You can't do it with a single view matrix, you have to change how it's specifically drawn to the screen by ...

Alright, I've almost succeeded so far. I say almost in that I'm able to account for half the directions necessary for this perspective. I can't do the other half with a single matrix4. Working on it as I type. Will update soon.

you have a solution? I spent days messing with things to no avail when I last looked at this ( bug report ), gave me a headache

To fix that weird look of the sphere, you have to correct Irrlicht's default FOV. Just set the FOV to (45 * irr::core::DEGTORAD). Should work fine. I'm still working on ...

Chris, please hold questions until I respond to the above. Yes it's do-able, in fact it's not very hard to do at all. -And yes, I know of some, which I'm going to list as a response to the second question. I'm going to post it all together soon.

Sure thing; let me compile a bunch of resources then and I'll post them all here when I'm certain I've done both the things you're asking for.

Okay, regardless of what the other engines are doing, that article you sourced has no sources of its own that are reliable, and it even states so at the top. If you look at a "perspective corrected" picture, you get an otho view with depth in only one direction. Hence the current camera. It is ...

Look at your own example, you FAILED at creating a fish-eye. Never once did I claim to be attempting to implement fisheye distortion. My code shows that the distortion occurs at large field of views.

Nope, that one isn't wrong. The D3DXMatrixPerspectiveLH documentation shows the exact same matrix ...

Okay, ignoring all the nonsense you just spewed, the perspective "problem" isn't a problem. It's a reality of curved lenses. I don't want to keep reiterating myself. Look at your own example, you FAILED at creating a fish-eye. I took a screenshot to show you what's wrong with it. Why did it fail ...

Okay, update. I fixed your source code, which I suspect was just an accident or some such (just had to change the irr::SEvent event to const SEvent& event), and it ran fine except for it's not really a fish-eye lens, although you used the same altered attributes I mentioned above about how it SHOULD ...