Jean Horten

That Machine is a typical business laptop for basic office use, web browsing and all that entry level stuff people do on computers in standard office/business usage. It will not run Second life well, it might run SL with lowest graphics settings, but don't expect to get high fps rates from the integrated Intel HD4000 graphics chip . J.

Bondo Quixote wrote: I checked and the only way to get Snow Leopard is to buy it on disk and have it mailed to me. I have no idea why Apple won't sell it as a download, but damn, that's stupid. Looks like no SL for my trip. Think I'll just save up my pennies and buy a Chromebook. **bleep** Apple if that's their attitude. Don't expect to find a way to run Sl on a chromebook. J.

Ramona Beck wrote: For 2 weeks now my Firestorm screen freezes every time I right-click mesh to edit something my avatar is wearing and I have to "force quit" and re-log which takes 2-4 attempts to log back in - as far as I can tell this only occurs in certain places i.e. my skybox and my friend's skybox which is in a different region to my skybox although there could be more places. He also has this problem in those 2 places. If I use the inventory folder to obtain the edit option and I'm extremely careful not to click my avatar in any way I do not crash. If i right-click on a furniture item not attached to my avi I don't crash. If I go to a sandbox I don't crash. I am not using the Firestorm beta. I am using Firestorm 4.4.2 (34167). My computer is a 64-bit Windows machine running Windows 7 Home Premium and is not very old. I have an ASRock Z787M Extreme4 graphics card which i have checked for updates and there is none available. My computer is only a few months old. I do not over-clock. I have ADSL2+ cable internet which is stable. Does anyone know how to fix this annoying problem? You did not state which hardware you're using, your so called 'Graphics Card' is a obviously misspelled mainboard name, so helping you is not possible at this moment. J.

friscolives wrote: The title pretty much explains my frustrations at the moment. Tonight so far i've crashed at least ten to fifteen times. I've used both the SL viewer and the Firestorm version of SL. I uninstalled both, did a reinstall, and still crash with the new ones. I don't know what's going on, but its really frustrating. I'm not sure if i'm the only one dealing with this, but its not a good impression to make--especially with the new Linden CEO just starting. I kind of hope that person tries to log in and gets to experience the same stuff i've dealt with all night. Maybe a new programmers looking for work in the morning hopefully. Don't expect to get any support on that cant without any technical background information.

Both, the viewer's exe file and theslplugin.exe require to be allowed to access the internet. Seems the slplugin.exe is being blocked by your security settings. J.

Es macht keinen Sinn, fuer ~30 ct/Stunde in Sl zu arbeiten.

Go to a local computer store and have a machine built according to your needs. Then you can even get around that Windows 8.1 crap. Buying at a local dealer has several advantages, you don't have to ship the machine way across a whole continent in case of repair, you don't need to deal witrh anonymus call center guys if you have problems etc pp. It's a computer, it does not matter which brand name is written on the case, the inner values like cpu/gpu/memory/psu are important. J.

I presume a graphics card failure here, do you still have warranty on that card? If yes, have it replaced. J.

Cerise Sorbet wrote: Going to echo the others, fglrx does the job for me. It's nice that those driver projects take note of the standards, but they really need to take note of Postel's law too. Wait and see what happens when xorg1.15 hits your distro....

No tech savy person uses free drivers for Nvidia cards under linux unless this person intentionally wants his gpu performance reduceded by up to 90% Phoronix: Open-Source Nouveau Driver Remains Slow For NVIDIA's Fermi, Kepler The free Nvidia nouveau drivers are for oss fundementalists only (like Richard Stallman) who don't browse the web directly and who still run cli based linux from scratch to work in emacs. J,

Hiro Fluffy wrote: Another thing that helps is to support the API the video card was designed to use. All consumer video cards are highly optimized for DirectX but for some reason LL only supports OpenGL, which means the entire rendering engine of Second Life is coded to use a rendering API that is thrown in as a gimme for compatability reasons on every consumer GPU. Switching to DirectX would give SL an immediate performance boost measurable in thousands of percent. How much would you be willing to pay for a DirectX SecondLife? It's not only about *gimme for compatibility reasons', it's also about paying Microsoft a lot of money for being allowed to license and use MS'ses Windows only proprietary DirectX instead of license fee free open source OpenGL Switching to DirectX by the way would exclude everyone who is not running Windows ,about 25-30% of all users, from SL completely., which would make stings lite tiers even more expensive. J. P.S. Thousands of percents immediate performance boost with proprietary DirectX? Expecting 400 FPS on a 50 US§ AMD GPU with DrectX? You have not understood a single bit of SL's technical background!

