NW.js 0.13.0-beta4 is out now, is that still affected?
Just tried it.
Same thing.
No change.
—
Dunno Tint looks it's not quite there.
Just tried 122 preview still gets the ghost nwjs after first run.
Maybe it's time to try out Electron Ashley ?
At least not have all our eggs in one basket.
System compare is between values.
Touch.x, touch.y
Develop games in your browser. Powerful, performant & highly capable.
http://opengameart.org/art-search-advan ... ollection=
lol
R0J0hound
Thats spot on. Just tested, spawning eats up fps, but it goes right back up to 60 even with hundreds of objects.
Guess there were some improvements I missed.
9 patch is like 9 objects in one.
They are already picked.
Vsync means speed tied to dt is also tied to frame rate.
Meaning stuff goes faster at higher frame rates, and collisions will suffer.
Also most browsers are capped at 60 anyways.
I haven't really talked to Kayin a lot.
Maybe you could ask who made the other game.
I wouldn't want to be the guy that gets in a lawsuit.
It's doing it for me in preview, but only after I open and close it the first time.
The nwjs 32 remains in the task manager.
There is no law that allows it.
There are people that steal, and people who sue them.
If you're still not sure, the rule of thumb is: do unto others.
Can't read minds.
You don't apply it to the character. You do it to the obstacle.
I think Waltuo was getting at that it would also disable collisions for some other object that might interact with the obstacle.
That's a whole other argument than the ops.
Check the sprite object.
Um, what's wrong with number 2?
If it works with physics, it works with all behaviors that use solid.