Search options (Page 20 of 60)

I have to say that I don't understand what you mean by "restrict  the export to Deform bones only"
can you give a clear example ?

Hi and welcome !

one question is, should the bug report topic on the forum be closed to redirect all bugs/patchs on google code manager ?

You can use a dot product between two normalized vectors :

ex :

pos1 = getPosition(object1) -- player
pos2 = getPosition(object2) -- enemy

-- get the direction of object2 if it's face is oriented toward the Y axis
dir2 = getRotatedVector(object2, vec3(0, 1, 0))

-- get the vector between object1 and object2
vec = pos1 - pos2

-- find the angle between dir2 and vec
dotValue = dot(normalize(dir2), normalize(vec)) -- dot product returns the cosinus of the angle
angle = math.acos(dotValue) -- get the angle in radian
angle = math.deg(angle) -- convert to degree

If you want to code a 2d rotation (around the angle Z only) you can use some arithmetic :

-- get 2d vector length
function getLength2d(vec)

    return math.sqrt(vec[1]*vec[1] + vec[2]*vec[2])

end

-- normalize 2d vector
function normalize2d(vec)

    length = getLength2d(vec)
    vec[1] = vec[1] / length
    vec[2] = vec[2] / length
    return vec

end

function lookAt(object, dir, rotSpeed)

    -- compute object X dir and Y dir
    rot = getRotation(object)

    zAngle = math.rad(rot[3])
    sinZ = math.sin(zAngle)
    cosZ = math.cos(zAngle)

    YDir = normalize2d({sinZ, -cosZ})
    XDir = {-YDir[2], YDir[1]}

    -- dot products for orientation and angle
    ori = (dir[1]*XDir[1] + dir[2]*XDir[2])
    angle = math.acos(dir[1]*YDir[1] + dir[2]*YDir[2])

    if ori < 0 then
        angle = - angle
    end

    rotate(object, {0, 0, 1}, math.deg(angle) * rotSpeed)

end

For a true 3d look-at, it's more complicated, you need to use a dot product to find the angle between the objects
and a cross product to find the rotation axis. It's better you use the look-at behavior directly.

first this two line need to be inside onSceneUpdate :
force = getCentralForce(Player)
speed = length(force)

but you are not using "force" or "speed" variables.

What is the problem with your script ? is it not compiling or just acting strange ?

I don't know what your script does exactly, but I can say that you should do "thrust cap" after "raise thrust\lower" and not before.

If you just want to add this velocity limitation we talked about, try to add this after "--Movement RCS" block :

force = getCentralForce(Player)
speed = length(force)

if speed > maxSpeed then
    addCentralForce(Player, force*(-0.1))
end

Hi,

do you mean like the object should behave normally with no damping but could not go faster than a certain velocity ?
or do you mean the object will be affected by a sort of resistance or friction ?

He used blender particle hair, that was the problem as it cannot be supported like that in real-time, it need to be textured plane.

For example, if I continue on this random example, the way I would do it is like this :

- create a game plugin in c++ with 3 behaviors (player, enemy1, enemy2)
- a custom MGame class if necessary (for example to handle path finding or global events)
- the variables (speed, power) will be attached to each behavior so it will be possible to edit their value in-editor
- a custom draw function for the player behavior to draw the field-of-view in-editor as an helper
- custom script functions in c++ to call special actions from lua
- the scene specific logic in lua

There is a way in lua to control objects : http://wiki.maratis3d.org/index.php?tit … ng_example
it can be helpful for some entities, however everything need to be written in lua and cannot be manipulated by the editor compared to the behavior system.

It is seductive to think about a data editor inside maratis to manipulate game variables, I taught about it when writing the behavior system, but I realized that it will be hard to be flexible enough and anticipate what a game will need (float, string are easy, but maybe you will need to store a complex table, a matrix or else).

kirilz, you wrote you'd like to write the data definition in lua but operate it in c++, if you operate the data in c++ it means you have to know the structure of the data in your c++ code, so why no define the data in c++ ?

What I'd like to discuss, and it's what I try to ask Nistur too, is a practical situation in a game that can be studied, like :
- a game with one player and 2 types of enemy :
  - player : can move around a level. It's variable are : speed, life, score, field of view
  - enemy 1 : is attracted by player, touching the player reduce player life depeinding on it's power. It's variable are : speed, power
  - enemy 2 : is attracted by player when out of player field of view, and repulsed by enemy 1 if it's power is inferior as the one of enemy 1. It's variable are : speed, power

we should :
- be able to change the variables in-editor to fine-tune the game
- the entities interactions should be updated automatically
- I'd like to call special actions triggered in lua
etc

Hi, it looks very promising !
I'd like to see a video !