Pussycat Catnap wrote: Dante Seminario wrote: So I have been reading up on Singularity and how much it's suppose to boost fps and run the game smoother, so I downloaded it, compared it to the Second life normal viewer and the normal one actually runs a higher fps.. Why would this be? Almost every TPV claims it runs better than the official. Most of these claims are based on tests against V2, not V3, or on buggy versions of V3 - and the comparer then rarely goes back to look again. I've found that overall, with most versins of V3, it gives me the best performance. Every so often LLs goofs and there's a version out for a month or so that is bad, but then it goes back to being on top. So, how to compare current tpvs and a V2 viewer? J.

Well, the advantages of Multiarch. The user now does not have to install one metapackage but can figure out which libs are necessary and install them all manually. ( which of course only works for packages available in .deb format, yay!) Extremely convenient move, realised by the idiotic Debian devs and now adapted by Ubuntu ( thus coming in Mint 16 too) who introduced Multiarch to make devs' and packagers' lives easier without spending one single thought on their users. Wo needs users anyway? The only advantage of the removal of the ia32-libs is that Firestorm finally moved their prolonged back and work on a 64 bit linux version, wonder if LL will follow. Of course, as it's Firestorm powered by Microsoft © a fairly useless WIndows 64 bit version has to be released first, otherwise the Widowsians would revolt or burst out in tears.

Storm Clarence wrote: Qie Niangao wrote: For a while now I've been using the release candidate viewer for advanced particles, despite the fact it crashes very often for me in Mesh-rich environments. In hopes of getting a less crashy viewer, I went to download the official release, which is billed "Download the SL Viewer on Linux Version Number: 3.6.7.281795"-- but to my amazement, it tries to download the same crashy -79 3, now promoted to the official release!) I don't have a direct answer, Qie, but I tried Singularity on CentOS 6.4, also with 64bit libs--and it didn't work so well. I get the Firestorm viewer up, but it runs just as poorly as Singularity. I am getting 1-3 FPS on a 50mbit connection for both viewers. And both viewers blow-up after a short time. I know it is my graphics card Intel HD4600, which is a very good card for 3D, but apparently not SL. I'm running kernel 2.6.32-358.18.1.el6.x86_64 and the Intel i915 graphics driver; built for the i7 (4G Haswell) I think I need to do a lot more tweaking, perhaps upgrade kernel to a 3.x version. I could re-write the driver from the current specs, but I just don't have that kind of time, nor am I that interested as only SL is affected. Maybe, Qie, an upgrade of your kernel compiled with some new drivers/mods. ETA: The official SL viewer also gives me 793. Comeon, you're using one of the most outdated Linuxes around and wonder why an up to date viewer gives you problems while telling people to upgrade their kernels? Your Kernel 2.6.32 was released in december 2009, almost 4 years ago, time to move on to something more up-to-date if you want to run the latest viewer versions. Wondering how outdated your graphics driver is in CentOS...

Go to the directory where you unpacked your viewer archive, look for a file called (viewername).sh and run that one I'd recommend to use a 64 bit viewer on 64 bit systems ( Singularity or Kokua)

I do not know any tablet that is capable of running a fully featured SL viewer, these toys don't come with a graphics card that can handle SL. You can use a text based client to log in on them.

Hehe, Auch wenn ich das ae durch den dementsprechenden Umlaut ersetzte, gibt mein Duden dafuer nichts her....

One more thing coming to my mind: You don't happen to use a laptop with Nvidia Optimus hybrid intel/Nvidia graphics? J.

Yay, finally, link your SL to your RL. Uhm, be careful if you're something like a elementary school teacher in RL and a cruel BDSM master or worse in SL.....

Hi. GTX 460M indicates it's a laptop. It's rather unlikely that you can replace that card with another one, that's one of the 'advantages' of mobile devices. Have you tried a different viewer? There are a lot of other third party viewers available besides that 'Firestorm' thing, you might give one of them a try. J. P.S. Have you ever cleared your cache?

