indielib.com

[Javier López]

IndieLib 1.03 SDK

Fairly innocuous but helpful bug fix release.


Fairly innocuous but helpful bug fix release.

[ features ]

+ Added Render::BlitColoredTriangle () method, for rendering triangles with differen color for each of the faces.

[ bug fixes ]

+ Fixed some color glitches on Primitives.

+ Fixed wrong name in GetPosZ().

+ Fixed return value on IND_Entity2dManager::Delete ().

[Javier López]

Hi people!

Render->BlitColoredTriangle ()

Was a method really easy to implement. I don't now why it wasn't already on the engine. It just draws a triangle, and let you choose the color of each of its corners. You can also set a level of transparency for the whole triangle.

TODO:

1. Add it to the primitives tutorial
2. Add it to Entity2d, you can't add it to an entity yet (in the documentation it is wrong)

I want to ask you:

1. Do you think it would be helpful to be able to choose the amount of transparency per corner (for having gradients of transparency). Currently the transparency affects to the whole triangle.
2. Do you think should we create a wrapper for letting use vertex arrays, etc? I think it is not neccesary because you can directly get the pointer to direct3d and use it as you wish. But maybe, thinking in future portability it would be neccesary...
3. Do you need something else in primitives?

[Metadon]

Disregard this, i didnt know what i was talking about.

[Javier López]

[Metadon]

Oh, whoops. Disregard what i said then.

In that case, yes, separate transparencies for corners would be neat.

If you could add a filled triangle with only one colour instead of three, that would also be neat.

[Javier López]

[Metadon]

The alpha value in blitcoloredtriangle doesnt seem to affect anything.

This;

[Javier López]

There is something wrong, yes. It seems like alpha is not affecting primitives any more.

I'll take a look. I think I know what it is.

[Metadon]

Great, that bug is pretty annoying.

A question, is it possible to use blendmodes with primitives? If it is, support for using that would be awesome for some particular uses.

[Javier López]

TODO:

1. Add BlitColoredTriangle to the primitives tutorial
2. Add it to Entity2d, you can't add it to an entity yet (in the documentation it is wrong)
3. Change the names of collision system methods.
4. Splines
5. Check out if there is a problem the second time of calling an animation
6. Resizable window
7. Map editor tutorial
8. Possibility of checking focus lost.
9. SetMousePos
10. Currently, entities can not share animations. Well, they can share it, but if you make a "SetSequence" it will be done in all the entities that share that animation. I have to add a "Clone Animation" method for that. This is going to be in the very next release. It's really important.

Hey! No one here knows OpenGl / Direct3d? I'm starting to have too much work

An english speaker would be also really welcome. He / she only would have to read the sourcecode, fix English errors, and press "commit"

[Metadon]

English isnt my first language, obviously, but i could proof-read the sourcecode every once in a while if it would help. Im afraid i cant help you with Direct3d/OpenGL since i have close to zero experience with them.

[Javier López]

[smjones_gi]

I hope I'm not way off here and outstepping my bounds because I just downloaded the library today but I've found memory leaks.


In the End function of the main class that the game creates I did this to clean things up.

void CIndieLib::End()
{
// ----- Freeing objects -----

Math ->End();
MeshManager ->End();
Input ->End();
Entity2dManager ->End();
Entity3dManager ->End();
FontManager ->End();
AnimationManager ->End();
SurfaceManager ->End();
ImageManager ->End();
LightManager ->End();
Render ->End();
Window ->End();

delete Math;
delete MeshManager;
delete Input;
delete Entity2dManager;
delete Entity3dManager;
delete FontManager;
delete AnimationManager;
delete SurfaceManager;
delete ImageManager;
delete LightManager;
delete Render;
delete Window;

IndieLib::End ();

delete pinstance;
pinstance = NULL;
}

I used the CRT to find them. Now some people may disagree with me and point out that since we are shutting down the app that the OS will clean up the memory for us. I guess you can consider me a purist but I hate to leave memory hanging around for the OS to catch. I like to close apps all nice and tidy.

Put this at the beginning of your "main" or IndieLib function.

// Enable run-time memory check for debug builds.
#if defined(DEBUG) | defined(_DEBUG)
// Always perform a leak check just before app exits.
int nDbgFlags = _CrtSetDbgFlag(_CRTDBG_REPORT_FLAG);
nDbgFlags |= _CRTDBG_LEAK_CHECK_DF;
nDbgFlags |= _CRTDBG_ALLOC_MEM_DF;
_CrtSetDbgFlag(nDbgFlags);
#endif

and you'll see "Dumping Objects..." in the output window after the app shuts down.

Regards,
Steve

[Javier López]

Thank you very much for finding this. This is similar to what Black Bird found.

I have updated the TODO list for the new bug fixing release:

1. Add BlitColoredTriangle to the primitives tutorial
2. Add it to Entity2d, you can't add it to an entity yet (in the documentation it is wrong)
3. Change the names of collision system methods.
4. Splines
5. Check out if there is a problem the second time of calling an animation
6. Resizable window
7. Map editor tutorial
8. Possibility of checking focus lost.
9. SetMousePos
10. Currently, entities can not share animations. Well, they can share it, but if you make a "SetSequence" it will be done in all the entities that share that animation. I have to add a "Clone Animation" method for that. This is going to be in the very next release. It's really important.
11. Fix memory leaks when ending IndieLib.

[smjones_gi]

IND_Render::GetFpsString () { char *mString = new char [128]; itoa (mLastFps, mString, 10); return mString; }

Gives memory leaks! Lots of them. See that 'new' operator?

I saw this occur when my memory leak dump was huge. Is there anywhere where this is cleaned up that I missed?

Regards,
Steve