#SL Texture Loading Freeze

by

SH-2738 – Texture fetching freezes due to LLcurl. If you have seen textures refuse to download and/or rez completely you may be having a problem described in SH-2738. (There is no link because the JIRA item is one of the Lab’s private items. I should point out the JIRA tends to make items in some topics private, unless the Lindens remember to override it.)

Whatever the reason for privacy, this fix was included in an SL Viewer 3.2.5 build. Presumably it is in the Beta version of the viewer (246559) and later, but I can’t be sure. If you are having texture loading problems you may want to try the Beta version of the viewer.

Remember. The Beta is a beta and there is no guarantee it will work. It is a testing viewer, which means no whining about it. If you have a problem, file a JIRA report and send in your crash logs.

A related texture problem SH-2512 – Some avatar textures in welcome area never load on first visit. Could also be in this Beta release.

SH-1912 – Shiny metal texture characteristics entirely lost when Lighting and Shadows turned on. This fix could also be in the 3.2.5 version. Runitai made this fix in the Shining branch about 2 weeks ago. I see where it made it into the Dev Viewer (branch) about 12/12.

 

 

Firestorm-Phoenix QnA

by

The Firestorm-Phoenix team is going to have a Question and Answer secession this Saturday. The announcement is on the Phoenix blog.

Firestorm Release

The meeting is at 1 PM SLT in three regions; Rockcliffe I, Rockcliffe Library, and Agile 3D. Arrive early and divide up by name:

Check your script weight before linking. Get it as low as possible.

Bring your questions about the viewers and their future.

If you can’t make it, they will have a video available later.

#SL Server News Wk 50 Cont

by

Main Channel

This week the code from Le Tigre/Magnum rolled to the main channel. This is a server maintenance pack. It includes the LSL function llTransferLindenDollars(). The thread that links to is now about 5 pages long. The details of the function are:

  • Attempt to transfer amount of L$ from the owner of the object to ‘id’. Requires PERMISSION_DEBIT. Returns a key used in a matching transaction_result event for the success or failure of the transfer.
  • New LSL event: transaction_result(key id, integer success, string data) This event is triggered from an llTransfer* call (currently only llTransferLindenDollars).
  • id: matches the return value of the llTransfer call and if the transaction was a success will match the ‘transaction id’ shown in transaction history on secondlife.com
  • success: TRUE if the transfer succeeded otherwise FALSE.
  • data: On successful transactions will contain a CSV of destination ID and amount transferred. In failure cases it will contain an error tag on failure.
  • Error Tags for llTransferLindenDollars:
    • LINDENDOLLAR_ENTITYDOESNOTEXIST – The destination UUID is not a valid agent.
    • LINDENDOLLAR_INSUFFICIENTFUNDS – The source agent does not have enough L$ for the transfer
    • INVALID_AGENT – Destination agent is not a valid UUID
    • INVALID_AMOUNT – Amount is <= 0
    • THROTTLED – The scripted L$ throttle was hit for this object owner.
    • MISSING_PERMISSION_DEBIT – The script does not have debit permission
    • GROUP_OWNED – The object is group owned and thus can’t give money
    • TRANSFERS_DISABLED – L$ transfers are disabled in the region
    • EXPIRED – The simulator timed out waiting for a response from the back-end service.
    • SERVICE_ERROR – There was an error connecting to the back-end service

    Read more

    #SL Large Groups Won’t Load

    by

    It seems there are some long term problems with large groups. Seems a large group is 12,500 members… yeah that’s a large group. Some people have pointed out in JIRA SVC-4968 that some much smaller groups run into similar problems.

    One user, Point Luminos, suggests that computer resources are the problem, not the viewer. Point has a rather modest computer, Duo Core2 E7500 with 4gb ram. Point tells us that he/she is editing a 36,000+ member list each day without a problem.

    However, users with more computer and smaller groups are running into the problem. That is more as in newer CPU and more ram. So, it probably is not just a computer resource problem.

    The comments are arguing about whether it is a resource problem on the client or a bug in the SL system. Since some can edit large lists and some can’t edit some not so large lists it suggests another problem than just a size limit or computer hardware.

    Read more

    #SL Mesh Pivot Point

    by

    Getting pivot points in mesh has been a bit of problem. If you have ever made doors in Second Life you have probably run into pivot point problems. Creators working with mesh have the same problem.

    In 3D modeling programs we can set where we want a pivot point. The problem is that information does not upload into SL. So, there are ways to work around that problem. One of the simplest I’ve seen is here: Mesh pivot point?

    Drongle McMahon provides a link in a response post in the thread. it leads to: Change Pivot Point of Mesh which provides more information on moving a pivot point. Drongle made the older post and it is an excellent explanation and ‘how-to’.

     

     

     

    #SL Mesh UG Changes

    by

    I see that Charlar Linden, the facilitator for the Mesh Upload group, has broadened the focus of the UG (user group). The more official name is Content Creation/Mesh Upload User Group. The group meets Mondays at noon (PST/SLT) in Borrowdale, Nyx Lindens place. Check the group’s wiki page for meeting time and location changes. I expect this location and time will be good for some time to come.

    The wiki page contains the meeting agenda. Residents can add items to the agenda by logging in and editing the wiki page. The agenda is 99% plain text, so it is easy to edit.

    The post is also somewhat an official announcement that the Mesh Project has shifted from development to maintenance mode. I suppose that is some type of milestone.

    The post appears to be worded to generate conversation on what the group should be focused on. As there has been less to discuss about Mesh it is becoming obvious that time is available for other topics. You can join the conversation here: Mesh UserGroup expanding to cover wider Content Creation agenda – input needed.

    Read more