Irrlicht Engine

Software-way: convert the texture to a image and resize as already known.

The Hardwa[y/re]-way:
i think you can use hw accelerated scaling by rendering the Texture on a plain to a big RenderToTargetTexture in high quality (Antialiasing, Anisotropic Filter, Trilinear Filter etc)
and then convert the ...

Yeah thx,

the UPX sound nice, it will rearrange the exe and integrate a decompressor automaticly.

i looked at the irrCompileConfig.h and only found a few switches that should be commented out im testing what that brings, but

I believe the model-loaders make up the most space?

Do i have to have ...

hi, i like to know how you guys shrink the size of Irrlicht-Programs.

Mine are always 4 MiByte and above. In comparison GLUT programs are like 40KiBytes and such. I know there are many features in the Engine, but i thought the linker only links actually needed features to the programs. Is this ...

a perspective (isometric, perspective) is made with matrices

core::matrix4f camProjection;
camProjection.buildSomething...

then you can set the matrix to a camera->getFrustum().set... or camera->setTransform...,
or directly to driver->setTransform(ETS_PROJECTION, camProjection);

Hi, i like to ask if it makes sense to use two irrlicht devices (NULL-device for loading, saving) and a 2nd for rendering?

can both devices share data?
how would they be made threadsafe?
are they threadsave anyhow?
what pros and cons has IReferenceCounted to std::auto_ptr<> and such?
does anybody ...