Can't temp rez objects with flex prims

Has anyone else seen this problem or is it just me? If I try to rez as temp, objects that contain at least one flexlible prim, the object appears to be counted against the non-temp parcel prim limit and the object will not rez (parcel full message). If I set the flexible prim to non-flex, the same object temp rezzes normally and is not counted against the parcel prim limit.

I'm using a holo-vendor to temp rez various products and the ones with flex-prims cause my parcel prim limit to be exceeded whereas the ones with even more prims, but without any flex-prims, do not.

I've found a workaround that is kinda ugly, but works. If you embed a script in each flexible prim and use llSetPrimitiveParams to turn on the Flexible feature after the object has been temp rezzed, it is not counted against the parcel prim limit.

I will submit a bug report on this if others confirm they have seen the same problem.

Thanks.

I'm not able to reproduce this issue. I have an object which rezzes temporary flexi & non-flexi prims (individually & in various link combinations) and none count against the parcel limit.

-peekay

You are right a Link set that is Physical and contains a flexi prim and also set to temp does count against prim count on your land. Technically you are not suppose to be able to set a prim physical and felxi at the same time. At least that is was was stated by LL. So there are a few bugs there which are causing all sorts of problems from the looks of it.

Yes, the current Work-around for making a physical and flexiprim object should not be relied on. I was under the impression that this "bug" will be fixed in the near future.

Thanks, Gearsawe, but in my case the none of the prims in the linked set are set to Physical, but some are set to flexible and phantom. If I uncheck the flexible feature, they don't count against the prim count, but if checked, they do.

Thanks, Peekay. I should have been more specific in what I meant by "count against the parcel limit". While they don't show in the parcel prim count in the About Land window, if the number of prims in the temp object (with flexi prims) puts you over the parcel normal prim limit, the object will not temp rez and I get a Parcel Full message. Unchecking the flexible feature allows the same object to temp rez OK.

Also note that the linked set is NOT set to physical.

Hmm, I just tried again. I filled my land with prims until it's completely full, yet my test script can still rez multiple temp objects, each containing 14 linked non-phys prims (most of them flexi) without any problems.

Can you try in a different sim perhaps?

-peekay

That's interesting. Thanks for trying this. Now that I know it works as it should for someone else, I'll try some other tests to see if I can further isolate the problem. Unfortunately I don't own any land in a different sim.

I run into the problem whether I rez from a script or by just dragging the temp object from my inventory to the ground. In either case, the problem only occurs when the linked set contains at least one flexi prim. Very curious.

I've been able to work around this problem by rezzing the object with flexi OFF, then setting flexi ON after rezzing.

I finally figured out what was going on. I had some child prims not set to temp so they were counted against the parcel limit, even though the root prim was set to temp. When I looked at the edit window and selected the linked set, the Temporary box was checked, but I couldn't tell the child prims were not temp until I unlinked the set and looked at each prim.

The fix was very easy. Just uncheck, then check the Temporary box on the linked set. That sets all the child prims to temp as well. I got into this problem because I was using llSetPrimitiveParams in a script in the root prim to set it to temp, but that doesn't propagate to the child prims like the check box does. The linked set then looked like it was temp, but most of the child prims were not.

In the end, it had nothing to do with flexi prims. I was being fooled because I was using the checkbox to temporarily set the temp off while editing the flexi params, then setting temp back on. That action simultaneously set all the child prims to temp and the problem went away.

This closes out the issue. Especially thanks Peekay for trying to duplicate the problem. Knowing it worked OK for him led to me investigate further.

Thanks all.

I was glad to find this posting, but am still wondering about the fix.

In order to save prims on my sim, I've been loading certain trees into an auto-rezzer that I created. The trees are set to rez as Temporary, and they do indeed have flexi components. I've not used the script to set the linked set to temp on rez. I've done this manually to the object before tucking it into the rezzer.

In spite of this, as soon as I set a handful of these beasts out, I got that darned SERVER FULL error. It showed that there were still over 1,000 prims left to be used on the SIM, and yet this error continued to show.

I've taken the object out, and turned Temporary off, then back on, manually in the linked set. Still seems to be a problem.

I also notice latency issues (both client and sim), and while the script I'm using to autorez reports very little impact against the sim, my guess is the cumulative effect of a handful of objects with timers firing off every 40 seconds is creating the latter.

Not entirely sure where to look next here, and would be happy for any insight that someone might be able to provide on a better way to approach this?

Thanks a bunch,

Sue.