Bug in new viewer phantomizes prims

Here I thought I had the pool problem solved. As some may recall, when I started out I wanted to make a linked pool and retain the phantom for just the "water." I succeeded by making the "water" a flexi prim. It was great. I had held back making any more designs to pursue scripting.

By pool btw I mean a standalone of about 5m diameter and not a large one set into the ground etc.

So the other night I made a quick pool, and guess what?

If you take it and rez it, ALL the prims are phantom! Unless you unlink and re-edit the other parts - which I wouldnt want recipients to have to do. Have to unlink; when you look at the prim object properties via edit linked the phantom selection is greyed out.

Of course I need to link these together - people are going to move and position their pool once they plop it down on their deck or in their yard.

This is NOT good!

That really isn't new. I have had that happen for a few years now. But rezzing a sculpty or flexi prim will generally will make it phantom by default. Annoying but true. As for prims phantoming, this has happened as far back as 2+ years for me. Almost always the base prim, for no reason, will phantom on me. I now am in the habit of linking my base prims either as a ceiling or wall, something you won't walk over. Why this happens, no clue. It resulted in me having to remove and delete the prim, and clone in a new one. Nothing in the attributes, just happens.

Holocluck, not to say I told you so, or to sound rude or anything, but as about half a dozen of us told you in that other thread, linking the water to the pool is an unnecessary complication. Pretty much nobody does that. The most common thing to do is to have the pool rez/derez the water on command. It's also very easy to script the water to keep itself centered, or in whatever position you want, relative to any prim in the pool. These things are standard practice in SL, and believe me, your customers will not be confused by them.

What you're trying to do, on the other hand, is very non-standard. It's not surprising you're having problems. Don't reinvent the wheel.



In any case, it's unlikely that the viewer has anything to do with the issue. It's more likely the recent server update is the cause of the new behavior. Collisions are a function of physics, after all, and physics only exist server-side.

Well, I was warned of odd properties but this did not occur before for me after about 3 pools and several rezzes.

As for rezzing water into an empty pool. It might be nice for some but I don't find it very helpful when what is filling the pool is part of the attraction and (hopefully) appeal. Call them art pieces or novelties: these pools aren't conventional and they should be displayed complete.

This scripting to hold it in place sounds much more helpful (as long as it doesnt effect any other scripting I have in mind like morphing the prim), but I had never seen anything like it and I dont recall it mentioned. I tried one of those Rez F's early on and for some reason following the directions to a T did not work.

If as Atom said only the base prim is vulnerable, perhaps I can get around it by placing a small, invisible prim somewhere against the pool.

OK, so you don't want people to be able to derez the water, got it. How about this then? Script the pool to rez the water immediately after the pool itself is taken form inventory, and script the water to follow the pool wherever it goes. Done.

As for why you couldn't get Rez Foo/Faux to work, the only explanation is you must not have followed the instructions quite so "to a T" as you had thought. You must have missed something somewhere. I use Rez Foo practically every day, and I've never had a problem with it. I've never used Rez Faux, but from what people say, it works just as well.

lets say I could live with a script which rezzes the water immediately after the pool is taken from inventory. The other script sounds great.

What I also didnt like about the Rez Faux (I think it was) is that it always had some object with it, a prim which everything was bound to. If the sequence of linking prims can control the bug and destermine which extra single prim becomes phantom, I think that's a better way to go.