You can change the 'viscosity' value if you like. In line 24.
evilSOB, you made this so simple! very user-friendly.

Yes, but i mean about fps-independent feature... i think, there is a trouble, in the evening i'll send you video

I think Vet is right, the fps-independance is a bit of a "fudge" ATM.
Im going to have another look at it shortly, just NEED coffee first.

Glad its user-friendly, thats something I take pride in...

Also guys, I think we may need to change the "name" of the viscosity define.
Because if the terrain size IN QUANTS is small, the viscosity needs to be small to simulate a small body of water.
But when the terrain size is large IN QUANTS, but has the same number of wertices as the small one,
then you need to set the viscosity high to simulate a large body of water.

So maybe "viscosity_scale" or something? Any ideas...

That would be perfect.

hmm... i dont think so: for example, user throw brick into the large lake and into the small lake... so, velocity may be the same

No, you're right: if large terrain has the same number of vertices, as the small one, looking you really need to scale velocity

My thoughts exactly.
To my aging mind, the "velocity scale" and a fluids "viscosity" will be directly related to one another.
So my "viscosity_scale" allows the programmer to "tweak" those values at the same time.
A higher viscosity_scale means that either the terrain is a large body of "water",
or a small body of a "thicker" fluid.

Would you guys agree with this? Play with the viscosity value with what Ive already posted to see what I mean if need be.

"tweak" is good, but i dont think that its good in this case

I think, that you may find distance between 2 vertexes and count viscosity_scale automatically

For example, if dist_between_vertexes = 1 Quant, then viscosity_scale = 1,
if dist_between_vertexes = 2 Quants, then viscosity_scale = 0.5,
if dist_between_vertexes = 0.5 Quant, then viscosity_scale = 2

Something like this

Sorry, but I think that would be bad.
FI, what if you have a level where one quant has a "game" scale of one inch,
then another level/game where the game-scale is one quant = one foot.
It would look awful.
Its got to be up to the level designer to decide on the "viscosity_scale" that
"matches" both the game-scale of the level, and the "type" of fluid being represented.

[EDIT] Getting this thing frame-rate independant is being a real bastard!

Hm.. what about this variant: if designer set viscosity_scale = 0, then it is counted aitomatically, and if != 0, then engine would use that value?

Ill keep it in mind, cause I dont think it really makes any difference, after thinking about it.
After all, the viscosity_scale calculation will take place at the start of the action anyway,
and IF the entity is being created by ent_create, then the calculation will be completed by
the time the calling function over-writes it with a hard-coded value anyway.

I'll have to get back to you on this later though, cause the time_scaling is being a real
bastard, and the viscosity_scale will piggy-back off that when its done.