Nalates Urriah

Anyone can call accounting for any money interaction problem with the Lab. That the phone tree is miss behaving is only an indication of it not working, not a lack of permission to contact them. Wait a day and try again. Also, check the Grid Status. They have been having phone issues. Also, weekends and holidays office things tend to get behind.

Here is some more information about your Profile Image: http://wiki.secondlife.com/wiki/Profile_Image

If you closed off your payment method, the Lab would close the account on the renewal date as there was no way to pay the renewal. I am assuming the account you are logged in with is not the original Premium account that had your inventory. To get that account you will need to contact Accounting and see if they will/can recover that account. I think there is a small charge for that. But, you should get your inventory back.

You can use CPU-Z (free) to find your motherboard brand and model. Then look for its driver updates. There will probably be a driver for audio. If there is no Win 10 driver, you may get by with Win 7 or 8. Pay attention to whether you need 32 or 64-bit versions.

In the Linden and Firestorm viewers look in the upper right corner. In Linden there is an icon that looks like a monitor. You use it to save settings or select a preset to use. Firestorm is similar. In Preferences->Graphics there is an option to save settings into a preset. There are some good Third Party viewers. Firestorm is the most popular. About 3/4 of SL users are using it. Other 'official' viewers are listed here: http://wiki.secondlife.com/wiki/Linden_Lab_Official:Alternate_Viewers These are RC versions that have varous fixes. Other than the AssetHTTP I doubt any will help with your problem. Third-Party Viewers are listed here: http://wiki.secondlife.com/wiki/Third_Party_Viewer_Directory There is also the Cool VL Viewer which has a long history and good reputation. The author is a grumpy old guy that refuses to do the paperwork the Lab wants to be on the list. I suggest this: http://blog.nalates.net/2011/10/26/troubleshoot-your-sl-connection/ I doubt yours is a connection issue. A quick check is to open the Viewer Statists Panel (Ctrl-Shift-1) and look at Packet Loss. 0% is ideal. The higher the % gets the more problems you'll have. 1% and below is very livable. Above 3% things get bumpy. I've have textures rez slowly using Firestorm. But, usually within 5 to 10 minutes they are good. So, I am not sure why this one texture is being a pain.

You haven't given us much to go on. While Alwin's answer is likely correct, it is incomplete. Were you a Premium Member? If so, did you have to request the account be reinstated? Are you thinking the inventory is tied to your email address? Inventory is for a specific avatar. If you opened a new account, no inventory. Or at least not more than the basic new user inventory. Are you saying the Library in inventory isn't there? Have you reset the Inventory Filters? Are you looking at the Recent tab? So, we are guessing...

For whatever reason, the texture is not completely loading/rendering. Textures in SL are stored as JPG2000 a multi-resolution file format. That just means they have a low rez, medium rez, and full rez version stored in the same file. That you can enable TextureLoadFullRes and see the full render tells us the texture properly downloaded. So, clearing the cache is just slowing you and everyone else. Increasing texture memory is always a good thing to do. In general the only visible effect it has is to reduce texture thrashing, the render, go blurry, render, repeat endlessly. Changing TextureLoadFullRes is not going to damage your computer or break SL. It will affect your viewer performance and slow scene render. The viewer will wait for the entire JPG2000 file to download. "Wait" may be accurate, but the viewer will request the entire file rather than just the part it needs and that slows things down. You should not Have To change it. I suggest you save some graphics-settings-presets. Check to see that the value of this Debug Setting is saved. Have a preset with it enabled. Have it disabled in your other normal settings. Switch back and forth as needed. Mesh heads tend to have really high polygon counts, meaning they can be really slow to load. Mesh heads also use Level Detail (LoD) rendering. Meaning at certain distances different meshes render. SL provides 4 levels; high poly, medium poly, low poly, and lowest poly. Some designers are weak in making LoD versions. Those that depend on the viewer-upload to optimize and create their LoD levels usually have problems. So, this may be more a problem with the mesh than the texture. The less knowledgeable designers tell you to set LoD to 4. Bad move as it slows you and everyone else. You don't need to try it as your closeups show you have forced the highest LoD to load, at least it should have. With the FullRes enabled you can see it correctly... so that isn't you problem. I suggest trying different viewers and seeing if it is a viewer related problem. You don't mention having tried asking in Firestorm Support in-world. I suggest you see if they can help. Their wiki has a page on Slow Rez. You may have to check your connection. A good Internet does not mean you have a good connection to the SL servers.

