posted 11-02- 08:30 AM
Hi all,Any thoughts on this would be appreciated -
I am seeing unexpected origins for fire which I have not intentionally programmed. I don't understand exactly what is happening here but here are two possibilities(I am leaning toward possibility two:
Possibility one:
As you know the game engine starts engine fires under certain circumstances. I believe someone said at 50% damage, the engine can catch fire. Before I added my engine damage code, the engine fires were always at the center of the engine object.
It appears that now(after adding my damage code) the game engine may be starting the fire at the origin of the last SmokeTrail function processed by the higher level obDamage function.
I have a fuel leak process which creates a "fuel leak" smoke trail coming from the right exhaust manifold on the P51D. Once in a while in addition to the fuel leak smoke trail and a fuel leak noticeable on the fuel gauge, there is a small fire coming from the same origin as the fuel leak smoke trail. It is also the same diameter as the fuel leak smoke trail.
Possibility two:
I have a small fire function immediately following the fuel leak function. It appears the fire function starts the fire at the origin of the fuel leak function. This would seem to say that when the fuel leak and fire functions are called at the same time, the fire starts at the origin of the fuel leak smoke trail. If this is true, then placing the fire function in a different place would cause a fire in the origin of whatever smoke trail function preceeded it. It could also mean if you place the fire function last, it will start a fire at the origin of whatever was the last smoke trail function to be executed.
I know you could explicitly make the fire function have any origin if you code it properly. I like how this effect is working, but I just want to understand exactly why it is doing this.
Thanks,
Condor out
------------------