Freya Mokusei wrote: I have seen this issue too, it seems to be caused by a traffic choke somewhere upstream - I would suggest your router, but honestly the solution seems a little different for each person at the moment. I am still investigating. Suggest these steps:- If you're on WiFi, stop that. Toggle HTTP textures in the Advanced menu - if it's currently on, disable it. If it's currently off, enable it. If you have a spare router, configure this for use and test again. If your router is from the same decade as your laptop (likely), it could well be failing, Disable any indexing being carried out in the cache folder. Disable or re-evaluate any Firewall rules running on ports: 53, 80, 443, 12043 or 12046. Information that would help:- If you could paste your primary and secondary DNS hosts this would be useful for my research into this issue. If you don't know what this means, ignore it. Find your overall connection speed using http://speedtest.net as well as your typical ping sim (found in Statistics Ctrl+Alt+1). Test to see if nslookup responses are intermittent during your crashes. If you don't know what this means, ignore it. Your entire computer seems on the low-end for the SL experience. I am doubtful that you will get good results in busy places even if this issue is resolved. Note that WinXP is now EOL. Any solutions that I come across will only be tested on Win7 and above. Win XP will still get support for 7 months

Muireann McMillan wrote: Hello, I have started getting regular crashes in busy places. This happens with both stock SL and Catznip, and started around the time Server Side Appearance was deployed (I did get some crashed before but much more rarely). Crashes seem to be hardware related, as another laptop with the same software runs fine. The affected PC is a 2006 laptop. It should NOT have overheating issues as it was taken apart for cleaning recently and also has a good fan system under it. It is a Dell Latitude D620 with the NVidia NVS 110M chipset. It runs Windows XP. I have to use the drivers provided by Dell, as the ones from NVidia (selected for this specific chipset) say that they can not find supported hardware, and fail to install. In the download notes it does say Dell notebooks are not supported. So I don't have the option of a driver update, unless perhaps I use Windows 7 or 8 instead. (Or Linux, but I think there is voice trouble and no video support under Linux?) I'd prefer to have things running in XP. Are there any changes that I can make to SL settings or Windows settings that could possibly tackle the crashes? Thanks! Voice and streaming media work perfectly under linux unless you use a 64 bit linux and a 32 bit viewer

As long as LL will not ban my favorite viewer that still uses the old V1 UI, I don't care. I can't use official viewers anyway, they have limited functionality and cause tons of errors on my operating system.

Griffin Ceawlin wrote: Click the arrow at the left of the line that says (Nearby chat). The awful new CHUI chat box, there's hardly a way to waste more screen real estate

Voff Uggla wrote: I've read in another topic, that cache should almost never be cleared now, only as a last resort if there's any problems. As compared to several years ago, it was suggested to clear cache almost everyday. So now I want to go to the bottom of this. First of all, in the Graphics Tab -> Hardware - 'Viewer Texture Memory Buffer', the maximum is set to 512 MB. My question is, if that folder on my computer exceeds 512 MB, shouldn't I clear the cache then? I mean if I have more MB than the maximum, it must mean the texture folder is full and need to be cleaned...?! Same question about 'Total Cache Size', there is a maximum of MB there as well. Common sense tells me that's maybe it's time to clear cache if that folder exceeds the limit of MB set in the viewer. Common sense is not the same as being a programmer/computer tech specialist, so please can anyone explain, how the cache works and when to clear it. The cache is a dynamic folder where textures and other things are constantly being added when they are being downloaded by your viewer, Stuff that's not required anymore will be discarded. Clear chache only when you run into issues with misformed prims, weird looking textures or when you upgrade yor viewer. If your texture buffer folder or cache folder is set to a certain size, it cannot exceed this size (as it is being set to than max size in your viewer's prefs), the viewer will automatically discard unused stuff inside them. The old ' Clear cache and relog, if it won't fix it, clear cache and relog aagain' recommendation, made especially by the supporters of one certain TPV is wrong, if you clear cache when having a bakefail or similar things, it will make things worse instead of ressolving issues. Clearing cache was/is no general means of fixing things. J.