Nalates Urriah

If you have a mesh item... just rez it in-world like you would anything else. Drag it from inventory to the floor. You can link it to a mannequin just as you would any prim. How it is going to fit the mannequin is unpredictable. If the mannequin NPC is a bot, then it will be using a shape and have a sleleton. So, the item will fit is like it w ould any avatar.

No one seems to really have explained property division SL. The basic unit of land in SL is a region, 256m x 256m x 3,000m. Similar to a section of land iRL, USA. Actually about a 1/16th of a section. The owner, individual or Linen, can divide the land into parcels. They can be sold or leased/rented. There are almost no size restrictions. One can go as small as 1m x1m to a full region. 1/2 region, 1/4 region are common. The basic parcel is 512 sq m and the shap varies. A sort of standard is L = 2 x W. There are various ways to see the parcel boundaries. The way depends on the viewer you use. The Linden or default viewer is not all that great at showing parcel boundaries. Zoom out where you can see the land and press Ctrl-Alt-Shift-P to have the viewer draw the boundaries. You can also right-click on the terrain to reveal the parcel boundary. In the World Map you can click on Land Sale to see some boundaries. Some third party viewers show boundaries in the Mini and World maps. There are maps of the various continents in the wiki and online. The map server generates some maps, mostly those used in the World Map. But, you'll see them used in other applications. Since everyone has access to the boundary information in-world there is little need for mapping in SL. While in iRL finding a property line can be a challenge, in SL it is a right-click away.

You can look in the SecondLife.log file to see if it gives you any clue as to what the problem may be. That this happens 5-10 minutes after starting SL suggests a possible heat problem. Get something like Open Hardware Monitor to check your temps. Temps in the 50C are decent. 60"s livable. 70's are hot and anything greater is definitely a problem. Windows has some AI error correcting features. So, before spending a day reinstalling Windows, keep playing ans see if the problem reoccurs. Before I would spend a day reinstalling everything, I would make sure that effort is actually going to fix the problem. To know that I have to chase down the problem. So... start with the SL log.

Such problems are almost always video driver related. When you ask a tech question use the Viewer's HELP->ABOUT... to collect the computer and viewer info and paste it into your post. Start here in the Firestorm Wiki: Troubleshooting

When asking tech related questions we need to know about your computer, viewer, and connection. Use the viewer's HELP->ABOUT... to gather the computer an viewer information. Paste that info with any questions. In general, restart the computer and router/gateway and see if that resolves the problem. If not, try a different viewer. The Firestorm and Linden viewers are pretty much the default debugging tools for SL problems. If that doesn't solve it, check Grid Status to see if there is a problem SL side. Check the Viewer Stats (CTRL-SHIFT-1) to see if the region you are in is having problems. PING should be <250ms, Packet Loss <5%, Time Dilation >0.90, and Server FPS >40. Even if these numbers are good, try another region. Before you start ripping your computer appart and reinstalling stuff, wait a couple of hours at least. Slow rez and rez fail almost always connection problems. A crrier between you and the Lab's servers or the Lab can be having problems or experience a griefer attack or temporary heavy load. Give them time to block the hacker and/or clear an overload.

The Viewer Managed Marketplace (VMM) was a 2014-2015 project that rolled out in final form in 2015. The Beta ended long ago. To see the old coverage, see: http://blog.nalates.net/?s=vmm+&submit=Search You may want to consider a new source of Second Life news... or perhaps a source...

When you ask a tech question include information about your computer and viewer. Use HELP->About... to gather the information. Did you look in the SecondLife.log file? What did it say? Have you checked your upload speed with SpeedTest.net? Have you checked your Packet Loss? Use Ctrl-Shift-1 to toggle viewer stats open and closed. Use this infomration to decide if you have a connection issue: http://blog.nalates.net/2011/10/26/troubleshoot-your-sl-connection/

Often such problems are network or server related. This means if you wait, the problem will self correct. You may do a clean reinstall. That may help or not. But, it is very likely that the time you spend backing up, cleaning thngs up, and reinstalling may be the time needed for the network or servers to recover from whatever problem they had. So, a good process is to restart the computer and gateway/router. Retry your login. On fail, check the Grid Status. If nothing is showing in Status, try logging into a different region, say Furball, Pooley, Fishergate... I have region names in my favorites that I try when I can't login to my home. If these steps fail... Bounce into the forum and ask if there are problems. Kill an hour or two and then try again. While you wait you can test your connection to the SL servers: http://blog.nalates.net/2011/10/26/troubleshoot-your-sl-connection/ Only after a couple of hours do you want to consider things like a clean install. Don't trash a computer that is working well because your login-target-region is down.

