Hi ben,<br><br>I can help you, specially in adding a node editor option for designing states.<br><br>--hamed<br><br><div class="gmail_quote">On Thu, Jun 12, 2008 at 12:02 AM, Benoit Bolsee <<a href="mailto:benoit.bolsee@online.be">benoit.bolsee@online.be</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi Kent,<br>
<br>
I know that a state engine system like you describe is already possible<br>
but it becomes messy very quickly because you have all these connections<br>
between bricks crossing each other. The only sensible way to build a<br>
state engine of a certain complexity with the current system is to code<br>
it in a single big Python controller, but that's not user friendly for<br>
non programmers.<br>
<br>
The main goal of the improvement is<br>
1) readability: the GUI allows you to display only the<br>
controllers/sensors/actuators that are linked together in a state and<br>
not just all or nothing as today. An overal vue of the state engine is<br>
also very useful.<br>
2) user friendly: state engine implementation becomes accessible to<br>
non-programmer.<br>
3) performance: disabling sensors of inactive states saves CPU.<br>
<br>
I forgot to mention that there is another enhancement that is needed for<br>
the Apricot project: support for shape keys in the Game Engine. I'll try<br>
to do that as well.<br>
<br>
Benoit<br>
<br>
_______________________________________________<br>
Bf-committers mailing list<br>
<a href="mailto:Bf-committers@blender.org">Bf-committers@blender.org</a><br>
<a href="http://lists.blender.org/mailman/listinfo/bf-committers" target="_blank">http://lists.blender.org/mailman/listinfo/bf-committers</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Hamed Zaghaghi,<br>MSc. Student of Algorithms and Computation,<br>Engineering Science Department, University of Tehran