Nalates Urriah

Rolig's is probably the correct solution. It may also be a region or connection problem. Try unpacking in a different region. Check your connection to SL, not the same as a good Internet connection, by opening the viewer stats panel (Ctrl-Shift-1). Look for lost packets. There should none or very few.

Wow! Force them… a bit on the pro-totalitarian side aren’t you? Linden Lab has consistently come down on the side of creative freedom. Personally I think freedom is better than any centralized form of control. You are free to make whatever video display devices you would like. The Lab has developed a replacement for QT and Flash that uses current popular technology (HTML5-CEF). Whirly points to the RC VLC Viewer. You can try it. Sometime yet this year it will become the main/default viewer for Second Life and third party viewers will adopt the tech, some may have already. Once it becomes the default viewer we will see merchants hawking the new tech for their in-world TV’s and video players. Until then the uninformed in SL will be buying useless QT and Adobe devices. The Lab has weekly meetings where they discuss coming changes and features. Users are welcome to discuss problems with them at those meetings. Only a dozen or so people show up for those meetings. Almost always the same people. The Lindens have a blog where they post articles on changes as they are released and/or reach the public feedback stage. But, few people read those. I can tell by the questions asked in the Answers section and posts like yours.

The problem is likely not you. The voice service of SL has been under attack for sometime. Vivox, the people that provide the service, and Linden Lab have been working on the problem. Over the last couple of weeks and this week's server updares the effort has been to change logging and aquire more data on what is happening and to improve recovery and reduce attacks. The only work-around for now is TP to a new region or relog. The other possibility is you have a poor connection to the SL or Vivox servers, which is way more specific than having a good general Internet connection. See: http://blog.nalates.net/2011/10/26/troubleshoot-your-sl-connection/

http://blog.nalates.net/2013/04/23/second-life-shape-export/ Units in 3D modeling can get confusing. I use Blender. But, it provides proof of the ideas. In all the modeling and CAD programs the use of feet, meters, centimeters, and etc. are for human convinence. The program it self uses 'UNITS'... just a number. It could represent lightyears or mimimeters... Between Blender and Second Life we consider Blender Units meters.http://blog.nalates.net/2013/07/11/blender-measurements-for-second-life/ But, I never turn on any 'units of measure'. That I can use units units in Blender and with an import ratio of 1:1 can get the correct size objects in SL, shows what numeric values SL uses. An avatar is generally 2 units or less tall. That you get the correct size object into SL says you get that 'units' part right. That it goes wonky when you wear it suggests the problem is in the weighting or your skeleton. If you download the SL avatar from the wiki, import it into your modeling program, export from your program to a file for upload to SL, import to SL and check the result in ADITI... should show if you have a problem somewhere in the import/export process, which I doubt. The result should be wearable and should pretty much work. That will leave only your weighting or skeleton as the source of the problem.

There are some Win 10 problems. You are running an older version of Win 10: build 10586, 64-bit. The current version is version 1607 build 14393. You may want to try updating. I suggest you Google for your laptop and Win 10 Anniversary update problems. Then decide. I was confused on your driver version. Your CPU i3-6100U CPU @ 2.30GHz is a sixth gen CPU and the latest driver Intel shows for its 520 in Win 10 flavor is version 15.40.28.4501. (Reference) You show 20.19.15.4300. So, looking for a 520 version 20.19.15.4300 driver I find that is the driver for 520’s supporting Win 7. I suggest updating the driver. You may find the Win 10 updates the driver. There are other changes in Win 10 that make this a bit nicer OS to use. Plus there is a significant change in the graphics pipeline. My new GTX 1060, yes I’m bragging, would not install on the pre-August 2016 version of Win 10. I had to update. Some SL users are running into OpenGL problems, the Second Life render interface. If you force updates so that you are sure you have all the updates, you should be good. At least I seem to be missing the problems others are reporting. Force the update by typing WINDOWS UPDATE and selecting Check Now. The tech info you included gave me a clue as to what may be the problem. But, the best tech info for troubleshooting SL issues comes from the viewer. Use it’s HELP->ABOUT… to collect the driver info we need most. You didn’t provide an OpenGL version. I would very much like to know what frames you get with you system... if you would message me here in the forum.

