MaterialDrawCallback()

[Flexman]

I was going to use MaterialDrawCallback() to bind user skins for different vehicles. This callback is supposed to return a pointer to the entity being rendered no?

 

Any attempt to access TEntity properties results in an exception even though it's not a null pointer. Not really sure what's going on with that.

 

Function MaterialCallback(material:TMaterial, entity:TEntity)
  if (entity.material)
     // kablewie
  endif
End Function

 

Just wondered if anyone else has tried this and got it to work OK? Seemed like a reasonable way to create non-instanced player skins.

[LordHippo]

I also have the same problem.

I'm using this in C and actually the entity is always NULL.

However the number of times this callback is called is correct.

 

Anyone have ever used this callback?

[L B]

Confirming, tested in my C# implementation.

I would also like this fixed somehow.

[Aily]

This code is printing

 

.............

 

Camera

Directionallight

Camera

Directionallight

Camera

Directionallight

Camera

Directionallight

Camera

Directionallight

Camera

Directionallight

Camera

Directionallight

Camera

...........

 

Framework leadwerks.engine
registerabstractpath AppDir
Graphics 800,600
createworld
cp=createpivot()
cam=createcamera()
entityparent cam,cp
moveentity cam,vec3(0,5,-5)
pointentity cam,cp
b=createbuffer(800,600,BUFFER_COLOR|BUFFER_NORMAL|BUFFER_DEPTH)
lt=createdirectionallight()
moveentity lt,vec3(1,2,3)
pointentity lt,cp
c=createcube()
mat=creatematerial()
setmaterialcolor mat,vec4(1,0,0,1)
paintentity c,mat
Function on_paint(mat:tmaterial,ee:TList)
For e:tentity=EachIn ee
 Print getentitykey(e,"class")
Next
End Function
setMaterialCallback mat,on_paint,MATERIALCALLBACK_ENABLE
Repeat

If KeyHit(27) Or AppTerminate() End

turnentity cp,vec3(0,.1,0)

setbuffer b
renderworld
setbuffer backbuffer()
renderlights b
Flip 1

Forever

 

seems like second function parameter is the list of cameras\lights

 

Want to know how to use it myself

[Josh]

Sorry, the docs were wrong. There is no second parameter in the callback:

http://www.leadwerks.com/werkspace/page/Documentation/le2/_/command-reference/materials/materialdrawcallback-r295

[Aily]

Sorry, the docs were wrong. There is no second parameter in the callback:

http://www.leadwerks...awcallback-r295

 

So then how in this callback to get from what entity was callback called? Because with only one material parameter seems it is unusfull for us

[Josh]

There's not necessarily even an entity associated with every material. I would use the entity draw callback for anything that needs the entity.

[Aily]

http://leadwerks.com/wiki/index.php?title=SetEntityCallback

 

• ENTITYCALLBACK_UPDATEMATRIX - will be called whenever an entity rotates or moves.
  
• ENTITYCALLBACK_FREE - will be called when the entity is freed.
  
• ENTITYCALLBACK_COLLISION - will be called when the entity collides with another entity (bodies and terrain only).
  
• ENTITYCALLBACK_UPDATE - will be called once each time UpdateWorld() is called.
  
• ENTITYCALLBACK_MESSAGERECEIVE - will be called when the entity receives a message.
  

 

it's not here

[Aily]

I would use the entity draw callback for anything that needs the entity.

 

How?

[LordHippo]

I was talking about MATERIALCALLBACK_DRAW.

The wiki says:

Gets called for every instance that is drawn that has this material. Using this will disable fast instanced rendering for any entities with that material.

 

So I think if the entity is not passed to the callback, it would be useless.

So I assume it as a bug.

 

Another question: will the entity draw callback called exactly when the entity is being drawn?

For example if I change shader uniforms in this callback, will these changes be applied to each entity, or the last change to all the entities?

[Aily]

I don't get how it works

[LordHippo]

I don't get how it works

It was the original question Aily.

The entity is not being passed to the material draw callback.

So any function on that entity will result in a crash.

In C, the entity is always NULL.

[Aily]

It was the original question Aily.

The entity is not being passed to the material draw callback.

So any function on that entity will result in a crash.

In C, the entity is always NULL.

 

As you can see - in my function in BMax - i don't do any with entity, line inside function is commented. And error spawn on renderworld.

Good if it works in C.

 

P.S. Yeah, i'm some mistaked with callback names before...

[LordHippo]

As you can see - in my function in BMax - i don't do any with entity, line inside function is commented. And error spawn on renderworld.

Good if it works in C.

 

P.S. Yeah, i'm some mistaked with callback names before...

Sorry. I didn't know that ' is for commenting in BMax.

 

Yeah it's working, if the NULL entity is assumed correct

[Aily]

Last news

This function don't have entity, and don't be work as we supposed. Wiki is wrong, wee need always look only to

http://www.leadwerks.com/werkspace/page/Documentation/le2/_/command-reference/

 

I maked not instanced materials, but for this i creating copy of mesh on HDD, load id, delete from HDD - have not instanced model, but materials is instaced.

 

Parse all it surfaces, and same write copyes of materials to HDD, load it, assign, delete from HDD.

 

Same with shaders...

 

Looks like there is no another way.

[Josh]

At the point materials and shaders are enabled in the rendering pipeline, the code has no idea what entities are being drawn. All it has is a 4x4 matrix. Materials are not enabled per-entity. They are enabled once for each batch of surfaces drawn.

[Aily]

It easy to hack your engine for you Josh

Just add funtion LoadUniqueMesh that will be add system time value to mesh,materials and shaders filenames before loading it.

And engine will think - that it's absolute separate mesh with separate materials.

And all will be happy