When you are missing any data clearing the cache will likely make things worse. All legitimate recommendations for clearing the cache are based on its content being corrupt. Long ago that was a common problem in SL. But, some years ago the cache was revised to be faster. Then downloading of assets was moved from the UDP protocol, no error correction, to the HTTP protocol, with error correction. Now we very very seldom see cache corruption. Thus we should seldom if ever clear cache. Clearing the cache makes many problems it used to fix worse. Avoid clearing cache unless you KNOW the cache is the problem. Clearing cache is the last resort step. There is also a bug that is being worked on. We don't yet know if it is user error or a gremlin in the viewer. http://blog.nalates.net/2017/05/20/second-life-inventory-loss-warning-yikes/ The Linden viewer just updated to provide more protection from accidental deletion. Another bug happens when you have a weak connection and lots of items in a single folder. With a good connection having more than 5,000 items in a folder can trigger the problem. Use lots of folders to keep the items per folder number small. So, depending on your connection only part of your inventory may be loading. The Firestorm team has written a good inventory troubleshooter: http://wiki.phoenixviewer.com/fs_missing_inventory

But... but... isn't SL an inventory game?

@Puwii When asking questions like this let us know which viewer you are using. Use HELP->ABOUT... to collect the information needed for technical questions.

Can your friend Giannitra login here? That tests the ID/Password and account. Has Giannitra ever been able to log in? If there is a language issue, try posting in Giannitra's native language. I suggest a two language post for faster answers. Use Google Translate. LittleMe is right, we need information from HELP->ABOUT... also information about how Giannitra is connecting. Give us lots of details. Failure to connect is almost aways a connection issue. The next most common is an SL region problem. To eliminate the second possibility use the Destination Guide to pick different login locations. Try 2 different places.

Ideally, the 5GHz is the better 'performance' choice. But, walls degrade the 5GHz signal while 2.4GHz mostly passes through. Get the WiFi App and see if you can find where the signal drops off. Adding a repeater/signal booster may get you back on the 5GHz. Glad you have a working connection.

On Tuesday and Wednesday mornings you are likely to see this error. From 6 or 7 AM SLT/PDT until 10 to 12 they are updating the server software. That involves restarting the region hosts. Any given region is down for 10 to 20 minutes. A region being down will cause this error when you try to log into it. At other times the region you are trying to log into is down for various other reasons, thus the error message. In these cases, there is no telling how long a region will be down. If it is down for more than 30 minutes, file a trouble ticket. You can use the web-based Destination Guide to find a region you can log into. Clicking on the visit region button in the guide should open the viewer and setup the login destination. If all the regions are down... something is wrong. If you get the message for every region you try... check grid status. It can take an hour or two for the status to update. So, don't take it as the absolute state of the grid.

@Zareru Zerundi The obvious problem as pointed out is the packet loss. Now, what does one do? You will need to find out if the problem is you, meaning your equipment and software, the ISP's, or the Lab's. The steps are in my Troubleshooting article: http://blog.nalates.net/2011/10/26/troubleshoot-your-sl-connection/ If it is the ISP, you can complain to AT&T. If yours track down the problem device. A U-verse router/gateway should be new enough to not have design problems, meaning it should handle the needed connections. There are wired and wireless U-verse routers depending on where you are. Either way, if packets are dropping after leaving the router it is AT&T's problem. If you are running SL via a wireless connection to the router, try using a wired connection. If adding a wire from the computer to the router solves the problem, you have signal interference in your house. Fluorescent lights, which most are these days, are a huge source of interference. Change to LED if possible. Also, 5GHz channels are way more subject to interference. Try changing over to a 2.4GHz channel. If you have both channels (5 & 2.4), they will show in the Windows connections panel. Assuming you have a smartphone you can get an app from the Play Store called WiFi Analyzer. You can use it to check signal strength in your house. Reading lower than -40db in the area where you want to use the computer can be a problem. You can use the phone and app to find where the signal is blocked. Remember. The signal wants to go in a straight line. So, both sides of a room may have good strength while a middle section sucks because it is in the radio shadow of a metal cabinet or something. Since you are using AT&T it most likely is the signal from them to your house. When there is a choice, avoid AT&T networking.

Nah... I think bumping Whirly's to the top will handle it...

@drakeos99 According to signs in the region classes are free.

You have found a bug! I'll file a JIRA. See: BUG-100723 - Land Auction Search Fails. You can add to it or just Watch to see what they do with the information. As there is no region for sale named "test" the system fails... not you, them.

If you get this far down... Please vote up Whirly's answer (left side up-down arrows). that moves it up and should save people a lot of time...

@Bo Falworth Try going through your web dashboard: https://secondlife.com/my/index.php In ACCOUNT look for Mesh Upload Status. That should get you to the test. With a failing URL, you can try to recover by shaving parts off the URL. Delete from the right taking off everything up to the first/next '/'. Repeat until you have a working URL.

What you are reading is a server error. I doubt it is anything you did caused it or that there is anything you can do about it. You haven't told us enough to know for sure what the problem is. Alwin is right. We need to know what you were doing, how, and with what browser and your computer specs. You might try using a different browser to view the auction pages.