Typical settings that work for cloud scroll in FS and SL are >-1 and <1. My sunny day leisurely clouds scroll at 0.20 and 0.01. You may have to click on the slider, let go, and then use the arrow keys to move the slider. In the SL viewer you can tell the slider is selected as the button is highlighted. In FS you just have to know. It is the sort of thing that has me calling FS the power user’s viewer. FS has alternative clouds. You can change them by adding in your own texture. So, another factor is the size of the texture being used for the clouds. AFAIK, Windlight has not changed in years.

It is a bug, not you. Log out and log into another region. That sometimes fixes the problem.

We need a lot more information to suggest what may be effective for your friends avoidance of griefing. Rolig is right. Gettig kicked off SL is almost always a technical issue with connecton issues being the leading cause. GRiefers can't really kick you off grid. They tend to crash your viewer. If your friend recently set her ACI to UNLIMITED, change to to 350k. That will add video crasher protection. You can also read the viewer's log to see why the viewer shut down or logged off.

Patfinding is enabled by default. The region owner can disable it, a security thing not a performance thing. Think of it like 'no-rez' areas. It keeps people from doing somethng but doesn't change performance. Pathfind was designed to run ONLY in the server's spare time. If pathfinding consumes more than that, it starts to throttle itself. You can look ar your servers spare time to see how well pathfinding will work. Many think that pathfinding slows their region. That is never the cases. They have simply miss identified the problem. During development of parthfinding I and others had discussions with the Linden dev's about just this subject. You can find my blog coverage here: http://blog.nalates.net/?s=pathfinding&submit=Search I'm not going to find the specific subject subject of performance for you... your task, if you are that interested and want to know who said what. There are also pictures of the NavMesh and a bit of how to. My experience is complex pathfinding animations tend to get stuck. One needs to program for that so the objects can recover. Also, there is a need to program to handle region restarts. Depending on which Firestorm viewer you are using, there are no pathfinding tools. I think only the 32-bit SL version of FS has them. Quick Start - missing pictures. Pathfinding Overview - This article lists the LSL functions that use Pathfinding. From here you can jump into the scripting commands. There isno additional information in the Knowledgebase, other than to mention the Lindens use it their experiences.

In the viewer, before login, you can click HELP->ABOUT... to collection your computer specs. Or if the viewer is not running get CPU-Z and GPU-Z, both free, and they'll show yu what yuor computer has. Without specs we are guessing at what you need to do. Odds are AGAINST us guessing correctly. So, no one is going to put a lot of effort into explaining what to do. You can try this Intel® Driver Update Utility to see if it will help. If you are on AMD try Driver Auto Detect Utility. Or try these drivers, they may get you going: http://www.eightforums.com/graphic-cards/2519-intel-hd-graphics-2000-3000-a.html If you have an older CPU with the older GPU built-in, you are going to have to get a Win 8 driver and talk Win 10 into installing it. There are instructions for doing that. Find them via Google.

You got some answers but the how to check is a bit vague in them. On the purchase page you can scroll down to see pending buy-sell orders in two columns. Look at the top of both columns. Sell is at L$258/US$1 and Buy at L$268/US$1 (L$2,500 pending). The Buy offers at L$269 have stacked up to L$34 million. Whoever is willing to buy at L$268 is waiting for a seller as are those wanting L$34 million worth. Within the L$34m orders will bee filled in order placed. The line is long and it will take some time to get to the last buyer in that cue. There is no way to know how long. Everyone guesses. You can go into the page's left column and select MANAGE your L$ and see market data. Look at Today's Volume. It will give you an idea of how much money is moving through the exchange. As of now it is showing L$17m. The graphs say the last two days volume has been about L$110m. That doesn't guarantee today will perform at that level. It does say it is reasonable to think the whole L$34m will clear today. The problem is we have no idea how many will come in today wanting to buy L$ at 268... They will clear ahead of those wanting to buy at 269. So, some portion of those 269 orders probably won't clear. If I wanted to be certain an order filled today, I would buy at L$267. That would move me to the head of the line. Or I would offer at 268 as that is a really short line. Any seller willing to sell at L$269 will fill the L$267 first then the L$268 then the L$269 orders. With experience you can pay attention to the market data and make a decent guess at how long it will take a given buy order to fill. This is one place where patience pays, literally.

