Flexiprims will make more Henthai Tentical Monsters!!!

Don't worry Torley, just upload "watermellon"!

Just, please, not

<font style=color:lime;background-color:turquoise>lime green (avs) on turquoise (one's objects)</font>

Here's an example of what this looks like (or just look on your minimap).

Hehe I already saw a patch of tentacles that were scripted to flop over nearby anyone that walked near. It was really gross.

You're welcome!

You can find the code in this thread. ^_^

I can finally realize my dream of destroying SL with a gelatinous, quivering, mile high Cthulhu.

on edit: it appears I've been beaten to the punch.




damn...

IA! IA! Cthulhu! IA! IA! Shub-naggurath!

The Goat with a Thousand Young! IA! IA!

OMG what a cool litttle black page with diarrhea of tiny little colorful letters. I did a find in that page but didnt find any link to a hidden baby_chibi_amoeba_tenticle.

oh sorry is it offtopic already?

Which doesn't work; "f" isn't defined within scope on this line:

That's a keeper.

*snork*

Sure it is. You're right, the code doesn't work... it needs to go in the usual sensor framework, I didn't include that because it's obvious and everyone has their own. You'll need at a minimum a state_entry that kicks off the llSensorRepeat.

You're misinterpreting the error message. It's not that f isn't defined, it's that set_force isn't defined.

I left it out because because set_force has more tentacles then the secret screening room at an Anime convention.

The API for flexible prims is not well behaved, and the way PRIM_FLEXIBLE works is clearly in the processes of gelling, and my code for set_force in 1.9.1.13 may or may not work in 1.9.1.15 and may or may not even be the best code for 1.9.1.13... figure it out when the grid comes back up. Hack your own version, without looking at my uuuuugly code, you'll probably end up with something better.

Um, duh. Note how I didn't mention that as being the problem...

That's not what the error message says...

As far as I know, the PRIM_FLEXIBLE parameters have not changed since their inception. Hence, your copout excuse for shoddy code is moot.

That's correct. Not only did you misdiagnose the problem, you missed the other ways in which the code fragment I posted was incomplete.
Yes it is. The problem is that when a function is missing the error cursor points to the end of the parameters to the function, not the function itself.

I guess you don't actually write much code in SL, or you would have caught all of this. This stuff really is obvious to any active programmer. I'll keep that in mind when reading your messages in the future.

Noooooo... 'v' and 'r' are also undefined!! Augghh *gurgles and screams* *dies*

.... there is nothing to see here.

I didn't miss the other ways because they were obvious and unnecessary to mention.

However, that's now what the error states.

I never claimed I was a programmer. If you're going to post code snippets, at least have the decency to post WORKING code with ALL variables defined.

Quit being a troll, troll.

Henthai Tenticles ---> reduced to shortened form ---> hentacles

This has been a public service announcement.

I post snippets for the benefit of programmers. Anyone who can't take a couple of lines describing an algorithm and turn it into working code in a couple of minutes isn't part of my target audience.

I'm beginning to understand why Knuth went to the trouble of defining a toy computer to describe his code.

PS: Next time I get that kind of bogus error from LSL I'll bug-report it.

I feel I've been enlightened.

Pastafarianism is starting to make more sense.

i need help

i have

float last_f;
float fudge = 0.01;
//...

default
{
state_entry()
{
llSensorRepeat("","",AGENT,4,PI,.5);
}
sensor(integer n)
{
vector here = llGetPos();
vector f;
vector v;
float r;
while(n-- > 0)
if ( fudge*fudge < (r = llVecMag(v = llDetectedPos(n) - here) ) )
f += llVecNorm(v) / (r * r);
if( fudge < llVecDist(f,last_f) )
set_force(last_f = f);
}
}

but i still get that f is not defined withen scope
i also added f = llDetectedPos but i still get the same error

It will take quite a craftsman to doft all the overfiend textures.

Isn't it Hentai?

I see a new internet poll being made:
"Which tentical rape hentai movie are you?"

I'd so be Inma Seiden.

Congrats. You're the first person to actually notice that. I'd give you a cookie, but I'm fresh out.

Isn't it tentacle?

Heh...

1. last_f should be a vector. This isn't the bug, it's another problem you'll hit when you get past this one.

2. it's not f, it's set_force that's not defined. The error message is misleading, it's pointing at the end of the parameters to set_force, not the variable f. They just happen to be the same location.

[imagine a long rant here about the quality of the LSL compiler]

Anyway, those places where I have "//..."? There's code missing there, 'cos the point of this code snippet was to explain the algorithm for the force on the tentacles.

set_force is the tricky bit. Ideally, it should be something like...

set_force(vector force)
{
  list p = llGetPrimitiveParams([PRIM_FLEXIBLE]);
  p = llListReplaceList(p, [force], OFFSET, OFFSET); // Check the release notes for the value for OFFSET
  llSetPrimitiveParams([PRIM_FLEXIBLE]+p);
}

... but that doesn't work, or it didn't in the earlier versions and I have had too many other problems since 1.9.1(16) to mess with this. The code I came up with works but it's full of commented out code, redundant code, and other nastiness.