Nalates Urriah

You can track regions in the SLUniverse thread: http://www.sluniverse.com/php/vb/virtual-business/8523-new-sl-sims-past-week-63.html

You can either learn more about LSL or dig through a Script Library and find something that does what you want. There is a group named College of Scripting and Music that has a building in SL. They have 6 or 7 floors of... posters... visiual examples of each LSL function and how they are used. In some cases they have working examples to show the functions in action. It makes learning scripting much easier. Builders Brewery is a group that teaches building and scripting in-world. There are a number of groups that teach scripting. A free program LSLEditor makes scripting much easier, IMO. It has some bugs but is the best debugging tool I have found. The manual is a bit weak on how to build projects (multiple scripts that work together). For anything other than projects it is intuitive.

There is a problem on ADITI. If you recently changed your password, you may have the problem. See JIRA item SVC-7727. Please add your information and viewer details and click WATCH. There are some steps in the JIRA you can use to get around some of the problems. Maestro Linden says they have a fix for the problem. It just has not made it into the QA queue. So, it will be some time before we see it roll to the ADITI grid. In ADITI there are a large number of server versions running for various tests. I have problems uploading in Pathfinding regions. I can upload in other regions. Some viewer versions will NOT upload regardless of regions. A previous Dev Viewer version had that problem. You will have to experiement and see if something works for you.

If you have started using Microsoft's Skydrive that could be the problem. Search here for Skydrive and see how others have fixed the problem. It is possible to run SL and Skydrive at the same time. Also, you say you have a Viewer 2, current viewers are versions 3.3.x. Unless that is just a slip on your part, get a newer version of the viewer. There are a couple of versions of the viewer that crash on upload attempts. When you ask a tech question include information about your computer and viewer. Get the info from the viewer's Help-About... and paste that into your post with your question. To add your info to an existing question use OPTIONS->EDIT. It’s in the upper right of your post.

Open Help->About Second Life in the viewer either before or after login. You will see the first line says something like: Second Life 3.3.2 (259040) Jun 6 2012 17:24:17 (Project Viewer - Pathfinding). I happen to have the Pathfinging Project viewer up when I saw the question. The bold part is the 'brand' and version with the build number in ( ). If you ask a technical question here use ALL the info found there in your post.

Here is a link to Perrie's recommendation: Can I Run It When you ask a tech question include information about your computer and viewer. If the viewer will at least show the login screen, get the info from the viewer's Help-About... and paste that into your post with your question. To add your info to an existing question use OPTIONS->EDIT. It’s in the upper right of your post. Otherwise, on Windows click Start and type DXDIAG, case doesn’t matter. That will open the dxdiag in the panel. It will give you your system specs. We need to now video driver version, OpenGL version, …

Rolig's answer is good and the likely solution. Along with her recommendation to rez a cube, try standing and looking in different directions when you attempt to rez. They were talking about the problem in the Beta Server group meeting today. Because the rez point is selected by the viewer figuring out where you clicked, the direction you are looking has an effect. The solution to the problem is running on Magnum Release Channel, if I remember correctly. If your region has a bad case of the problem you can ask that it be moved into the Magnum channel. Next week or the week after the fix should roll to the main channel.

The region idle has been running across the grid for over a week. Le Tigre has been running the same code for over a week. You need to look for another cause of the problems you are seeing. Region Idle should help your region's performance or make no difference. In the time frame you are considering, I think the significant change is the viewer version. Also, a significant change is IPv6, which could make a difference depending on your ISP and location. See: Happy World IPv6 Day

See SVC-7727 in the JIRA. Visit the JIRA and add yourself as a watch and provide your data. Yes there are a number of problems with ADITI. The fix is in the QA backlog, or so I am told today. Last Location does NOT work at all and may prevent your login. Try logging in using a region name you know. Try Morris or PathtTest1, PathtTest2, PathtTest3, and PathtTest4. Depending on when you last changed your password ADITI may be almost unusable. You won't be able to rez recent items from AGNI that are in your ADITI inventory. Seams like about 30 days old is the limit. Nor will you be able to save things to inventory. They save but are gone on next login. Your clothes will be stuck to whatever you were wearing when you changed your password. It is a pain right now. There are a load of things behind schedule in QA so things are backed up and ADITI is a low priority. Also, I can't upload mesh with the latest Development viewer anywhere. But the main viewer works except on Pathfinding regions, which are now all Premium and Snack sandboxes in AGNI.

The technical term for Iam is wackadoole... The first thing to test is your connection. I have been logging in and out between AGNI and ADITI all day and not having a problem. Run these tests and figure out if it is you, SL or one of the ISP's inbetween that has a problem. If it is not a connection issue you can move on to other tests. Troubleshoot Your #SL Connection I Can’t Login - This covers some oddball SL problems like ghost avatars and how to do your own ghost busting. There are a number of reasons one cannot login. We’ll start with the easy things first. Check the Grid Status and make sure it is not an SL outage. http://status.secondlifegrid.net/. Some group tag used to have characters from the extended character set. The viewer seemed to have a problem with them. You can look at your groups in my.secondlife.com. If you have a group with strange characters in the group tag, leave the group or contact the group owner and ask them to remove the extended characters.