The avatar reamining as a particle cloud is called bake fail. To recover press Ctrl-Alt-Q to reveal the Developer menu item in the top menu. Click: Develop->Avatar->Character Test->Test Male/Female. This will load the built in avatar and you should render. Once working you can put on any outfit you want. I have noticed that the Current Outfit Cache gets messed up and the avatar refuses to render. The Test Avatar forces a cache clear and reload. If that does not resolve your problem, look at the connection to the SL servers. A good Internet connection does not mean you have a good connection to the SL servers. You can test it: http://blog.nalates.net/2011/10/26/troubleshoot-your-sl-connection/

Are you assuming the server hardware hasn’t been updated in 13 years? I think about 2 years ago there was a massive hardware upgrade. It wasn’t the first. Every so often I hear about backend services getting new hardware and software. Currrently new voice software is in developement. This is new VoIP tech not available elsewhere. Are you assuming that server and viewer software has not been upgraded? For the last 2 or 3 years we have been getting a new viewer version about each month with fixes and often new features. The servers get a new package almost every week. For the last year few new features but lots of foxes an improved performance. Are you assuming the majority of SL users have new hardware? They don’t. An XP user was asking for viewer software just this week. We have a load of Singularity users that don't have enough computer to run Firestorm. The load on the servers is an interesting topic. 4 or 5 years ago the Lab added mesh. Prior to that most objects in SL were primitives and the mesh matrix for those was built into the viewer as is the classic avatar. That measn no data download for the mesh. Adding what we now call ‘mesh’ made a significant uptick in the data to be downloaded. Script size and animation size have been increased. Materials were added and that alone almost tripled the possible texture download. Viewers were upgraded to use point lighting and changed from supporting a few lights to 256… or… I’ve forgotten the upper limit. What you aren’t seeing is that while the item count on a region hasn’t increased the number of polygons those items can represent has skyrocketed. Now we are adding more bones and animation possibilities to the avatars: Project Bento. I suspect the Lindens are counting on Avatar Complexity Reporting to drive down the avatar poly count and increase the demand for low impact clothes and avatar bodies. Freeing up render power to handle the new animations. You seem to think SL is old tech. Over the last 3 years we have been seeing huge updates to the latest tech. You are just looking at the wrong numbers.

Rolig gave a good answer and possibly the correct one for your situation. There is the possibility that the region you are loging into is having a problem. Go to the web version of the Destination Guide and pick another location. Try logging into on a couple of those. While you may have a great Internet connection, that does not mean you have a good connection to the SL servers. The particular set of routers you need to pass through to get from your computer to their servers may be having a problem. Check out the links Rolig gave you and figure out if the problem is on your computer, router, ISP, backbone, or the Linden's network.

Everytime im trying to use melee with left click in the sim my cursor changes to the avatar steering icon the + symbol. Is there anyway to disable this?

People are logging in and I got in... so its not an SL login problem. You've made 8 posts so you are probably fairly new... It may simply be the region you are logging into that is the problem. Go to the Destination Guide and pick a place you haven't been. Try a couple. If that fails, the problem is almost always a connection issue. So, step through http://blog.nalates.net/2011/10/26/troubleshoot-your-sl-connection/ You may have a good Internet connection. But that is not the same thing as having a good connection the SL servers. Test the connection to SL. See if there is a problem along the route. If the connection looks good, create an alternate avatar and see if it can log in. If it can, the problem is in your avatar's account. If it can't the problem is likely in your computer. Dig into the SecondLife.log and see if you get any hints. C:\Users\[Win_Login_ID]\AppData\Roaming\SecondLife\logs\ PS: If it is an account issue contact support.

