Nalates Urriah

This section of the forum is generally about PEOPLE stuff. Tech questions go in the Technology Forum section. When you have a tech question we need to know a lot to give an ANSWER rather than a guess. Use the viewer's HELP->About... and paste that info with your question. The first troubleshooting step you have taken, try another avatar. Now try another viewer. Most Firestorm users keep a copy of the SL Viewer installed for testing purposes. AND... if you do have to go to the Lab for help, they will insist you use the SL Viwer to get their help. Also, strip your avatar to the basic nude Classic avatar. These steps will reveal or eliminate most of the possible problems on your side. Also, they provide info needed by the Lab to help. When all else is failing and when you and those helping have no clue, look in the viewer’s log files. 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 viewer starts. You’ll find the logs in: Windows: C:\Users\[Win_login_ID]\AppData\Roaming\SecondLife\logs\ Mac: /Users/<username>/Library/Application Support/SecondLife/logs You will change folder and file names based on the viewer used... But, they are all similar. 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 a 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 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. Entries in the files associated with errors and warnings are labeled as such. That makes them easy to find by searching. Search and read through them starting at the end of the file and working backward. 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.

This isn't the thread for long tech discussions. This is a thread for showing off the results of our skill, knowledge, and talent... however little or much that may be. We get to enjoy, compliment, encourage, and gather ideas. The Technology Forum is a better place for the technical discussion. It is common to add questions here and get quick answers. But tutorials and long discussions need their own thread. Two reasons: for some the discussions are boring and it gets tedious skipping over them and next, the discussions here are very difficult to find for those searching for the same how-to, which is more appropriately placed in the Technology Forum. Also, when moving to a new thread it is common to place a link in this thread.

When asking about technical snags include the information about your viewer and computer. Use the HELP->About... in the viewer WHILE logged in. @cyrotic FS 6.6.16 has some odd inventory issues affecting how things react in SL. I didn't see any problems while I was using 16. But, I took their advice and upgraded to 17. From what you've told us, we have no idea if you have a 16 problem or something else.

Yes and no... for terrain there are height maps. Not for prims... For prims we use Normal Maps. You can find a lot of this information in the SL Wiki.

😳 I am so disappointed...

This is not the first time the Lab has thought they would do something with the ADULT part of SL. Since I came in (2008) they have done this a couple of times. Nothing really came from the previous efforts. We did get an Adult sandbox which is a griefer heaven and seems mostly ignored by Linden maintenance and governance. From talking with Lindens over the years it seems there is an in-house stigma on those agreeing to work on the Adult projects. I suspect that is still likely. If so, this will be another short-lived effort. As best I can tell anyone that ever 'volunteered?' to work on one is no longer with the Lab. So, not a good career move. While most corporate teams shy away from sexual and political affiliations or associations the tech world is changing as younger people enter the ranks. Plus the Woke and liberated young are more accepting of formerly taboo topics... or maybe its just that they don't know they were ever taboo. The Lab is data-oriented. They track all sorts of SL info and use patterns. They may see something that says this will be a good move. We know sex sells. Often very well. It is always just a matter of how it is presented. Does the Lab have some novel new approach for a virtual world? I suppose we will find out. So far the ideas people have had here seem rather limited... which I suspect is less a personal imagination problem than an opinion of the Lab's imagination. 🙄 We'll have to wait and see if they surprise us. But, since they are not working on this one in cooperation with the residents, it probably isn't going to go all that well. But.... I can hope...

To know what Lelutka will do ask them. But, I suspect the cost of a lawsuit would far exceed any amount of damages that could be proved. I think it is not an issue.

No. SL has made the Classic UV Map available for use in creating skin and clothes. With Lelutka ask them. Consider picking up their Developer/Creator's Kit. It has all their restrictions and conditions.

Their Alpha and Beta testers have access to Firestorms PBR versions.

I am enjoying the National Blab. I think if the hope is to elicit comment and discussion then it does NOT belong in this thread... and comments are part of the fun. But I don't have a good suggestion for where to put the Blab. So... here will do. Now that I am looking at this image... wrong dress. I'll have to borrow a dress from Victoria.

I would like a bit more realism. The PBR rendering will add more realism to our surroundings. However, until the Lab upgrades to Vulkan, I doubt much can be done about the unrealistic appearance of skin. I would love some avatar-targeting controls... so lips would meet when kissing... maybe stretch the neck for a kiss. Getting other parts to fit would be a plus too. Maybe something so via scripting, we could tell the system which parts to fit together. Movement improvements... kinetics for animation would be nice.