With the opportunity VR provides for bringing new people into SL, can the Lab really give up on it? We have lots of recent improvements to SL performance server and viewer side. Avatar Complexity will move SL conent toward being more optimized. So... will VR support be more likely in the future as possible performance improvements more us toward a better experience? Aren't more people upgrading computers to handle VR? I doubt the Lab can completely and forever give up. So, what might be going on? My thoughts are here: Second Life VR Door Closed? What do you think and why?

Its not clear where this is going... VR is an opportunity to bring more people into SL. I can't imagine the Lab completely giving up on the SL side while developing the tech on the Sansar side. So, what might be going on? My thoughts are here: Second Life VR Door Closed?

Medhue has a video out showing the differences in no-translation and translation using animations. See VIDEO:

Contact support. They'll explain how to prove you own the account. Once you do, they'll give you a new password. If you have a non-technical issue related to billing concerns, you can call the Linden Lab billing team at the following toll-free numbers at any time 24/7: US/Canada: 800-294-1067 France: 0805-101-490 Germany: 0800-664-5510 Japan: 0066-33-132-830 Portugal: 800-814-450 Spain: 800-300-560 UK: 0800-048-4646 Brazil: 0800-762-1132 Long distance ( not free, but you can use Skype to save some cost ) : 703-286-6277 **Note: Support is offered only in English

DO NOT FREAK!!! You are probably OK. Do not rip your computer appart. You may not be the problem. First check things with the Linden made SL viewer. It is the main troubleshooting tool for problems. If you don't have it installed, install it. While you may only ever use it for troubleshooting, having it will save you lots of heartache. Also, don't be clearning cache. In your case clearnng cache likely has agravated your problems. There are two possible problems that are popular right now. One has to do with how your inventory is arranged. If you have folders with more than 5,000 items (>5,000 items and folders in a single folder), that could be your problem. Run the Linden SL viewer. If you have the same problem, contact support. They will rearrange inventory so there are no more than 5k items per folder. The next problem can develop if you use the Preview/Beta grid for testing things you make. If that is the case provide that information to support and they will clean up your inventory. The Linden viewers use a sperate cache for the Preview grid. I don't know if Singularity has made that change or not. If not, there is a good chance a visit to the Preview Grid corrupted your inventory server side. So, support has to clean it up. Explain that you use Singularity and that now the Linden Viewer has the same problem. Your inventory list is keep in a separate cache. You can clear it without clearing the main cache. Trying to reload the main cache and inventory list on a weak connection leads to all sorts of problems. Read the Firestorm Wiki for instructions on how to clear just the inventory list. Also, log into a deserted and empty region like Furball to try and reload your inventory. Lagging servers can mess you up too. Good luck.

You could replace the video card... If you remove it, what are you going to connect the monitor to? There are video drivers for your video card. You can search the forum for the current best version to use. You can change out drivers at will. Most Radeon problems are driver problems. ------------- You say Radeon thing like there is only ONE THING ever with Radeon video cards... So, we are left clueless to what you are talking about.

Visit the Adult Hub. You can use in-world search to find it. The area will have some free stuff for new users. Skins are part of some packages. There are a number of regions that are devoted to providing free stuff to new users. You can find them by searching on free and, as suggested, freebies. And try free skin.

AFAIK there are no changes to Havok, the physics engine. But, they did upgrade the grid with a new server package. See DEPLOYS and follow on to the release notes. There isn't much information. But, it is the only change I know of. There are some rumblings in the forum and groups that others have run into problems. I suggest you file a JIRA bug report. Provide all the information you can. Have others you know of that have run into the same problem add to your JIRA.