Sort of... see: Obsolete Viewer. Scroll down. It is not fully functional. I suggest you checkout some third party viewers, Cool VL Viewer and Singularity Viewer may work for you. Information about them can be Googled. I personally recommend Cool VL because I sort of have a relationship with Henri, the developer. He sometimes yells at me... mostly he corrects my mistatements about his viewer. I see Cool being updated more often than I do Singularity. Both are said to run well on older systems. Win XP really can't support an SL Viewer. It will run but it will be an ongoing frustration. Hopefully less so with Cool or Singulartiy. I'm sure you have been told to upgrade. For games that is becoming a must-do thing.

First, the idea that the Lab stopped paying for a Linux license from the Havok people or other providers may or may not be true. Whither it is or not, their purchase would likely not cover third party use in any case. The functionality is delivered to third parties by the Lab building libraries that use the licensed code. They were for the Lab’s use but they shared. There are some legal restrictions on use of those libraries including Havok. That is why third party viewers used on grids other than the SL grid have no Havok features, at least not via Havok’s code or the Lab's libraries. Oz Linden, SL Project Manager, has talked about the Linux issue. Several of the Third party developers have too. The Lindens decided that supporting Linux was not worth the the Lab's time. There just aren’t that many SL users running Linux. So, they stopped compiling the Linux viewer libraries which were used by third party developers. That means third party dev’s have to come up with their own. The lack of Havok does not mean Linux users won’t be able to upload mesh items. What it means is their viewers will not be able to build LoD and physics layers. The designer will have to manually create those layers just as they do for third party viewers on all other grids. As far as I know the Linden viewer is NOT tested against WINE. But, you could go to Oz Linden’s Open Development meeting and ask. If you do, remember you are coming late to the conversation. I suspect such testing on WINE would have to meet the same ‘return on investment’ Linux fails, not enough users to justify it. I can understand the FS people pointing at the Lab. Not knowing what they told you, I can only suspect that it is reasonably accurate as the FS peeps I know are good guys. The Lab is not making the libraries they need for Linux. The FS people already buy the Kakadu JPEG2000 library for their viewer. Buying the Havok library and building a duplicate of the libraries used by the Lab is likely too expensive in terms of money and time. As to the Lab not talking… Oz Linden explained in the Third Party Developer’s meeting why they were dropping Linux viewer development, too few users. It isn’t that they don’t answer questions, it’s that you have to know who to ask what and how. The 64-bit viewer is in progress. Until it is in the RC stage of development it’s a stepchild, meaning they work on it when they can with most other things taking precedence over it. So, 64-bit dev is unlikely to be in the way of any Linux development.

There is a setting for Always Run. There are some settings that affect whether you walk or run. Debug Settings - the list of settings. AllowTapTapHoldRun JoystickRunThreshold Via the top menu use Me->Movement->Always Run (Ctrl-R). If you pressed Ctrl-R by mistake, you changed the setting. See Second Life Basic Movement instructions.

At the Tuesday and Thursday user group meeting the Lindens talk a bit more about what they are doing with the servers. Inara Pey (her blog) and I (my blog in sig) write about the goings on in those meetings. Currently there is work on Voice/Vivox, griefing fixes, and adding code to collect performance data. It is vacation time. That slows some things. There are meetings going on with Vivox. Vivox and the Lab are working to find and fix problems in voice. Recent denial of service attacks on Vivox servers have caused many dropped and intermittantly failing voice connections. Plus they are planning improvements to the voice service. There is more work being done on the Linden made 64-bit viewer. While there are not new shiny features to brag about showing up weekly, there is work happening and changes are being made. And while I like new shinnies, I understand some upgrades and changes are, to me, boring and yet have to be made.

