IJCT ,

michael ,

Check rex's rex_text_properties behavior.

rexrainbow , that would be simply amazing! Thank you in advance

eli0s

Iw seen that, its an old plugin and its boids overlap eachother... wich is a deal breaker for me...

I see. Then perhaps you can build something with events. Have a look at this example made by R0J0hound. I believe you can fiddle with it and make something that resembles a flock-like movement.

-EDIT- Sorry for deviating from the main topic, this behavior is amazing! -EDIT-

irina , have a look at this, perhaps it already does the flocking part.

Thank you A0Nasser

sizcoz , I guess that in your case the GT 745 is making the difference from Monumental's results. Dedicated graphic cards seem to add a lot to the performance.

saiyadjin , the debugger isn't that accurate, especially if you're displaying a lot of staff it can cause a lot of performance loss. I think it's better to use a text object (or even better a sprite font) to display the fps, cpu etc in normal preview.

— , the examples above however are on a different level. Also, The light-shadow system as it is now can't really support more than one light sources without artifacts.

Monumental , I see... That's unfortunate, I guess integrated chips aren't as well optimized for this kind of calculations.

sizcoz , Thanks! Does your laptop have a dedicated graphics card? Those fps results are remarkably good!

saiyadjin , that's great! This is also a laptop right? I guess the 980M is a beast even on it's mobile form!

eli0s

why is everyone saying that NW.js 12 is good? its horrible! take a look, this is with the exact same project!!

Yes, I saw this on the other topic and I am very surprised. I don't understand how or why on some machines the recent updates made things worse. In my case the improvement is dramatically for the best on a recent benchmark I made. On this particular example I don't experience any lag, jerkiness or frame rate inconsistencies.

However, just to be on the safe side, before I replied with this post I visited my old post about the jerkiness in the movement and run the ridiculously simple capx I 'd made on that first post. I must say the results are not as smooth as I would have wished for.

Try the current r198 beta which has an optimization in rendering and the latest NW.js 12. I think you'll get much better performance at least concerning any jittering you might have.

-EDIT- Also, Ashley just posted a blog post in response to your question about single core usage.

Monumental , I 'd expect more from surface pro... Which version of the tablet do you own?

QuaziGNRLnose , it's been a while now, any plans for (at-least-a-basic) workflow tutorial..? And what are the news from the manual's front..? Anytime soon would be awesome...