It sounds like you think you are talking to the Lindens. You are talking to other users of SL. The problem is in your cookies. Clear all the cookeis out and try your experiement again. Also notice the servers you are connecting too. The Community server will ask about cookies different than what the ID server asks for. Don't be surprised that it gets confused with alts. I can log into SL with the viewer with one AV and the forum with a different AV... at the same time. It should be possible for Mom, Dad, big brother, little bother and baby sister to all login from different computers in the same house using the same IP address and have everything work well for them. They try to keep track of things via cookies spiked into the individual computers.

I just saw this problem when trying on mesh hair at TRUTH (Amelia or Auralee Do... I forget). One of the Do's failed and displayed a bunch of those little pyramid icons. I was using the Second Life 3.3.2 (258114) main stable release. I assumed the region was lagging or some other problem. EDIT----- Actually in this case is does seem to have been the region. Trying the same demo at home (different region) it rez's.

Rendering the avatar is a special case. It is a more complex process than rendering in the rest of Second Life. The idea with avatars is to save CPU cycles on users' computers and the SL servers. The idea requires your viewer to download all the textures that make up your avatar and its clothes; a shape, skin, top, pants, hair, and shoes textures. The viewer ‘bakes’ those into a single composite texture. You see your avatar render nice and sharp when that bake completes. Then your viewer uploads that composite texture for all to see. That saves others downloading all the individual textures and baking them. Your avatar goes blurry as it downloads and decompresses the composite texture you just uploaded and it becomes sharp when that process finishes. You are the only one that sees the double blurry for your avatar. If that process hangs or fails there is a problem. Where it fails affects what you or others see. You can try the old standby quick fixes for avatar rez problems: Change your active group or group tag. Press rebake (Ctrl-Alt-R) once a minute for 3 minutes. Change your bald. Change your shape. Move to another region and try 1 to 4 again. When those fail, check your connection as it is the most likely problem: Troubleshoot Your #SL Connection There is a longer explanation of the problem here: #SL Clouds, Grey, and Blurry Avatars. More in depth fixes are here: Avatar Render Problems: Ghost Cloud Smoke Ball Ruth.

Check that your computer meets the System Requirements | Second Life. When you ask a tech question include information about your computer and viewer. If the viewer will at least show the login screen, get the info from the viewer's Help-About... and paste that into your post with your question. To add your info to an existing question use OPTIONS->EDIT. It’s in the upper right of your post. Otherwise, on Windows click Start and type DXDIAG, case doesn’t matter. That will open the dxdiag panel. It will give you your system specs. We need to now video driver version, OpenGL version, CPU, SSE version, video card model…

Things have changed a lot. A big change is in region crossings and scripting. Visit the Market Place and get a free script counter. If you have a load of scripts you will have TP problems. Also, the cache size has changed and how the viewer downloads data has changed. More and more the viewer uses HTTP protocols. So, as Rolig says, test your connection. For specifically testing SL connection read: Troubleshoot Your #SL Connection. Also, you don't say which viewer you are using. If you are using the old viewer you used to use, that could be part of the problem. The 1.23 Viewer should work, but you are going to have problems and your experience will be incomplete. If you updated to one of 3.3.x versions then you may need to review your computer specs against the minimum requirements. System Requirements | Second Life. If you are trying to stay with a old viewer user interface check out the SIngularity, Cool VL, and Firestorm viewers. They kept the old UI and updated the viewer insides. Also, when you ask a tech question include information about your computer and viewer. Get the info from the viewer's Help-About... and paste that into your post with your question. To add your info to an existing question use OPTIONS->EDIT. It’s in the upper right of your post.

The Lindens won't say how long they keep them. I suspect that is more of an information flow thing than a security issue or secret. The Lindens meeting the public are not the ones maintaining servers at that level. What they have said is it is about a week to 10 days. But, no one swears that's the right answer.

Make sure you are not tryiing to upload in a pathfinding region. I can't get mesh to upload in a PF region. The exact same DAE file will upload in a different region. 3 main viewers... do you mean stable release, beta, and development? I have been using the stable release (main viewer on DL page) without trouble. I have had problems with the Dev viewer (Second_Life_3-3-4-258816_Development). I get the look in log error message. When you read the log (secondlife.log) look for errors and warnings. They should give you an idea what is wrong.

Yes... we do know what is wrong. Sort of... It mostly depends on when you last changed your password and which viewer you are using in which region. See JIRA item: SVC-7727 and please click watch and add your information. Make sure you are NOT in a Pathfinding region. I can't upload mesh there at all. I can upload the same mesh DAE file Morris. Avoid using the latest Development viewer (Second_Life_3-3-4-258816_Development). I can't upload mesh anywhere with that viewer. IF YOU CHANGED YOUR PASSWORD since April 2012, you are screwed. You won't be able to change clothes or attachments. Each time you log into ADITI you will be wearing whatever you were wearing when you last changed your password. Anything added to your inventory 30 days prior to your pw change will rez in ADITI. Anything added to your inventory in AGNI in the last 30+ days that transferred to the ADITI copy is not going to rez. Anything you make in ADITI and save to inventory will be gone the next time you log into ADITI. Last Location does not work... you always rez some place other than your last login. Often you can not login unless you type in a destination region name. It is a royal PITA!!!!!!

