I was just testin out the extrusion constant.. :D Cos the shadows tended not to reach certain points if it was too far off. Infinite planes would be nice. :D

 Sent. :D

 Sorry I took so long... :( I'll send it to you right away... What email addy you want me to send it to?

 Wow that's excellent.. (ole)
I hope to see some major improvements soon!
Haddd looks to be really promising! :D

 I think it's mainly to do with the Tools namespace.
Why not build it directly into the main Haddd class?
So instead of importing a mesh using HImport.Haddd.Load,
make it Haddd.Scene.MeshObjects.Load?
or Haddd.Import.Load?

 Another thing I realised about the engine while playing with it.
It's rather disorganised... It could do with some reorganisation.. :P

 I'm waiting for the animation module to be released. :D
In the meantime I'm doing some 3d modelling.
Haha that's why you haven't heard from me in a while Haddd.

 Gracias :D

 By the way Berserker,
Can you release some documentation on the scripting commands?
List what kinda options are available...

 Mucho Gracias! :D

 Hi berserker,
What's the variable to set in my material script that adjusts the U and V tiling?

Código [Seleccionar] Expand

material "terrain" {

layer "layer0" {
 map diffuse {
  mapChannel 0
  amount 1
  u_tile 10
  v_tile 10
  color  ( 0.690196 0.690196 0.690196 1.0 )
  fileName "grass"
 }

 map specular {
  color ( 0.1 0.1 0.1 0.1 )
  power 50.0
 }
}
}

I can't seem to get this to work right.

 Wow that's some pretty damn powerful stuff...
Haha.. The material scripts rule! :D

Thanks berserker! (ole)

 Hey guys,

Do you think it would be better seperate the material portion of the .haddd files into a seperate material file? Maybe a .material file? That way it would be easier for someone to load the same mesh but with different textures using external files. Of course it would mean there would have to be an extra line of code to specify the material file... But shouldn't be that much trouble if you just put it as Mesh.LoadMaterial(string) right? :D

Another thing is, at the moment, we're creating a material array whenever we want to assign a material to a mesh right? Would it be a better idea to make it a list instead and have users create a single material and add it to the mesh.

Maybe something like this:

Código [Seleccionar] Expand

HMaterial material = new HMaterial;
HMaterialLayer layer = new HMaterialLayer();
material.AddLayer( layer );
sphere.AddMaterial(material);


That way we can keep adding materials to it without having to worry about reconstructing the array.
Is this feasible or does it cause performance issues?

 Thanks a bunch Vicente... :D

That's encouraging.. I'm gonna try to model some stuff and put it in the game...

I'll need some ragdoll templates too so i'll try my hand at that when I get confident enough.

 Thanks! :D Expect more though! B)

Oh yeah, you think the angle wrapping is a good idea Haddd?
Bringing it down to 0 to PI.