Horde3D

The current code (including all documentation) in the SourceForge svn is very close to what we plan to release as Beta3. Since there were many changes after Beta2, it is well possible that some new bugs got introduced.

Please try out the latest version with your project to help identifying possible problems. We would like to release Beta3 officially as soon as possible. From the readme:

Looking good! I will take SVN head for a spin as soon as possible.

Mind if I provide a few minor grammar corrections to the readme?

_________________
Tristam MacDonald - [swiftcoding]

Beta3 looks good but I am missing way how to change texture in material sampler. Is there any way how to do that by official API?

we will probably need something like this:

or

A function setResourceParamstr is already available. Currently it only allows changing the class attribute of a material.

Does not even compile for me as it complains about the function "max" not being found (egRendererBase.cpp:176).
Did you mean maxf? That one is declared in utMath.h. Is that function declared somewhere on Windows?

I know. I was thinking about new function (in addition to existing one) which allows me something like this:

Ah thanks for pointing that out, max is defined in windef.h indeed. I (hopefully) fixed it by introducing maxi.


Sorry, I overlooked the additional parameter.

You could also consider using std::max instead

_________________
Tristam MacDonald - [swiftcoding]

I am missing support for DXT1A textures (DXT1 with 1-bit alpha). Detection of DXT1A from DDS is little more complex (you have to decode block and compare colors of the block ( if colour0 <= colour1 then DXT1A else DXT1 ). But I think that it is save to assume that all textures are DXT1A. There is probably no speed penalty for doing that. This modification in the egRenderBase.cpp will enable DXT1A textures and DXT1 will work also.

Ln: 234 (old code)

Ln: 234 (new code)

Horde3D::setNodeActivation does not wok same way as in the Beta2. Now it does not affect children of the node. Is it new feature or bug?

ii001, thanks for the feedback.


Good point, we will check that...


This seems to be a bug, probably related to the the introduction of the spatial graph.

Is anything planned on manually setting material textures? I've just hit the problem that for this project I need to dynamically create/manipulate textures of different size for one material.

I'd say, as far as possible the whole material/pipeline/shader system should be accessible for programmatical creation of resources.

EDIT: Just saw that I am including the internal headers already (for my own scene nodes), I might as well just use the functions there.

EDIT2: Argh. There isn't even an internal interface to change samplers -.-

EDIT3: I really need this, so I just started my own patch for that. First part in the attachments.

And who disabled *.patch in this forum? -.-

Sorry I haven't looked at beta 3 yet, but can't you use the following code to do that?
Horde3D::setResourceParami( materialID, MaterialResParams::TexUnit_0, textureID );

You can't do that any more as the textures are now referred to by names and the functions for accessing them have been deleted.

EDIT: Added a patch that implements changing the samplers. Does not yet implement adding or removing of samplers, though this is quite simple to implement. Please, share your thoughts on the interface for this.

EDIT2: Both patches released under the WTFPL. Use them as you want.