Irrlicht Engine

Ahh, right you are! Thanks hybrid

Ahh, that's very helpful, thank you both! Pretty much the only problem remaining is why does the fireball go away. I'm going to look into it in between hammering on raknet to get it to play nice with irrlicht. There's a pre-alpha package available if you feel like checking it out, by the way (in sig...

I think you can supress the typematic rate of windows inside your application, I don't recall the exact setting tho.

When it starts, it pours. Let me tell you I fixed problem 3 too. Prepare to be amused : scene::ITerrainSceneNode* terrain = sm->addTerrainSceneNode(path+"terrain.bmp",[...] should really be, at least if we're writing in C, terrain = (scene::ITerrainSceneNode*) sm->addTerrainSceneNode(patth...

Ok, I'm pleased to report that I've made some headway.

Point 4 above is due to nothing else than the expectation of the executable to actually find tower.x and the other referenced files SOMEWHERE. All in all not exactly unreasonable on its part.

Right, but look in the cmd window, what does it say ?

So run them from a cmd, you'll be able to see their output and error message that way.

I would very much like to believe it's the hardware, or the drivers, but the problem is I've been able to reproduce this on three different systems.

It's my "code", if you can call it that.

So basically, I've been playing around with the supplied demo, and I've managed to accomplish a few things. However, there's a few things that I can't do and are driving me nuts. 1) Remove the quake map. That's right. The demo loads a bsp file, which is a pre-light terrain+object mesh. I want to rem...

If make says they're not in there, they're not in there. Put either the path to the .a in correctly, or else put the .a in the path you currently use.

With some testing it turns out the 1024x768 resolution issue was a local problem, strictly due to bad directx9/videocard interaction. Nothing to do with Irrlicht

Hm... well I still can't quite figure why that is.

And since we're on the can't figure line, why does changing the resolution to 1024 768 crash the screen shoots ? (ie, if I modify in cdemo.cpp to 1024, 768, pressing F9 crashes the demo).

Well yes, but moreover, why would you want to do that ?! I mean logically, do all the video stuff in one function, rather than have to get the device twice ? No ?

I know it can either load zips/pk3s or else it can load precompiled quake levels

I don't understand why getvideodriver() is called twice in the demo example ? Namely, once in cdemo::run void CDemo::run() { [...] video::IVideoDriver* driver = device->getVideoDriver(); scene::ISceneManager* smgr = device->getSceneManager(); gui::IGUIEnvironment* guienv = device->getGUIEnvironment(...