Jump to content

Samm Florian

Resident
  • Content Count

    84
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Samm Florian

  • Rank
    Advanced Member
  1. You're probably right, but I'd rather it was Linden Labs tellin' me that. And I'd hate to see any long-runnin' contests disappear because the hosts are afraid of what might happen. Or look at it this way: we're tryin' to help LL "debug" their policies by considerin' all the potential edge cases of their policy.
  2. Does the term "game" include contests, such as building contests?
  3. Oh that's ridiculous! I ran 3.6.6 just the other day and it was fine…better'n fine, the first release that actually did Advanced Lighting correctly! How 'bout leavin' it up t'us t'decide. Well, back t'Firestorm fer me.
  4. Oh good! I was worried: I'm working with large lists which could theoretically reach the limit if the cruft weren't cleared away, and it's for a sale item where I don't want to have to go and reset everybody's products after 6 months. I will definitely add a memory check, but that bit I saw about "The heap never shrinks" scared me a little. Thanks! And you're right, I should do some testing…
  5. So if the list is changing pretty slowly, like once a day, then garbage collection should take care of it with no problem?
  6. I'm having trouble figuring out how Garbage Collection works in MONO scripts. If a script deletes items from a list, is the memory from those items released? More specifically, if I am adding and deleting objects from a list so that the list's size remains relatively constant, am I risking a stack-heap collision? I've seen some references suggest that heap memory, once used, is never reclaimed.
  7. I'm having trouble figuring out how Garbage Collection works in MONO scripts. If a script deletes items from a list, is the memory from those items released? More specifically, if I am adding and deleting objects from a list so that the list's size remains relatively constant, am I risking a stack-heap collision? I've seen some references suggest that heap memory, once used, is never reclaimed.
  8. This could be a big deal or it could be nothing. The question I have for LL is this: Are there any features in the current TPVs which violate this policy? For example, is RLV OK? Can Firestorm continue to show us which viewer another avi is using? What specific features did they have in mind when they wrote this policy, specifically the third one about the "shared experience"?
  9. But why would the router allow me to go online in SL, but then block certain parts of the viewer's functionality? I could understand if the router stopped me from logging on at all…
  10. Hi everyone. I have a question: recently I've been having a lot of trouble with Viewer 2.8: my groups wouldn't show up, music wouldn't play, and the little "Buy this Land" tag showed up in the location bar no matter where I was. (No, it didn't work; I tried! :) Now in the lists of troubleshooting steps I saw around on the web, I saw the suggestion to reboot one's modem and router, but I skipped that step because (a) my modem and router were upstairs at the time (lazy!) and (b) I couldn't see why it would matter. But nothing else I was doing worked. So today I'm using the internet away from home, and I decided to try out 2.8 here, and voila! Everything's fine. Which suggests that I really *do* need to reboot my modem and router when I get home. So my question: why the heck would that make any difference? It seems like total voodoo to me. Thanks! :)
  11. You'd think 3D would be simple for LL to implement: give everybody two cameras a certain distance apart, pipe both views to a customized viewer, and display one in red and one in blue (or different polarized light, or whatever). Would make building easier too: I reckon every builder's positioned one prim so it appears to be sitting on top of another, only to change camera angles and find that they're really 5 meters apart.
  12. I've been able to customize Firestorm so that it looks basically identical to V2 (with the Starlight skins)—no pie menu, no IMs in the local chat, etc; I'm still not sure whether I prefer it to V2 or not, but the customizability has made it easier for me to try it out.
  13. I have seen this problem off and on for a while, maybe since January. What happens for me is that anything with transparency, including textures with transparency, shows up as glowing instead. Setting "RenderGlow" in the DebugSettings to false makes this go away. This happens with all V2 viewers (V2, Kirsten, and now Firestorm) but not Phoenix. I'm usin' a Mac, and it seems to happen after I've used the DVD player, and only rebooting my computer fixes it. I posted a JIRA on it in April, but got no response. https://jira.secondlife.com/browse/VWR-25594 I reckon that it has something to do with the Graphics card, given how rebooting fixes it; but I don't know nothing about graphics cards.
  14. I think I was having the same problem on my Mac: the program would open a window that was blank white, and then just freeze. My solution was to download the beta viewer, 2.7.2, which does not have that bug. Yay!
  15. The use of social networks in conjunction with SL, rather than unqueering SL, can actually help to queer RL. Pretty early on in my SL life, I created an email address and a Twitter account for my avi, and have a Plurk account as well; it lets me spend a little time with my character throughout the day, when it would be inappropriate to boot up the old viewer.
×
×
  • Create New...