So I'm trying to get dynamic water to work so see if it really is as laggy as so many people claim.

I'm going to explain what I'm trying to do, line by line.

Ln 1 and 2 are self explanatory (I know they work.)

Ln 3. I'm trying to get a particle so it doesn't preform the velocity modification on it self and it only takes into account other particles around it.

Ln 4. Detects if a particle is in the proximity of 20 pixels (I know it's big) of another particle.

Ln 5. The particles repel each other.

------------------------------------------------------------

When I try spawning a few "Water" particles nothing happens
(except what'd normally happen if you spawned a particle).

Could someone explain to me what is wrong with my code and not just ignore this like my last 5 questions?

Water.Pos - Water.Pos is ALWAYS 0.

Think about it


You probably wanted to make an inner loop... something like this

Har har, solved the angle problem. It was pretty simple to begin with. First I calculate distance between the two objects,

and I get the direction with...

What? You can check how much dynamic water lags by using an emitter that spams infinite lifetime particles with the properties of water. You'd only need lua if you want to make stuff float. That's kind of pointless though due to all the lag it'd produce anyways.

Thats the point of water - making items float or sink on it. And an "water like quality" isnt possible WITHOUT LUA. Things settle.

It's perfectly ♥♥♥♥ possible without Lua? And it's not LUA. It's not an ACRONYM. Water like quality = low friction low bounce slight sticky no sharpness low mass. TOTALLY NEEDS Lua FOR THAT RIGHT. Stop being a sheep, Lua isn't some magical fairy stick you can just wave around and change the engine with. Actual pixel-physics water requires particles. GJ knowing nothing and flamebaiting someone who knows more about everything than you.

As I said before the only thing Lua would be good for is making things float and WHAT IS THE POINT IN THAT if you can only have a puddle 2 x 6 pixels in dimension without lag.

Dont give me the ♥♥♥♥ with "Lua isnt an acronym" I know that, im not a moron. And you know how many people tried to make a good representation of water in CC? Alot. It doesnt work, things settle, frictionless or not. And no, you dont know more about everything than me. Infact you are being rather stupid. His idea of a water simulation will work very well, with the 20 pixel repulsion range. If he sprites it right, It could make something that looks and acts alot like dynamic water, yet with only one particle where there would be over 1000.

Are you dumb or something? How is it dynamic water if there is only one particle that is manipulated for water? Yes, I do know a lot more than you, and particles that don't settle for long enough to show you how laggy dynamic water is would be easy to make without Lua. And Lua isn't an acronym, ♥♥♥♥♥♥♥. You used it as one. I'll give it to you all I want. Then again, your grammar is atrocious anyways so I don't think you even know what an acronym is.


You don't even understand his idea. It's not one particle where there is over 1000. Great job making yourself look dumb while asking for it.

"Ln 4. Detects if a particle is in the proximity of 20 pixels (I know it's big) of another particle."
Which means it will push away from any particle in 20 pixels. Sure, there will be a few particles within 20 pixels, but if the push is strong enough, there will be a circle with a radius of 20 around one particle, taking up the space of 1256 pixels, which in "water without Lua" would be 1256 lagging particles. And I know Lua isnt an acronym, and I was not using it as an acronym. Unless of course WITHOUT is an acronym too. And just because you have been around longer than me still does not mean you know more than me. You are not understanding his theory of making water work.

Don't hate me for this daman, but smith is right in this, although he made some invalid points.
The idea is that every pixel keeps distance to the others while still looking like it would be filled with water. The particles are big but not as much lag.

So It'd take less particles to fill a bigger space.

But apparently the Lua function for checking the
Water Preset Names that Geforz Suggested are quite
laggy, even if a normal rocket explodes or a clone gibs, it's choppy.
(And I have a 3.0 Ghz CPU with 4 Gigs of RAM)

How stupid I was to forget my basic pre-school training for calculating distance.
I'm gonna try Atomic's method for proximity this afternoon after school.

Hmm, as for the preset names thingy, how about a function like

And for the comparations


Edit: I just noticed lots of typos. I fixed them now.

It's not going to be water then? When you shoot it it won't splash. There will be an area above the water where things will float when not even in the water. Might as well just make it one pixel big water and call it a day. OR wait, hey, 0 pixel big water and use zones instead!

Point is it's not water if physics isn't going to be able to be applied to it. It's just space where stuff floats, except with added lag because of the use of particles far apart from each other instead of zones.

Can someone perhaps create a quick script that attributes some gold to Team 0 each time someone on Team 1 is killed? And if possible, perhaps make it so only Team 1 deaths caused by Team 0 count.

Pardon me for again taking against you, but...
I never said it wouldn't have physics applied to it.
I meant that the pixels can be covered with, for example, water-like screen effects, so they keep the distance between each other as 20(or just about any number).
The water is not as fluid, but it will still flow around and stack on each other. It will only keep the distance to terrain, each other, and maybe bullets for splashing. Actors just have effects like damping applied to them when in range of the water pixels. The water flows and affects things, but doesn't cause that much lag thanks to reduced amount of particles.

Edit: Typofix