You never say what your FPS is.... Don't expect GTA frame rates. SL content is NOT optimized and kills performance. The new Avatar Complexity is an effort to turn that around. Set it to 200k or so for your card and try lower values to find your sweet spot. DO NOT USE UNLIMITED. That turns off the video crasher protection and leaves you vulnerable to griefers. The video card is only one of the possible bottle necks. People often update a video card thinking it will make a big difference and find it doesn't. Software-wise make sure you have setup a Second Life profile in the NVIDIA setup. See: http://blog.nalates.net/2016/06/05/nvidia-settings-2016/ Take your Max Bandwidth from 2,000 to 1,500. This setting is for the server more than for your viewer. Trying to send more UDP info than 1500 generally causes problems. The setting is recommended as 80% of your max download speed or 1,500 whichever is smaller. Your draw distance shouldn't be that big a problem. But, keep it in the 128m range. If it is larger than the distance you can see, you are loading items and rendering some of them that you can't see. Save those cycles by reducing the distance to what you can normally see. The Quick Graphics update gave Linden Viewer users the feature FS users have had for some time, setting up graphics settings configurations and saving them. That allows quick changes. Low Draw Distance for shopping and combat and long ones for outdoors and photos. Use the feature and see if that makes a significant difference. Check your Anti-Aliasing setting. With a 1080 some people get carried away and set it at the max. In SL 2x or 4x is pretty good. See if it makes a difference. Experiement with other settings. My old 'settings guide' explains what all the stuff is... if you don't already know: http://blog.nalates.net/2010/12/17/graphics-tweaking-for-second-life/ If you haven't already, get the free program CPU-Z and get the memory chip info. Memory should be the fastest your motherboard can support. You may have to look up your motherboard specs to find the max it can handle. Check the motherboard specs and make sure it can take advantage of the SSD speed. If you have an SSD hooked into the SATA ports rather than an M2 port, it may not perform any better than a fast, large cache hard drive. Also see if it can do 6gb/sec or just 3gb. You've checked temps, so that elminates that problem. If none of these tips help, post what you find and IM me via the forum. I don't follow these threads. I'm a comment and bounce kina girl... so I probably won't notice your follow up. If you find your motherboard is limiting you, the only way around it is a new board that works with most of the hardware you have. I am building a new machine with a z170 board. I'm having to buy all new stuff because my existing machine is too old. Drives are 3gb era. Memory is slow DDR2 and the new board uses DDR4. So, there is a lot to consider when having to cange out the motherboard. ------------- PS: If you haven't done a clean install in some time, try a semi-clean install. What I mean is close the viewer, restart the computer, delete everything in the Second Life program folder (this doesn't affect chat logs, settings, or cache), reinstall the viewer. This is more of a problem for Linden Viewer users than others. FS recommends a clean install with every version update.

I often use Google Chrome's Remote Desktop to access my main computer from an Android phone and my HP laptop. The app is free and works well. It is a little bit of a pain to setup and f umble through the first time. After that it is easy. I find that using SL on the laptop via Remote is marginally slower than just running SL on the Laptop. But, I can push the render quality up on the desktop and have a nicer image on the laptop than when limited by the laptops HD Graphics. There are other remote desktop access programs. I've used a few for my self and to support clients. I've pretty much settled on Google's Remote Desktop.

The Lab and some third party developers track crash stats on their viewers. 64-bit viewers have a much lower crash rate then 32-bit viewers. Using a 64-bit operating system helps 32-bit viewers crash less often. In general many viewer problems are memory related. 64-bit systems can spread out and use more memory generally avoiding problems longer than 32-bit systems. Having a lower crash rate does not mesn they have better performance. But, having lots of memory in the system can improve viewer performance. 32-bit systems are limited to a 4gb memory space. Taking out room for the OS the apps have 3.5gb to work in. 64-bit systems are generally only limited by what the motherboard can handle, typically 64gb. Taking out 0.5gb for the OS that leaves 63gb for apps. I don't know of anything the 32-bit Firestorm Viewer can do that the 64 bit can't...

