Phantom Avies....

Does anybody know how the new phantom devices work? I know it's a bug but can't figure it out for the life of me. Well I really don't have my hopes up that someone will post the secret on here. But I'm hoping if someone out there that knows how to do this would provide or sell this script to me that can be turned on and off vial llLinkedMessage. Thank you in advance

llSetScale is used in some of the ones ive seen but the really really nice ones.... thats a secret .

oh and llVolumeDetect is *mostly* dead but it use to be the best way

Actually tried llSetScale using with a timer. Couldn't get it to work. Must be missing something... Hmmm.

Using llSetScale for this actualy does bad things to the sim. llSetScale is an ugly hack, llVolumeDetect was a bug. They should have just left us with the volume detect bug. It was clean and simple.

You know, even though I have no interest in this, I'm tempted to experiment just to put that "secret" into open source... LOL!

/esc

Sitting on an object that uses llVolumeDetect makes you phantom, too.

sitting on a object makes u basicly collision less any way no need to use llVolumeDetect()

We used to use it for visitor counters and stuff to get rid of the sensors, but was working on one the other day and it was only working half the time..

A new phantom avatar exploit ? I was heart-broken when they killed the first. Now I keep getting stuck in rezzing buildings again as I attempt to fly past. Thats all I want it for, honest, guv !

I've gotta have this new one !
(taking notes about faint clues in forum and planning experimentation while scratching head)

Meanwhile, you could vote for my feature proposition
https://secondlife.com/vote/get_feature.php?get_id=170

Proposition 170 requests solution to fly-past problem.
The initial suggested method is that any phantom that has been flying at full speed for 3-4 seconds becomes phantom till it stops. Please post other suggestions to the proposition thread.
/13/13/42951/1.html

This limited suggestion attempts to respect LL's obvious aversion to a simple "go phantom" capability. Though in my opinion the reasons for denying us this are not entirely rational, I can see the thinking behind it - I guess huge numbers of the worst griefers are not very bright ?

I'm sure there are better ways, so maybe you could post them to the Proposition's associated thread .

blah blah blah, setscale is much better than volumedetect because instead of being phanton and registering collision, you dont register collision at all. this means that all bullet guns that require collision to push (seburros and the like) do not work, making it one of the most effective shields against all guns besides sensoring pushguns. And BTW, even though it isn't hard to figure out i'm selling them in game, pop an IM on me.

Any gun worth its salt wont rely on just collision push bullets .

maybe not a scripters gun. My "good" guns dont, but you would be surprised at how many guns there are that DO rely on only collision. Its still better than the old volumedetect bug.

Actually, they acted pretty much identically.
The main difference is, the llSetScale hack puts a noticeable load on the server (all that updating). The llVolvumeDetect bug at least was a passive misroute of the collision information.

At some point in the future, we need a library call that can phantom an avatar as it's function, useful for various things as it is - and add the ability to prevent it by plot of land so it cant be used as a games cheat. Something official is bound to be better than this bug explotation.

acutally, you are wrong. There is no "all that updating" involved with the setscale hack. if you think putting rapid setscales into a timer is what causes the hack to work, you are mistaken. Try boiling down the trick to its roots. My phantomizer doesnt lag sims at all, only as much as a single set scale call. imagine that! I'm giving too much away here

But yeah, it would be nice to instead of having to set your land as no script being able to set you AVATAR to no script / phantom. That way, we could all avoid getting shot while still being able to work and play (although we would not be able to use scripts in attachments). doubtful implementation though.

P.S. They didnt act identically. There was a major difference, with volumedetect your avatar still registered collision from things like bullets, with setscale, you dont. Its like your avatar's bounding box isnt really there. or something

I used the llVolumeDetect bug all the time, push bullets never went off, they just passed through me. *shrug*

as for the hack's working.. I don't know. I've never seen one that didn't constantly pass scale updates. *second shrug*

okay im really beating a dead horse here, but mine uses only one setscale call.

Yes, you mentioned. I said that I didn't know about it, as I'd never seen one that does it that way. So, I'm not sure what prompted you to repeat that.

did i mention i use only one setscale call!?!

Think 2D. Imagine a bounding box from (0, 0) to (9, 9). Now imagine a bounding box from (9, 9) to (0, 0). Hmm... I wonder...

How about instead of playing childish "I have a secret and I'm not telling!!!" games, you use the scripting forum for its intended purpose and just post how it's done?

it probably uses an ulta low mass prim. A prim that has been tortured into having no mass at all. There are ofcourse a number of ways to making said prim. One simple way is to take a torus, then tapering it, cutting it, advance cutting it. hollowing it, then finaly setting holesize x & y as close to zero as possible. This should give a very low mass prim.