Jump to content

Alyssa Jessop

  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Alyssa Jessop

  • Rank
  1. Google DNS did the trick for me too. TY To Valerie for pointing me here.
  2. I noticed earlier this week that I was unable to see my mesh avatar when I logged in. I had been running Firestorm v4.0.1xx and have been getting the notices that there was an upgrade available, so I thought maybe doing the upgrade would fix my problem. So. I followed the instructions for doing a clean install on my Mac (removed the app, deleted the Firestorm folders from Application Support and Cache folders), and started it up. Still no mesh. I am running OSX Lion, 10.7.4 with more than adequate hardware to support secondlife including 8gb RAM, 512 gb vRAM and a core i7 processor. What happened over the last few weeks that I can no longer see Mesh? I suspect it has something to do with SL's upgrade to 3.3.3, but i'm not sure how to fix it. Please help!?
  3. An update: I installed Snow Leopard and logged into SL and found that these problems had disappeared, so clearly it is related to the OpenGL issues mentioned earlier. I then upgraded to Lion and things continue to run smoothly. On a happy side note, upgrading to snow leopard (not clean install, upgrade) freed up 10gb of hard drive space, lol.
  4. Interesting! Thanks for the info guys, I'll try that!
  5. I recently made a purchase from someone on the marketplace, had an issue with the purchase and wanted to contact the seller, so I looked them up in search and read the blurb about looking at her picks to find out info on contacting them re: store issues, so went to look up her profile... No picks tab. No tabs at all. I had a friend check her profile and sure enough, he can see her picks and other tabs. But I cant.\ I can see other people's picks tabs, just not this particular user. Any idea why?
  6. Hi everyone, I know there are dozens of threads on here about alpha channel issues, but I couldn't find anything quite like what I'm experiencing on the forums or in any of the bug tracking articles I read so I thought I would reach out to the community for help. I am running Mac osx 10.5.8 (leopard) with 2gb of ram, a dual core 2.33ghz intel core 2 duo and an ATI Radeon x1600 graphics card with 256mb of dedicated Vram. I initially downloaded the latest LL viewer and logged back into SL after a fairly lenghty break. Things seemed to go fine, everything looked normal. Upon logging in for a second time, however, I noticed some weirdness going on with objects that had alpha textures applied to them. The faces that were supposed to be invisible were not. They were not solid either, but rather they had a sort of lattice of black and white and invisible pixels that would vary depending on view angle. Again, I've seen people who had issues with alpha textures appearing solid black or solid white, and I'm a little bit familiar with the OpenGL issues that alpha textures have endured since SL began years ago. This is different. I have a few screenshots to demonstrate but am not sure if It's kosher to post them in an op or not. When I disable basic shaders, the issue reverts to a more familiar issue with these textures turning solid black and/or white. Thinking this may be a viewer issue, I downloaded and instealled the latest Firestorm viewer, and lo and behold, things worked fine again on the first load. But upon exiting and re-entering the grid, the issue returned. This is only happening on objects that have had an alpha texture applied. On objects where I set the transparency to 100%, things display properly, and on lots of older objects like hair that have mixes of alpha and drawn texture, there does not appear to be an issue. This issue is only happening on faces and objects that have the 128x128 alpha or the 32x32 alpha textures applied to them from back in the day when 95% was the highest allowed transparency setting by default. It has the feeling of some kind of texture corruption to me, but I have no idea how to resolve this. Some people have said that it may go away if I upgrade to Lion, which I intend to do anyway, but in the mean time if ayone has a possible fix to this problem, I would appreciate the input. Thanks, Alyssa Jessop
  • Create New...