We usually refer to Blender as 2.49 or 2.63a... I'm not sure if you mean a 2.49 version. I've been using 2.63a and doing pretty well, provided I change the object's name in Blender. If I have a problem, I drop back to 2.62. There is a naming problem that Gaia Clary talks about here in the forum. There is also a Bone Handles problem. They are made from empties. They have to be removed before you can use version 2.59 to 2.62 to create the export file. There are a bunch of gotchas. They are all explained here in the forum. Presumably you are using SL 3.3.2 (258114), now the main viewer. I've used it to upload several mesh items today. HOWEVER... if you are in one of the Pathfinding beta regions, it won't work. At least I have not been able to upload mesh to PF region. You can look in Help->About... to see whether you are in a PF regions or not.

Using seach inside the viewer can be a problem. There are some glitches. When searching for people be sure you select PEOPLE in the search drop down. It does a better job of searching than just typing in a name and hitting search.

Everyone is considering this a video problem. Since that is not fixing it... lets look at something else. First... When you ask a tech question include information about your computer and viewer. Get the info from the viewer's Help-About... and paste that into your post with your question. To add your info to an existing question use OPTIONS->EDIT. It’s in the upper right of your post. I gathered that you are on a Mac. Mac's have DNS problems and that create connection problems. So, run through these steps and consider changing your DNS settings as the article discribes. Troubleshoot Your #SL Connection When you download a texture, SL send yous a version of a JPEG2000 image. As you get closer to an image, say a pic on a vender in a mall, the viewer requests a more detailed version of the picture. The system has to connect again and request a higher rez version. Your problem may be coming from the viewer not being able to get the higher rez image. Since Phoenix and Firestorm use separate caches the problem is likely to be inconsistent across the two viewers. It will be dependent on what your connection is doing at any given time. Also, it can be dependent on which server addesses your computer DNS system has cached and which it can't find. You could test whether it is DNS by clearing your DNS cache, you'll gave to Google as I don;t know how that is done on a Mac. Then clear your viewr cache. This shouls change what is happening in your viewer, if it is a DNS/connection issue.

Your SL Profile is also available on the web. Visit My.SecondLife.com to see it. Login and you can edit it. You can also set your privacy settings to control what shows on the web. To check your privacy settings, you must logout to see what others see or use a different browser without the cookies SL adds when you login.

When you ask a tech question include information about your computer and viewer. If the viewer will at least show the login screen, get the info from the viewer's Help-About... and paste that into your post with your question. To add your info to an existing question use OPTIONS->EDIT. It’s in the upper right of your post. Your problem is almost always a connection problem. Use these steps to TEST your connection: Troubleshoot Your #SL Connection. If your on a Mac, it has the DNS fix they need. You should always look at Second Life Grid Status Reports to see if a grid wide problem has come up. It can take a couple of hours for a problem to appear there. So, keep checking while you try to resolve the problem.

When you ask a tech question include information about your computer and viewer. If the viewer will at least show the login screen, get the info from the viewer's Help-About... and paste that into your post with your question. To add your info to an existing question use OPTIONS->EDIT. It’s in the upper right of your post. The chances are good this is a video driver problem. Without being able to see the drive version and video card type all we can do is guess. But, try updating your driver. You can also try the Beta version and the Development version and see if they make a difference. The Beta and Dev version are pretty close together right now, so it may not be worth installing both. They install in different folders. So, you can run all three at the same time. Also, before logging in, go into Prefernces and set your graphics settings to LOW. Then try logging in. If you get in, its defenitely video. Also we need to know if it makes it through Init VFS before it crashes. If it does, it is more likely its video driver issues. If not, it could be a cache problem. You can look in the SecondLife.log file for errors and warnings. that may give you a clue. I think the logs are in: Users/Username/Library/Application Support/SecondLife/logs/ --- I'm not a Mac person.

The part of the system that catches high Land Impact mesh objects BEFORE they rez is creating the problem. The "interceptor" tries to anticipate what the Land Impact will be before the item rez's and all the script and partical prim calculations are done. This program is apparently simplified for speed and miscacluating Land Impact values. I have some potted plants I was given that show as 90 items with a Land Impact of 1. With 80 prims available, they will not rez. I can go to a sandbox with 10k prims availabel and they rez just fine. This failure is a bug. See: SVC-7392 The JIRA item is incomplete and the Lindens cannot reproduce the error. If you can provide them a Step-by-Step that will reproduce the error and a copy of the problem model, they will look at it. If they can reproduce the problem, they'll get it fixed. You can submit the file privately so only the Lindens can access it. You can also bring the model to Monday's Content/Mesh Creators User Group meeting. The Lindens there are always interst in problem meshes.