Flexible no longer simulates phantom?

Either I am brain dead or something has changed. In the past one could make a prim flexible to make it phantom without having to actually make the prim phantom. This was a trick I have used to link phantom prims to a build in the past.

Yesterday, I linked a large build together that has some flags (true flexible) on it. The entire linkset kept going phantom on me. After some investigation, I found that the flags I made flexible are now marked phantom and non-physical. These boxes are grayed out so they cannot be changed.

I checked some old builds, and using edit link parts, the flexible prims I used in them are still okay (not marked phantom). I created some new flexible prims, and as soon as I checked them flexible, a check was ticked on the phantom box, and the phantom box and physical box grayed out preventing change.

So, is anyone else seeing this, or am I nuts?

Bracken

I presume your floopies aren't the root prim.
I just went in and made four rectangles, made one floopy, linked them, turned linkset physical - everything worked as expected. What else can I try?

Did you try turning your build non-phantom then making select prims floopy?

try making just 1 prim. Go to features, click on flexible paths so it is checked. Go back to object, and look at the phantom box. Is it checked and grayed out? Is the Physical box unchecked, and grayed? That is what is happening to me. Linking this prim to a build is forcing my builds to go phantom. I can uncheck phantom on the build, but after a few minutes, the build goes phantom again.

Bracken

Floopies can't be physical and are always phantom so... I'm not sure what the difficulty is. They work as expected by me in linksets.

Hmm, well thanks, I am not sure what is going on. My linkset is strangely going completely phantom after a few minutes of being linked. I can uncheck the phantom on the linkset, and everything is fine for a few more minutes before going phantom again. Prior builds using flex prims seem fine. I will continue to investigate this. Again, thanks for looking into it. It is obvious something I am doing.

No, it might be something weird - we live in a world of strange magic ;-D

I'll try leaving a linkset alone for a while then poking it to see what's up, if anything.

Hi.

I face a somewhat similar problem as reported by Bracken. Within another thread i have posted a script snippet which dealed with combining phantom and non phantom objects into one single linkset. The published trick worked great for me until about 2 weeks ago:



Then suddenly it didn't work any longer:



I bet that this is the same issue under the covers: As soon as the linkset is created, all linked objects turn phantom if at least one child-prim(!) has got llVolumeDetect(TRUE). So Bracken... You are not alone. There are already two of us ... It doesn't help but it proofs that we are not completely disoriented

BTW i am using the RC-viewer and sometimes i use Emerald. That might be relevant for this particular issue. Maybe i have to try it again with the standard viewer.

cheers,
Gaia

What I get is:

Create linkset, make one prim floopy, rest of prims are solid, the floopy one is phantom.
and
Create prims, add volume_detect script to one, link the prims, the scripted prim is phantom but the rest are solid.

However if one links then adds the volume_detect script to a child prtim the linkset turns phantom.

Osprey, Thank you for sorting out this one

I can now confirm, that the order is important. So everything is OK
in my case at least when llVolumeDetect() is applied BEFORE the object
is linked to the linkset. (And of course the object must not be the root)

Thanks Gaia and Osprey.

Unfortunately I am not trying to use a script to make a prim in a linkset phantom. All I am trying to do is link a flexible prim to a linkset without making the whole linkset go phantom. I have done this numerous times in the past (specifically the use of flex curtains as room dividers), without a problem. I have rechecked all my old builds with flex prims in the linkset, and they are fine (although I haven't tried unlink and relinking to see what happens, which I should).

I will keep looking for answers. Thanks for the input.

Just knowing he screwed up somewhere,
Bracken

I have a similar problem today.I am trying to make 2 prims phantom in a link set of 11 but try as I may when I link the set is all non phantom.I have tried making the 2 prims flexi but it will not work >I will have to find the script mentioned earlier.

I just revisited this and tried linksets with flexibles.

In addition to what Osprey writes i noticed that the whole linkset turns to phantom when you change a part of the linkset from non flexi to flexi.

And in order to verify that the linkset keeps in its state over time i relogged after a couple of minutes to verify that nothing changed.

As i mentioned i use the RC client and maybe that matters ?

Hmmm, from the two of you, it appears it might truly be the order I am doing things. I will do some experiments tonight when I get home. I can't remember if I made the prims flexi before or after linking. I know they are not root. I will do some work on them tonight and let you know how it went. Again thanks for the help.

Well, sort of - yes, it turns Phantom, but you can untick the box and it goes solid with the floopy bits staying Phantom.

Hi


re read your reply and followed the link to your script.I tried it out and lo and behold it worked for me.I took a copy and rezzed it and it broke.I tried shift drag and that worked

.I have been in a sandbox for an hour rezzing multiple copies and all seems well now,both copy and shift/drag.Thank you so much .I hope it works again for you.BTW I am useing snowglobe.

Thanks to Osprey i was able to understand that it was this little detail of which i did not take care:

IMPORTANT NOTE: This method works only if the script is applied to the prim BEFORE it is linked to the linkset. Otherwise the whole linkset turns phantom.

I added this note just a couple of hours ago to my original contribution. So it works for me again now

Well last night I relinked the 200 prims of the whole thing, adding the flex flags to the linkset last, and the linkset did not turn phantom on me. Later I added a couple more prims to the linkset, and the set remained stable. I am not sure what happened the other day, but everything appears to be working normally as it should now.

Life goes on, prim by prim,

Bracken

no offense but discussing i nthe forums won't get this noticed by the lindens. take it to the jira and you will get answers from a maintenance linden.

yeah no offense, but Linden attention is rarely helpful... and generally residents know things are broken before they do, not to mention how to work around it if possible. LL has yet to figure this out, evidenced by their nerfing of these forums. jira's fine if you want to report something broken, but it's the residents that are up to speed. Jira might get it fixed.. eventually (or not) but I'd never count on finding a linden provided solution there.... in fact it's rare that they might do more than just comment that they read it.

Things aren't always broken. It's useful for us to help each other - even just confirming that whatever is going on is reproducible, let alone coming up with workarounds or alternate methods. And we are usually quick.