Lots of info on the hardware... it all looks good. The viewer has various log files you can read to get an idea of what has gone wrong. Look at the log immediately after you crash or exit the viewer. Logs are replaced the next time a viewers starts. You’ll find the logs in: C:\Users\[Win_login_ID]\AppData\Roaming\SecondLife\logs\ crashreport.log – This log is generated when the viewer crashes, the previous version of the file is overwritten. Rename this file if you plan to restart the viewer before examining the file. Otherwise, just read it with a text viewer (Notepad is good). debug_info.log – This file is internally formatted as an XML file. I never find it of much use. It is mostly the specs of your machine. SecondLife.log – This is the main log file. I find it the most useful. Start from the end of the file and work toward the beginning. Search for ‘WARNING’ and ‘ERROR’. With any luck the messages there will give you an idea of the problem. Recent changes have added section heading to parts of the file that can identify the general nature of the problem. There are lots of performance stats included. At the end of a non-crash log there are secession stats; Run Time, Average Packet Size, Dropped Packets, Resent Packets, etc. The file is replaced and recreated for each viewer secession. SecondLife.error_marker – I don’t know what information is inside. I don’t have a copy to examine as I write this. The presence of the file indicates where, when, and what error happened. I think this is a disaster backup file for crash reporting in which information about the crash is retained in the event the crash handlers are destroyed before they can create the other more complete crash files. SecondLife.start_marker – There is no information inside. The presence of the file indicates how far into the start process the viewer has gotten. Whether the file exists or not is the pertinent information. SecondLifeCrashReport.log – This is another file internally formatted to XML. It is created when the viewer crashes. I think this is the new version of the crash log. It is mostly text. stats.log – This is a short file containing network statistics. Similar information is in other log files. It is an easy to read set of stats that show how many packets were dropped and resent in a secession. I find the SecondLife.log is the most useful file for tuning and troubleshooting the viewer. It is verbose and reasonably easy to understand. There is a Debug Setting in the viewer that allows you to increase or decrease the level of reporting. Most of these files are erased when the viewer starts. If you plan to send the files in with a trouble ticket or bug report, place copies in another folder before starting the viewer. Marker files are temporary and may or may not exist at any given time. They indicate when the viewer died and stopped reporting. Entries in the files associated with errors and warnings are labeled as such. That makes them easy to find by searching. Warning entries are common and do NOT necessarily mean there is a problem. Some warnings are a part of normal operation. Some errors are trivial and do not indicate a ‘noticeable’ problem in the viewer’s operation.

I find your question a bit ambiguous. From the asnwers I take it others do too. Whichever viewer you are using, you can set the size of the snapshot when you are taking it. At this point ratio is NOT a criteria. You can use any raio you want. You just have to decide on the image dimensions. Ratio only becomes a problem when you want to display the shot in-world. We normally apply the image/texture to a prim. So, if we capture the image as 1024 wide by 512 high (2:1) then we need to make the prim 2m wide and 1m tall (also 2:1). The prim can also be 4m x 2m, 8m x 4m, etc. all being 2:1 ratios. The displayed image will look like what you captured, no proporational squish or stretch. While it is possible to use any ratio you want, the quality of the image when dispayed in SL can degrade if you don't also consider how the SL system stores images. The system will only allow power of 2 sizes... meaning 2, 4, 8, 16, 32, 64, 128, 256, 512, and 1024. The system maxs out at 1024. Width or hight can be any of these dimensions. Larger images are down sized and pixels discarded, which translates to lower quality. If you use other dimentions, like 1024x450 (2.75:1), the system will store the image as 1024x256 (4:1) or 512 (2:1)... I'm not sure which but, I suspect SL will always down size. The problem with that is you lose pixels. So, if you size your prim to hold the 2.75:1 ratio you captured to make the image 'look' right the system has to 'interpolate' pixels and the SL system is not very good at doing that... loss of quality, fuzzier image. I think most of us take whatever image we want at whatever size we happen to like at the time. Then for those images we display in-world we use GIMP, PAINT.NET, Photoshop, or some other image editor to crop the image to a power of 2 size and the ratio we want.

A new version of the Linden Oculus Viewer has been released 7/2016: Second Life Project OculusRift Viewer version 4.1.0.317313. Also see my blog. Look in categories to find all the related articles.

To answer technical questions we need information about the computer and which viewer you are using. Open the viewer and before logging in click HELP->ABOUT... and copy paste that information into your post. Click OPTIONS in the upper right to get to the EDIT option. Have you tried logging into a different region? The problem may be the login destination region. Have you given it a couple of hours? Many problems in SL are transient and will self correct. Have you tried a different viewer? Have you restarted the computer and router/gateway?

You can enable and disable member-role's ability to open chat. So, if most are in the EVERYONE role, you could disable that portion of the membership from posting. But, I don't know if that will stop people that have essentually logged into the group by posting. I'm not sure what you consider out of hand. Presumably, there is someone fanning the flames. Most groups give the person a warning. If they persist, they ban/eject them. In most cases only a very few people create most of the problems. Once those are out the group tend to run smoothly.

The Linden made Oculus Viewer is now well over a year out of date and I suspect incompatible with the retail Oculus Rift. For several months the lead SL Linden has been promising an update. It isn't here yet... The only 3rd party viewer supporting Oculus has discontinued the viewer. That developer is playing in HIgh--Fidelity. So... those with a Rift wait...