There are commonly a couple of possibilities. The region you are trying to log into may be down or having problems. Try logging into a different region. You can do that by going to the Destination Guide and picking a place. You may have a good Internet connection and connetion to your wi-fi access point. But, that does NOT mean you have a good connection to the SL servers. The Internet is a myriad of routers, hubs, and pathways between you and the SL servers. All of that eqipment and load managed pathways change by the second. So, test your connection to SL. http://blog.nalates.net/2011/10/26/troubleshoot-your-sl-connection/ You can eliminate a wi-fi problem by temoprarily connecting by wire. Or if you have more than one laptop/computer, try connection wirelessly by it. If one works and the othe doesn't, wireless is OK and you are pointed to the problem laptop. When you ask a tech question, include details of your system and viewer. Use the HELP->ABOUT... in the viewer to gather the information. Paste it in with any tech question you ask. Mac's have some DNS problems not found in Windows. Those are covered in Troubleshooting.

Look for the file: C:\Users\[Win_login_ID]\AppData\Roaming\SecondLife\logs\secondlife.log This is a text file. You can open it with Notepad or Wordpad. Read from the end of the file back toward the beginning. You are looking for errors and warnings. They are labeled as such. Hopefully your error message will tell you something useful. I am assuming you have completely shut down, not sleep, and restarted. I am assuming you have at one time or another been able to run the viewer on this laptop and it meets the minimum system requirements. Before getting drastic, download a copy of the viewer and install over the top of the existing install. If that fails to fix the viewer, download a copy of the Firestorm Viewer and try it. If both fail the same way then something is wrong with your computer. We'll need to now if the assumptions are correct and what error shows up on the logs.

It is possible to animate mesh. It does require use of the avatar skeleton. We have no other type of 'animation armature' in SL. Bento is not far away. Current guestimates are the Project will advance to release candidate status in the next week or two. For more information see: There is a sort of flip-card animation done with mesh now. A model is made for each frame of an animation. The models are combined and animated by making various models tranparent and visible creating the ikkusion of movement.

You haven't told us enough to know why you might be crashing. So, we are guessing. Use HELP->ABOUT... in the viewer, before or after you log in. Copy paste that info with your tech questions. That your computer started crashing after SL went down may be a coincidence. Or there may be a cause and effect. Use CPU-Z, GPU-Z, and Open Hardware Monitor to see what your computer is doing. Did a fan die and you have started over heating? Did a memory chip fail? Lots of things to eliminate. SL will drive chip temps up and use memory that often isn't used in regular use. A bad connection to the SL servers can create odd problems. The Troubleshooting article will get you started figuring out if the problem is you or not you. Look in the viewer's SecondLife.log to see what it says the problem is. C:\Users\[Win_login_ID]\AppData\Roaming\SecondLife\logs\ Start at the end and work back toward the beginning. Problems are marked as an error or warning. You have to look at the log AFTER you crash. The log is deleted and a new one writen when the viewer is started.

The Lab did. They have been talking about replacing media playing systems in the viewer for over a year. There will be a formal announcement when it releases and rolls out to the grid. They make announcements from time to time about what is coming. Recent Second Life Developments - What’s New and What’s Coming! REMINDER: Update Your Web Browser to Ensure Secure Payments! Project Bento Testing Is Now Live on the Main Grid! Why are all these people made of colored jelly? Lab Chat Returns Friday with Ebbe, Oz and Troy Linden! Exclusive Message for Second Life Residents Available Inworld Today! and it goes on and on... Designers and creators in SL stay up on events by following Inara Peys's and my blogs. We follow what the Lindens are doing and attend the in-world meetings. Some designers/creators do also. Tuesday Noon - Denby, Agni Thursday 1 PM - Hippotropolis, Agni Thursday 3 PM - Morris, Aditi That is about 3 hours a week the Linden engineers spend with residents. Who made your car and how often did the engineers meet with you to tell you what they were doing? Or even have a press conference? No one is so all that that the Lindens will track them down and tell them what is going on. They have made it possible for those that WANT to know to find out. You could grip to the makers of the TV's and other devices. They have known for a LONG time things were going to change. I expect they'll ignore you. But, you can grip.