Jump to content

Ann Otoole

Resident
  • Posts

    4,840
  • Joined

  • Last visited

Blog Comments posted by Ann Otoole

    A Farewell From Jack

    Best of luck in future endeavors Jack.

    Although I will say I'm a little concerned. We now have no means of discussing commerce related issues and concerns other than some CSR that infrequently appears in a restricted forum. My concern now is what? Bob Komin makes all decisions about every little thing at LL now? Is there a restructuring announcement due out to explain how things now work at LL?

    • user wants to run 4 sessions at once
    • user runs sl, sets cache to xyz1, logs to lxyz1, restarts client
    • user runs sl second time, sets cache to xyz2, logs to lxyz2, restarts client
    • user runs sl 3rd time, sets cache to xyz3, logs to lxyz3, restarts client
    • user runs sl 4th time, sets cache to xyz4, logs to lxyz4, restarts client
    • user gets done, closes sl clients
    • user loads sl client. cach now set to xyz4, logs to lxyz4

    Is that about right?

    I would recommend using separate configuration files and load them on the command line of the 4 sl client shortcuts. Otherwise there is still room for issues. And given what happens with cache/log settings under certain circumstances it might be wise to load a custom config on the command line all the time anyway.

  1. 
    

    ...

    The issue with multiple instances of the same viewer is different, in that case the trouble is that only the first instance is given write access to the cache, the rest are read only if they do not get their own folders. The third party viewers share this limitation and Torley's advice applies to them too.

    Torley's suggestion has zero to do with running multiple instances at the same time. There is no fix for that. it isn't even possible in a reliable manner. Maybe with a command line parm to load a different setting file for each instance you want to run. Eventually something hard coded to the default is still going to bite anyway.

  2. So what? making separate cache folders to prevent numerous issues predated Emerald's creation of it's own folder. And that was done immediately after I had a convo with the emerald developer about the need for each viewer to have it's own folder. Every viewer version written by whoever has issues with cache. If you think about it then you might see why.

    LL needs to make all versions create their own cache folder. So do all TPVs. Problem solved. In the meantime we users have to manually accomodate this defect ourselves. Oh and how's that reset cache working out? You know the one. It resets cache location to default and you have to go manually delete the cache and go reset the cache location again and what happens is people wind up all using the default again. So yes LL needs to address this with a separate cache location on a by version basis. And not reset cache location on reset.

     

    too many defects.

  3. We have been advising people to do this for years. Here in these forums and elsewhere. What Emerald did was the correct approach to eliminate this defective viewer feature. Emerald installed it's cache to it's own unique directory. What LL needs to do is each viewer create it's own unique cache folder on install. Problem solved. The fact some TPVs have been doing this for a long time should tell LL something.

  4. Yea. But the admin menu is disabled (greyed out) until you enable it in debug settings.

    Minor annoyance. For me. I always have to set debug settings to override LL limits on the appearance of SL so it is just one more to add to the list of tweaks to make SL look good on a modern day video card.

    BTW could you please remove the hide url option for urls. We need to see the urls before we activate them. There is no reason to hide them since the url can be acquired anyway. Hiding them allows people to put nefarious urls in and unwitting residents activate them.

    I'm surprised you guys remain unaware of commonly used features and then go cause people problems by removing needed features.

    But you apparently have bigger issues atm.

    See: http://blogs.secondlife.com/message/524998#524998

    Something about all IMs coming from one of your outsourced programmers called Grumpity ProductEngine. Assuming it is a real defect of course.

  5. There is a debug setting to turn admin menu on called AdminMenu.

    Admin Menu is on the developer menu. Advanced-> Show Developer Menu (ctrl-alt-q). or is in the prefs now.

    Odd that LL is hiding more things while they say having to go to debug settings all the time is a problem. I think there are a few aspects of admin menu that need to be brought to advanced. Like teleport anyone, show urls regardless of parcel owner preferences so we can see what urls are being offered and decide if we want to run them instead of being expected to load unknown URLs. (infantile to hide because anyone can still get the uber sekret radio station url with available O/S commands or utilities), fly if we want, etc. But the other admin menu stuff can be hidden as far away as LL likes since they are the only ones who use it.

  6. You are still giving large parcels for businesses you like a boost even when they should not be boosted because their products are fewer and inferior. It is called forming trusts to control an economy.

    Also Jack thanks for admitting you give free advertising to your friends like Ozimals. You stated this clearly at your office hour today. Everyone in SL paying tier to support a business needs to understand LL gives unfair advantage to LL's friends. It is called forming trusts to control an economy.

  7. I'm talking a single character title. Anyway LL makes enough money to pay for an SQA department. If LL wants to pay a L$1000 bounty per defect that is confirmed then I'll register defects.

    Edited to add: Stuff like this should fetch a bounty: http://blogs.secondlife.com/message/466955#466955 because it is, or should be, embarrassing.

     

    Update: Figured one out. There is some odd behavior not present before that indicates the code has been made overly complex. In addition the tag now only displays a few characters followed by a question mark. So basically group tags are now useless. Too bad Kirstens has so many issues now. Oh yea nice job disabling anti aliasing LL. It used to work. That should tell the board something.

  8. Drop your view distance to 128 or less.

    Try to find a mesh region that is not full of the gigantic models that LL needs to delete. Maybe one of the outlying regions and stay over on the outside edge so the giant garbage pile in the middle won't hose your up.

    LL needs to slap some limits on that stuff unless people start learning how to set the scale correctly in the modeler and make the models sized properly.

  9. I'm not having any issues right clicking models. In fact almost all of them rezzed in the beta grid are set with these permissions:

    meshpermsnotice.jpg

    Note that this applies to the mesh object that appears in inventory. If you create a sculpt, apply the mesh asset, set stitching to mesh then the permissions are how you have them set to default.

    I.e.; most of what is rezzed in aditi can be copy taken or moved around by anyone. LL might want to change that behavior before this goes live.

     

    What I do advise is to not view bounding boxes unless you want to be impressed with the largest array of bounding boxes you have ever seen. And then crash lol.

  10. It is great. As long as you are looking for the 24*7 fake never ending model contest spam that is actually an ad for a store. Maybe you guys need to be moderating the events system and dealing with the fake events if you want people to use it. I'll probably be looking at http://virtualadvisor.ning.com/events for events because looking in LL's events just pisses me off and I log off.

  11. 
    

    Medhue: I made a jira last night about the avatar becoming distorted after detaching a skinned avatar (without bone offsets). It's a new bug that wasn't there months ago.

    https://jira.secondlife.com/browse/CTS-261?

    
    

    PERMISSION VIOLATION

    It seems that you have tried to perform an operation which you are not permitted to perform.

    Guess we are not allowed to see that "CTS" type jira.

×
×
  • Create New...