Jump to content

Rolig Loon

  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Rolig Loon

  1. As Valerie suggests, try Nyll's solution in the thread that she referenced. It may work for you. Otherwise, remove the current viewer from your machine completely. Then either stick with Firestorm or download and install a previous version of V2 (from http://wiki.secondlife.com/wiki/Category:Release_Notes). If you decide to use V2, disable the automatic upgrade feature (in Preferences >> Setup).
  2. Sharing the cache folder between multiple viewers is a primary cause of “inventory loss” which many experience, although not the only cause. It also frequently results in crashes or erratic behavior. Clearing your cache manually will “cure” all manner of odd behavior and is the suggested procedure before resorting to more drastic steps like reinstalling the viewer. 1. Open Preferences → Network & Cache 2. Go to the first path “Cache Location” and click the “Open” button behind the path. This will open a file explorer window displaying your current cache location. 3. Logout (close the viewer) and then delete everything inside the cache folder displayed in your file explorer. Now continue as follows: 1.Log back into SL, to a quiet region (try Smith or Pooley). On your inventory window, click “Recent Items”. 2.Wait for your inventory to repopulate fully. The process may be sped up, if necessary, by typing random letters into the search bar. 3.While inventory repopulates, do not teleport anywhere, and do not attempt to access anything in your inventory. Talk to people or surf the web, or just go out for coffee 4.Watch as it repopulates. As long as you can see (Fetched…) at the top of the inventory window, it is still loading. 5.Once inventory has repopulated, log out of SL once more, then log back in.
  3. Don't bother. There are several bugs in the recent upgrades to the V2 viewer, and that one is affecting a lot of people. The best solution is to delete it entirely from your computer and then download and install a previous version (from http://wiki.secondlife.com/wiki/Category:Release_Notes) or a third party viewer (from http://wiki.secondlife.com/wiki/Third_Party_Viewer_Directory). If you install and earlier version of V2, be sure that you go to Preferences (CTRL + P) >> Setup and disable the feature that automatically downloads more recent versions.
  4. Everest Piek wrote: to thise complaining about the 'impolite tone': fankliness isnt impolite. politeness is a nice thing, but not useful if you have to say harsh words. No, "fankliness" doesn't have to be impolite, but it can be. If you're trying to help people learn a better way to do things, or trying to convince them to at least see things your way, using harsh words is counterproductive. Politeness is rarely a bad idea. I appreciated the OP's recent post, apologizing for the tone of the original. He seems to have realized that the tone got in the way of the very good recommendations he was making.
  5. We can sympathize with you, but there's not a thing we can do about it. We are not Lindens. We are all residents, just like you. When an IP address gets blocked, it's usually intentional. LL does it when they detect an account irregularity (that is, you aren't paying your bills) or when an investigation convinces them that someone at the address has violated the TOS. There are always a small number of accidental blocks, but it looks like there are suddenly more than normal. The same thing happened once last spring too. It's really maddening, but our answer here has to be the same. If you think they have made a mistake, you have to file a support ticket or call Live Chat to let them know. Otherwise, LL won't even think to look at your IP address and reverse the block. They'll just assume that it was blocked correctly.
  6. I can't ever tell. That's why I said "try". :smileywink:
  7. I'm in line too. One of the benefits of Mono is bytecode sharing. If you have several copies of the same script (a notecard vendor, maybe?) running in a region, they only take up the same size as one copy in server memory. Today, if I have a choice between running four copies of an LSO-compiled script at 16K each or four copies of a Mono-compiled script, it's a wash. If I can restrict the Mono script to anything less than 64K and still get the job done, though, I'll go with Mono.
  8. Most of the time, LSL treats a key as a string variable, but not always. I can't ever tell when it's important. Try defining the texture as key texture_UUID = "the UUID goes here" instead of string texture = "the UUID goes here"
  9. See if the information here helps >>> http://community.secondlife.com/t5/English-Knowledge-Base/Graphics-cards/ta-p/700073
  10. It may not be your fault, although don't be fooled into thinking that you can get SL to work just because you can play some "big games" on your computer. SL demands a lot more bandwidth and is much more sensitive to unstable Internet connections than most programs you are used to. Still, there have been several problems with the most recent version of LL's viewer, which is probably the one you downloaded and installed. We have seen an surprising increase in the number of crash logger errors recently. I suggest that you manually remove all traces of the viewer that you installed and then download and install a completely different one. Several very good, stable third party viewers are approved for use in SL. You'll find two of the ones that I prefer myself (Firestorm and Phoenix) at http://www.phoenixviewer.com . You may always choose to use another viewer (or switch among several) when you get used to being in SL, but the most important thing now is to get you started. This may be the best way.
  11. Ah.. Oops. Right thought.. My brain went left on me. Still, you can pack many numerical variables together as a single integer.
  12. Esta é a quarta cópia da mesma questão. O original está em http://community.secondlife.com/t5/Portugu%C3%AAs/minha-compra-fiz-agora-5000-lindens-por-favor-estou-aguardando/qaq-p/1015423 . Por favor, não ficar repetindo a mesma pergunta. Se você tiver mais informações para adicionar, use o link Opções no canto superior direito e selecione EDIT. Se você está preocupado com uma ordem de mercado que não foi entregue .... Para obter um registro dos itens individuais em sua ordem, de mercado aberto e clique no menu My Marketplace no topo da página. Selecione Minha Conta> Histórico de Pedidos> no menu suspenso. Se você não receber itens dentro de cerca de 24 horas, você deve cortar e colar as informações sobre um item em falta a partir desse histórico de pedidos e enviá-lo em um IM ou notecard para o comerciante, juntamente com uma mensagem educada solicitando devolução. A maioria dos comerciantes são muito gentis e dispostos a entregar novamente. Isso acontece o tempo todo e eles estão conscientes disso. Fazer, seja paciente, no entanto. Nem todo mundo faz login no SL a cada dia ou cheques seus e-mails. Se você ainda não ouviu falar em outro dia ou dois, siga-o com uma nota segundo educado e, finalmente, se você ainda não ouviu falar, um arquivo ticket de suporte em https://support.secondlife.com/create-case /, a seleção de mercado a partir do menu suspenso.
  13. Duplicate questão. Original afixado no http://community.secondlife.com/t5/Portugu%C3%AAs/minha-compra-fiz-agora-5000-lindens-por-favor-estou-aguardando/qaq-p/1015423. Por favor não coloque várias cópias da mesma questão.
  14. Duplicate questão. Original afixado no http://community.secondlife.com/t5/Portugu%C3%AAs/minha-compra-fiz-agora-5000-lindens-por-favor-estou-aguardando/qaq-p/1015423. Por favor não coloque várias cópias da mesma questão.
  15. Se você tem uma questão de faturamento, tente telefonar para um destes números: Toll-Free (EUA / Canadá) 800.294.1067 Longa Distância 703.286.6277 LL equipe de faturamento está disponível 24 horas por dia, sete dias por semana. Locais números de discagem gratuita * França: 0805.101.490 * Alemanha: 0800.664.5510 * Japão: 0066.33.132.830 * Portugal: 800.814.450 * Espanha: 800.300.560 * Reino Unido: 0800.048.4646 * Suporte está em Inglês apenas
  16. If you use the Billing Office phone number for a non-billing issue, you will be referred to Live Chat (if you are a Premium member) or advised to submit a supprt ticket at https://support.secondlife.com/create-case/ . There is no support phone number.
  17. It's a way to pass information from the rezzing script to another object as it is being rezzed. I suppose you can think of it as "storage" if you like, but the storage is in the sending script, not the object in inventory. After all, as others have pointed out, that object does not exist until it is rezzed in world. Void's observation is just that if you have updated information that an object will need when rezzed, you can pass it at that moment ...... if you can cast it as a string variable. If you have many variables to pass, concatenate them with a unique delimeter between them and then unpack them on arrival and recast them to their proper data types.
  18. Der Charakter Test ist in der Regel erfolgreich zur Lösung des Problems, die Sie beschreiben, aber es ist nicht die einzige Möglichkeit. Werfen Sie einen Blick auf diese andere Vorschläge >>> http://wiki.phoenixviewer.com/doku.php?id=avatar_unvollstaendig . Sie wurden für Menschen, die die Phoenix-Viewer verwenden geschrieben, aber die Lösungen sollten für jeden der anderen Zuschauer auch.
  19. See >>>> http://wiki.secondlife.com/wiki/How_do_I_configure_my_software_firewall_%28such_as_Norton_Internet_Security,_McAfee_Personal_Firewall,_or_ZoneAlarm%29
  20. Teen Second Life no longer exists. We are all on the main grid, where teens are restricted to regions with a General rating. See http://community.secondlife.com/t5/English-Knowledge-Base/Maturity-ratings/ta-p/700119 for information about the rating system. Teens under the age of 16 may only enter SL if they are sponsored by an organization like a school or youth program that owns their own estate in SL, keeps that estate private (that is, inaccessible to outsiders), and limits the teens to that estate. These restrictions are meant to protect teens from potential predators as well as from influences that many would consider harmful to their emotional growth. See >> http://wiki.secondlife.com/wiki/Linden_Lab_Official:Teens_in_Second_Life.
  21. That is high packet loss, and it could account for the trouble you're having. You didn't say, but if you are on wireless, get off it and onto a direct cable connection. If you are on a cable connection already, try temporarily bypassing the router entirely by plugging your cable directly into the modem to see if your router is bad (or has drivers that are out of date or borked). Check with your ISP to see if they are having server issues or are doing maintenance work in your area that could account for the problem.
  22. If you are looking for someone to write a script for you, the best place to ask is in the Inworld Employment section of the Commerce Forums (http://community.secondlife.com/t5/Inworld-Employment/bd-p/InworldEmployment). If you are looking for a script that already exists, try Marketplace or the Wanted section of the Commerce forums (http://community.secondlife.com/t5/Wanted/bd-p/Wanted).
  23. Be sure to use llSetStatus(STATUS_ROTATE_X | STATUS_ROTATE_Y,FALSE);
  24. Log in to http://my.secondlife.com/rod.Levee and do the obvious stuff.
  25. As you probably know, that error message generally means that your account has been put on hold. It can mean something drastic -- you have been suspended or banned -- or it could mean that LL has noticed an irregularity in your billing or some other account activity that they want to investigate. Or it can simply mean that there is a momentary server issue. So, almost anything from "Don't worry. Try again tomorrow." to "Don't call us. We'll call you." In any case, the only people who can fix the problem are at LL. It sounds like the Live Chat person is already forwarding your request to expedite review. I'd suggest seeing if it does clear itself up in a day or so, and then submitting a formal support ticket if it doesn't.
  • Create New...