A big part of the difference is the lighting. The ambient light in the first image is way more than in the second. Plus there is a color cast. I suggest you consider tweaking on the EEP/Windlight settings before worrying too much about a skin.

Well.... your ears are kinda big.... You are cute. Pretty avatar.

You kinda left us in the dark. When asking a tech question include the copy/paste from the viewer's HELP->About... This will most likely be a viewer problem. Possibly a network issue. Bounce around SL. Try the mainland regions and popular places. If this is happening everywhere. it is NOT a region that sucks but something else. When flying I will see this type of thing when the draw distance (DD) is at 128m. Changing to 512m DD clears it up. In some cases, a region is down and you will see this empty water. In Firestorm the mini-map/radar (Ctrl-Shift-M) will show the down region with red shading. You may have to zoom the map out to see several regions. Do some experimenting and testing to start narrowing in on the problem.

The change from copper to fiber should make no difference. HOWEVER, that doesn't mean your provider didn't mess things up. Since your computer and network connection work(ed) with the old network, it means those components are good to go. It points to the problem being in the new part of the network. That will need to be worked out with the ISP/provider. There is an exception. If you have old network switches or OLD CAT-3 wiring in your house, they will be a problem. The older 10-100mb switches will choke on the 10-1000mb data stream. When I upgraded my connection I had to replace all my switches. I could not connect via the old switches. Fortunately, I used CAT-5 for my wiring.

There is no prohibition to TPing into an open space, AFAIK. However, the region/parcel owner may set where those TPing in can land. When land is abandoned the Lab often does not reset the landing point or restrictions. Which means open space behavior may be inconsistent. So, when you create an LM, it may or may not work as you expect.

I suppose it depends on what you are experiencing... The mouse has a "resolution" which is an OS (Windows/Apple) setting. Some mice have buttons to change mouse resolution on the fly. In Windows, the setting is in Mouse Properties->Pointer Options (tab)->Pointer Speed (slider) THe OS sends mouse info into the viewer. The setting affects mouse speed in the viewer... and all apps. In BD on the Camera page of Preferences, there are several Camera Settings. Play with those. You can Ctrl+LMB-click on a slider to return it to the default setting. (RMB-click returns the setting to its previous setting.)

You do not have to disable them unless they are generating false positives, as does happen from time to time. Fortunately, the false positives from AV, Spyware, Malware, and other detectors are a rare thing. There are places where firewall settings have to be tweaked. At school that is often the case. In some cases getting through a university's firewall requires a personal virtual network (VPN) and port adjustments. We whitelist viewer folders as a matter of performance. With some AVs it avoids the mistakes they make in detecting PUPS and reporting false positives. Also, third-party viewers run into these problems more than Firestorm or SL Viewer. But all viewers perform better when they do not have to wait on the AV to check the files at each file access.

I had to do a clean install of BD 5.0.1 to get it to run. The EEP settings tend to appear in BD with less ambient light and more saturation. My avatar appears to be perpetually blushing and to have a bit of a darker skin. I can generally tweak the gamma up to correct the changes.

You can try using your physics item with the system/classic body. If you see the AP working with the default body but not with the mesh body... then you know it is not your AP settings or viewer.

Not all bodies use the bones influenced by Avatar Physics (AP). There is no good way to replace AP with an animation. If the designer does not rig the body to use AP then the info needed is just not there. With breasts, it is possible to make "passable" animations as the vertices of the breasts are almost exclusively weighted to a couple of bones. So animating the breasts is possible. With the belly and butt, most of the surrounding areas are weighted to the same bones. So animation moves more than just the part AP moves. Some clever creative may devise a way to do what you want. I have yet to see anyone that has done that.

This is an area of SL where you can spend money to save learning time ...or... spend time learning SL and save money. I think the latter is more productive. If one learns a lighting studio then they can do all it offers well. If one learns to control the SL environment (EEP/Windlight) then they can go beyond what the studio allows to all that is possible in SL.

I don't know. I suspect it is too soon for anyone to have made a deformer to make Lara clothes match LaraX. Since Lara and LaraX are included in the LaraX package those purchasing X won't need deformers. Those sticking with Lara might like a fix but, it would have to be cheaper than LaraX. So, I don't anticipate andy such deformer.

Yes, it is smart to disable Maleware and Defender when doing a clean install. Then while-list the viewer's install folders and the viewer's cache folders in Maleware and Defender BEFORE launching the viewer. Use the viewer's HELP->About... to get a list of the hardware and drivers that are important to the viewer. Post those here and we'll see if there is some other problem.