Jump to content

Phil Deakins

Resident
  • Posts

    13,493
  • Joined

Posts posted by Phil Deakins


  1. Penny Patton wrote:

    The only people hurt are those who rent out shop space for stores and malls. But that simply wasn't a sustainable business model so long as LL's goal is to draw in more users. The domino effect described only applies to those whose business model can only be described as "building on sand".

    Your "building on sand" comment is nonsense. The stores that have folded because of the marketplace didn't build on sand. They built on bedrock. Some time later, LL turned the bedrock into sand.


  2. Hippie Bowman wrote:

    Good morning all!  Its May the 1st!  Here is todays history.

     – The first 
     match is played in 
    .

    I think that should be the first international cricket match, and I think it was between America and Canada. Or could it be the first time that a cricket match was played in America. I would think that it was little early for the first international but I may wrong. What it wasn't was the first cricket match to be played :)

  3. When setting a limit that's over 64k, I believe it quietly sets it to 64k. If I'd written that bit of the system, I'd have sent the owner "cheeky buggar" message and set it to only 4k, and laugh while I imagine them trying to figure out why they can't get rid of the stack-heap collisions :)


  4. PeterCanessa Oh wrote:

    Yep, that's it.  I knew you knew that really.

    Except.  My llSetMemoryLimit(4096) Mono script will report as a 4k script, behave as a 4k script and
    be
     a 4k script only as long as it isn't at a party.  As soon as it is it just says
    llSetMemoryLimit(65536)
    , switches from llWhisper() to llShout() and goes wild.

    Shouldn't that be 65535? There are 65536 bytes in 64k but the numbering is 0-based :)

  5. lol. No I didn't know. I did know that a new thing that LL introduced a while back only showed the sum of maximums, and I thought that was rather useless. It was obvious that what Phoenix shows is also the sum of maximums. But when Qie said in a recent thread that customers can now see how much memory an object uses before buying, I thought it was something different that would actually show the correct value, which is why I started this thread. I wanted to know, and now I do - there is no way for a customer to know how much memory an object's scripts use before buying.

    Anyway, just for the sake of it, rather than for any practical value, I now have the memory limit of each of the 4 mono scripts in the object I'm working on set to a little above what they are actually using after initialising, and the object now shoes 75k instead of the sum of maximums (256k) that it showed previously.

  6. I was hoping that Qie was referring to another way than just the sum of max possible amounts.

    Unfortunately, most script memory useage is misleading but I'll set the memory required, if only to check that Phoenix reports it correctly, as it makes no difference to a script's actual useage.

    Thank you for your help, Jenni. It's appreciated.

  7. Ok. I think I have my answer (unless Qie was thinking of another method). The script memory information that Phoenix and Jenni's HUD return are the maximum that *might* be used by an object - the maximum that an object is able to use whether it gets close to using it or not. Pity.

  8. The problem with that is that you're saying there is no way of getting the more accurate script memory useage of an object unless the scripter has set the memory limit, and even then it would be set higher than is actually used. So you're saying that HUDs can't do it, but not in so many words. And yet Qie said it's possible, so my question about that type of HUD is still open.

    I see in my emails that Jenni has sent me her HUD so I'll be able to see for myself :)

    The reason I'm asking is because Phoenix reports one of my objects (one I'm currently working on) as using 192k  of memory (3 mono scripts) and if people actually believe that, they will have been grossly misled because it actually uses less than a third of that. If the HUDs can't do any better, then it would be bad for people to think they can tell how much script memory an object uses before buying it, especially if they judge an object's impact by it.

  9. Thank you, Jenni. I'd appreciate a resend :)

    In the other thread, I'd already not accepted the HUD before you posted that you'd sent it, and I was too embarrassed to say so at the time.

    It was Qie who posted in that thread that we can see how much script memory an object uses before we buy it these days. But, if we can't get any more accurate than the sum of all maximums, we can't see how much memory an object uses at all. That's what I'm trying to find out - waht exactly these HUDs show.

  10. I know about llGet Used memory() Peter. In fact I use it. I'm asking about a HUD that was mentioned in a recent thread and I want to know if it can report the correct memory useage on any scripted object rather that the simple (but incorrect) sum of max sizes.that is reported by Phoenix. I specifically want to know what the HUD reports.

  11. It's not the script time that I'm after, Peter. It's the amount of memory the scripts in an object use.

    Incidentally, I'm reliably informed (by Qie) that setting a script's memory limit is irrelevant, and only any good for reporting. A Mono script can use up to 64k but it only uses the amount of memory that it actually needs, so setting the memory limit makes no difference, except for reporting.

×
×
  • Create New...