Search options (Page 4 of 6)

But if we had more bricks, the community could grow faster, that's why I advocate lua behaviors/bricks as an intermediate/transition step. The shorter the learning curve, the more people will stay on board after a short evaluation of what can be achieved and with what easness.
And maybe porting robust lua scripts to C++ is more easy than writing them from scratch.

Wow! Works perfectly!

I've put the update_funct just before "def register():" in __init__.py
It works, but is it correct?

Many thanks, I've made some progress and things are clearer now.
I wrongly understood that values were updated each time the panel is drawn.

I've used :
    bpy.types.Scene.my_string_prop = bpy.props.StringProperty(name = "Rename", update=update_func)
to create my StringProperty

Now, in draw, if I use :
    layout.prop(sce, 'my_string_prop')
Anims in the stack are updated, but I can't retrieve the values from the stack into my_string_prop field (which is static) when I click on the anims.

And if I use :
    layout.prop(list_item.my_item, 'name')
I can retrieve the value from name when I click on the anims, but how can I call the update function as my_string_prop hasn't updated ?
Is there a way to assign a StringProperty to 'name' ? (bpy.types.Scene.name doesn't work).
I'm sure I'm missing something evident.

I have to get more familiar with panels before trying this one !

Currently I'm struggling with the anims panel.

[img=AnimsPanel]I:\Anims.jpg[/img]

I've added a field using:

layout.prop(list_item.my_item, 'name')

but I can't figure out how to update the anims' names in the stack.

Do you know how to achieve this and/or can you point me to good and up-to-date tutorials, ressources, snipets...

Sorry Anaël,

What I want to achieve is something similar to the collada and fbx export panel which allow to check a "Deform Bones only" option.

See Blender Collada Export for example.

This option is really interesting when you are using an advanced rig to easily pose your mesh or if you're using additional bones to create shape keys.

This is the "use_deform" boolean parameter in the Blender API.

Additionaly, I want the script :
    - not to write animation frames that are not set in the "Maratis Anims" from Blender Properties/Render panel
    - not to write scale values in the maa file if these values remain constant
    - to write the texture filename in the mesh file formated in this way : "../maps/filename" instead of "filename with path"
    - to export the textures in the maps folder of the project

Did you try importing in collada (dae) format?

A table is identified by its name. If you declare it more than once, you simply update its content.

So if life is sharable between enemie & turrets, you just have to declare it once before using it. You can declare it anywhere as long as it is before using its content.

If life is a different parameter for enemies & turrets or if the number of parameters is different (for example number of turrets and number of enemies are not necessarily the same), then you should create a new table for each set of parameters. Again, you can declare this set anywhere before using its content.

What links tables is not the way they are coded but the way they are used :

rotate(cloneList[j], {0, 0, 1}, rotationSpeedList [j], "local") -- use rotationSpeedList parameters with clones
rotate(turretList[j], {0, 0, 1}, rotationSpeedList [j], "local") -- use rotationSpeedList parameters with turrets

Yes, outside.
You can add any lists of parameters as you want. Just create a new table. For example :

object = getObject("object")
cloneList = {}
rotationSpeedList = {0.4, 0.3, 1}
translationSpeedList = { {1, 0.1, 0.1}, {2, 0.3, 3}, {3, 2, 1} }

for j=1, 3 do
    table.insert(cloneList, #cloneList + 1, getClone(object)) 
end

   for j=1, #cloneList do 
       rotate(cloneList[j], {0, 0, 1}, rotationSpeedList [j], "local")
       translate(cloneList[j], {translationSpeedList[j][1], translationSpeedList[j][2], translationSpeedList[j][3]}, "local")
   end

You just have to create the speed table :

object = getObject("object")
cloneList = {}
speedList = {0.4, 0.3, 1}
  
for j=1, 3 do
    table.insert(cloneList, #cloneList + 1, getClone(object)) 
end

   for j=1, #cloneList do 
       rotate(cloneList[j], {0, 0, 1}, speedList[j], "local")
   end

Spaces, tabulations, returns... are not relevant in lua, you can use them as much as you want to organise your code.

Try this :

player = {

objs = {getObject("player1"), getObject("player2")}, -- create a table that stores all the players
speed = {-0.4, -2} -- optional : set the speed of each player

}

function onSceneUpdate()

    for i=1, #player.objs do -- #player.objs is the length of the objs table (number of players)
        translate(player.objs[i], {0,player.speed[i],0}, "local") -- example : translate each player at their given speed
        if player.speed[i] > 3 then speed = 3 end
    end

end

NB: update = function() is for Nistur's MScriptableBehavior plugin only.