<p dir="ltr">actually I dont know about any showstoppers at the moment, but I only use about 50% or less of the api, have not tried cycling creating and deleting rigid body jointz, or the same for libload,<br>
libfree etc.</p>
<p dir="ltr">Thr engine seems quite stable in 2.74......<br>
</p>
<div class="gmail_quote">On Mar 14, 2015 5:33 PM, "FRANCISCO ORTIZ" <<a href="mailto:chicortiz@gmail.com">chicortiz@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>"Stability might be even more important for the game engine than it is in
other parts of blender, since bugs in a game affect the end user
experience and are much harder to workaround for an artist."<br><br></div>Sam Brubaker<br><br>###<br><br>You are a blessed man Mr. Brubaker. I would never put it so clearly! :)<br><br>Reminds me <a href="https://www.youtube.com/watch?v=5PmHRSeA2c8&feature=youtu.be&t=8m36s" target="_blank">The Rule</a>... <br><br></div><div>What tends to be a nightmare for artists is when the Blender Game Engine API is changed. Campbell will tell you that scripters are lazy, but unfortunately (<--<span lang="en"><span>no</span> <span>sarcasm</span> <span>here</span><span>,</span> <span>really)</span></span> making 3D game prototypes involves more things than making scripts... :I<br><br>If any changes need to be made to the Game Engine I would like to suggest two things:<br> <br>1) Make something to encourage artists to use Python by simplifying the understanding of the API<br>2) Or to make the game engine more robust If backwards compatibility is going to be compromised somehow. <br><br>And by robust I mean: Something that doesn't crash.<br><br>Yours,<br><br>Ortiz<br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 12 March 2015 at 20:01, Sam Brubaker <span dir="ltr"><<a href="mailto:sam@worldsday.org" target="_blank">sam@worldsday.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">The bge seems usable to me as well, but I do have some bugs in that task list. Stability might be even more important for the game engine than it is in other parts of blender, since bugs in a game affect the end user experience and are much harder to workaround for an artist.<br><br>I agree with Campbell that stability should be a priority until such a time that more risks and major changes are possible. Let me know if I should shut up.<br><br></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 9, 2015 at 12:20 PM, Jacob Merrill <span dir="ltr"><<a href="mailto:blueprintrandom1@gmail.com" target="_blank">blueprintrandom1@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">How can we fix bugs and refactor in the same move? </p>
<p dir="ltr">Also, the engine is very close to usable for me, I had 2 bugs get knocked off the tracker, and now I am hard pressed to find any showstoppers besides the Libload/LibFree cycling crash that appears related to texture cache.</p>
<p dir="ltr">I use almost all of the engines features and my game is stable,<br>
besides rigid body joints failing, but I guess that is fixed as well and will be in 2.74.</p>
<p dir="ltr">the only thing I can think of that I dont use is the vehicle constraints.....</p>
<div class="gmail_quote">On Mar 9, 2015 3:56 AM, "Campbell Barton" <<a href="mailto:ideasman42@gmail.com" target="_blank">ideasman42@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">There is really a lot of work to do on the game engine, see tbe bug<br>
tracker - there are many open bugs. (below)<br>
<br>
I don't think now is a great time to refactor Python API - just by<br>
moving modules around.<br>
First get the BGE stable and usable in its current state. Then make<br>
other improvements afterwards.<br>
<br>
If we don't currently have enough resources to keep the BGE stable,<br>
putting energy into breaking API changes seems not the best use of<br>
time.<br>
<br>
<a href="https://developer.blender.org/maniphest/?statuses=open&allProjects=PHID-PROJ-hjlgdc66wg5yny3jg2le#R" target="_blank">https://developer.blender.org/maniphest/?statuses=open&allProjects=PHID-PROJ-hjlgdc66wg5yny3jg2le#R</a><br>
<a href="https://developer.blender.org/maniphest/?statuses=open&allProjects=PHID-PROJ-we3tj3fbnpw6ltqucale#R" target="_blank">https://developer.blender.org/maniphest/?statuses=open&allProjects=PHID-PROJ-we3tj3fbnpw6ltqucale#R</a><br>
<a href="https://developer.blender.org/maniphest/?statuses=open&allProjects=PHID-PROJ-tbyxh6d7bngojy6cb6dj#R" target="_blank">https://developer.blender.org/maniphest/?statuses=open&allProjects=PHID-PROJ-tbyxh6d7bngojy6cb6dj#R</a><br>
<br>
On Mon, Mar 2, 2015 at 3:59 AM, tristan panzer<br>
<<a href="mailto:republicthunderbolt9@gmail.com" target="_blank">republicthunderbolt9@gmail.com</a>> wrote:<br>
> Hello, I'm start in the game blender development. I propose to move all<br>
> functions contain in bge.logic module in a new python proxy for<br>
> KX_KestjiEngine (like in C++ sources) to replace those functions by<br>
> attributes (when it's possible) ex : bge.logic.getSceneList() to<br>
> bge.logic.engine.scenes. The only role of bge.logic will be to contain the<br>
> constants, the python dictionary and the proxy of the engine. I know this<br>
> breaks all existing codes, but can be useful to do that or I'm on the bad<br>
> way ?<br>
><br>
> Sorry for my bad English.<br>
><br>
> _______________________________________________<br>
> Bf-gamedev mailing list<br>
> <a href="mailto:Bf-gamedev@blender.org" target="_blank">Bf-gamedev@blender.org</a><br>
> <a href="http://lists.blender.org/mailman/listinfo/bf-gamedev" target="_blank">http://lists.blender.org/mailman/listinfo/bf-gamedev</a><br>
><br>
<br>
<br><span><font color="#888888">
<br>
--<br>
- Campbell<br>
_______________________________________________<br>
Bf-gamedev mailing list<br>
<a href="mailto:Bf-gamedev@blender.org" target="_blank">Bf-gamedev@blender.org</a><br>
<a href="http://lists.blender.org/mailman/listinfo/bf-gamedev" target="_blank">http://lists.blender.org/mailman/listinfo/bf-gamedev</a><br>
</font></span></blockquote></div>
<br>_______________________________________________<br>
Bf-gamedev mailing list<br>
<a href="mailto:Bf-gamedev@blender.org" target="_blank">Bf-gamedev@blender.org</a><br>
<a href="http://lists.blender.org/mailman/listinfo/bf-gamedev" target="_blank">http://lists.blender.org/mailman/listinfo/bf-gamedev</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
Bf-gamedev mailing list<br>
<a href="mailto:Bf-gamedev@blender.org" target="_blank">Bf-gamedev@blender.org</a><br>
<a href="http://lists.blender.org/mailman/listinfo/bf-gamedev" target="_blank">http://lists.blender.org/mailman/listinfo/bf-gamedev</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
Bf-gamedev mailing list<br>
<a href="mailto:Bf-gamedev@blender.org">Bf-gamedev@blender.org</a><br>
<a href="http://lists.blender.org/mailman/listinfo/bf-gamedev" target="_blank">http://lists.blender.org/mailman/listinfo/bf-gamedev</a><br>
<br></blockquote></div>