Your problem is almost always a connection issue. A good general Internet connection is not the same as a good connection to the SL servers. Test to the SL Servers. See: http://blog.nalates.net/2011/10/26/troubleshoot-your-sl-connection/ Rolig mentions the other frequent cause, overheating. You can use the free apps GPU-Z and CPU-Z or may be CPUID HDMonitor. Any of the 3 will give you temperature data. Another app Memory History (free) will tell you how your computer's memory is being used. Use up all your memory and you crash. That you can spin your avatar is a big clue in suggesting yours is a network issue. Without clear information about your computer, viewer, and connection all we can do is guess. Use the viewer's HELP->ABOUT... to get ALL the computer and viewer info we need. You'll have to tell us about your connection. Satellite, DSL, Cable, Wireless (U-verse type), age, and make of router/gateway. Some old routers have a problem with SL. The viewer can have hundreds of open connections to the SL and CDN servers. The max open occurs shortly after login and when you arrive in a new region. Old routers (5+ yrs) often can't handle the load. They then prevent the various viewer and server tasks from communicating and the SL servers decide you can't connect well enough to run SL. Satellite connections have way too high a latency to be used for SL. Open the Viewer Stats to see how your viewer-server is performing. The article at the link above explains how to see if it is you, your ISP, or the Lab that is the problem.

There are various ways to create the Demo. Many create one by adding the word DEMO to the texture in Photoshop or GIMP. This is sort of creating two products and requires uploading the retail and demo versions. Others include a prim that carries the demo information. A SHAPE is an interesting challenge. No texture is involved. There is nothing to attach a prim to... During the creation process of Experiences the Lindens though they would be used to create demo versions that never cluttered inventory. Good idea. Poor practical execution. Experiences require land within SL. They are not global, meaning the experience only works in regions owned by the Experience owner. While Experiences would be a good method of providing a SHAPE demo, it probably isn't practical. So... in a SHAPE demo some part of the no-modify shape is distorted. Hands, feet, nose, something is set to a really ugly setting. I mostly see hands set to the max size. In the basic Linden viewer I do not know of any way to add or remove system body parts, which a shape is. There are scripts that remove system clothes. In the RLV viewers with RLV enabled, it is possible to script the addition and removal of clothes and the replacement of body parts. While about 3 of 4 SL users use a RLV capable viewer, it is a much smaller number that have RLV enabled. These restrictions and lack of scripting are to prevent griefing....

There are two Hover Height settings. 49 would have to be for the setting in your SHAPE. Right-click the avatar and select that Hover Height. The default is 0.0. Adjust your avatar down. You will have to tweak the setting when standing and sitting. Make sure you have the correct feet or shoe's system shoe on.

I suspect you are using the release version of Singularity and trying to wear Bento hands. It does not have BENTO. You will need to get one of the beta versions. Ask for a link in the Singularity Group in-world.

Firestorm will run on i3, i5, and i7. But, the CPU will have to be at least 4th or 5th generation. 1st, 2nd, and 3rd generation iCores have HD 3000 and less. If I remember correctly 2nd to 5th gen CPU's are interchangeable all using a LGA1150 socket. On eBay Intel i3-4130 3.40 GHz chips go for US$50 to $100 if you are patient. Any newer LGA1150 chip will work. Since you likely are not going to be able to add a graphics card, updating the CPU is likely the cheapest upgrade possible. As to what is wrong... you are running a system where the graphics processor is built into the CPU. The computer shares system RAM with video. The HD 3000 processor does not provide the graphics power and functions needed to work with Win 10+ SL. Win 8 is a step behind and will run SL on HD 3000. Not well, but... The HD Graphics is for 2D games and video streaming. It isn't designed for 3D rendering in real time. The HD 4000 and newer has enough added power and capabilities to handle 3D rendering, not well, but usable. ALSO... the HD 3000 runs a very old OpenGL. It is this version that the viewer is complaining about. The OpenGL 3.1.0 is the newest available for HD 3000. Intel doesn't make an update. The current OpenGL version is 4.50. If you look at the System Requirements for SL, you'll notice they do NOT mention HD Graphics. The Linden page is out of date. Your 4GB of memory has to be split between system and video. Even 8GB of memory has problems; mini freezes and texture thrashing. Your problem isn't Firestorm. Most viewers will have this problem. The problem is your hardware. You can try running Singularity or Cool VL Viewer. Both are designed for older less powerful computers. Running 32-bit, even on the older hardware is less likely to work well than running 64-bit. It is that shared video-system RAM thing that will bite you. With 64-bit you can add more memory to your machine. (32-bit max's at 4GB and only can use 3.5GB).