Jump to content

Aishagain

Resident
 View Profile  See their activity

  • Posts

    1,446

  • Joined

  • Last visited

 Content Type 

Everything posted by Aishagain

  1. Aishagain
    @RaeganBriana Dream on!
  2. Aishagain
    @Beq Janus Thankyou for this post...I am fairly sure I understand SL rendering better having read this, and that is a fairly major accomplishment!
  3. Aishagain
    In my perambulations of SL today I now see that there are two software versions on RC channel sims, 556138 from last week's Deploy (or was it two weeks ago?) to "Oranges" and the new one 556225. I think this is as LL intended but it was a surprise! As far as I could tell both worked OK.
  4. Aishagain
    *Sigh* Well if the post on the Grid Status Page was: 1) Not an automated standard format, frequently posted without ANY reference to what will actually happen. 2) Updated with correct information near the actual operation. I might agree with Solar. However it is frequently innaccurate and to my mind thoroughly untrustworthy. Solar is right in wanting an explanation for restarts like today's on/off/on farrago. Posts to this forum annoy Solar when HE considers them unneccessary. Clearly so does almost anything I say. So it goes. If the SL operation did not look like a confused mess, the lack of committment to posting info on this forum would be a bonus not a necessity.
  5. Aishagain
    @Solar LegionThere seems to be some confusion here. That there was no change to report is one thing...That nothing HAS been reported is quite another. If there is to be "no change" then the post is that there will not be a roll to Main Server. That is the convention. As it happens my region was NOT rolled until I prodded support, so that is another aspect. It would have been courteous of LL to let us know this prior to today but more to the point this is the third time recently that our region has been "omitted" from the schedule. Last time I restarted the region after more than 15 days continuous running. Today it was 21 days, as reported above by @Willow Wilder.
  6. Aishagain
    @Rowan AmoreI used the term as a reference to a storied unresponding entity, I had no intention to cause offence, I did not, for a moment, make such a connection. I will not use it again. The fact remains that for whatever reason, the Main Server Roll has come and gone today without any post on this forum from LL. @Profaitchikenz HaikuYour reference to the pandemic is understandable but the work of Linden Lab is, I suggest, one of the best examples of a company that can perfectly well function in a "work-from-home" environment.
  7. Aishagain
    And the Roll has started and the Server Release Thread tarbaby he say nuttin'. NOT. GOOD. ENOUGH.
  8. Aishagain
    Seems she has another nickname. Deafity. A name shared by other customer- facing Lindens. Sorry, I know this is harsh, but this situation has gone beyond normal boundaries. Why is this happening?
  9. Aishagain
    I know the Grid status page says it will happen and we have a fair idea of what was rolled to some of the RC channels last week...but what is coming to Main Server this week? Will it be 556138? I know it's only late afternoon PST, but it is nearly 1am in the UK and 2am in Western Europe. It'd be nice to know what was coming before we are up and about in RL in that part of the world; we make up a substantial part of the SL population so please indulge us LL and publish the server thread for the rolls before we go to bed in RL...please?
  10. Aishagain
    @Verona VoxelI am assuming throughout this that "Verona Voxel" is your legacy (user) name and not display name? LL viewer search will not recongnise nor search display names, I am told but FS will, perhaps because it can use legacy search (as you no doubt have realised). I believe websearch is not functioning for anyone properly since the uplift to the cloud and like many services that have been thus affected progress to a solution seems slow to none.
  11. Aishagain
    @Fredz Faulkes Having racked my brain to recall what I experienced, I have a suspicion that it might still be your AV/Firewall interfering with the download of the installer package. You might want to check the security level you have set. It may be identifying downloaded packages containing .exe files as potential security risks. ETA: It never occurred to me to ask, are you running a double monitor set up...see Dan Linden's post below and the forum thread mentioned there.
  12. Aishagain
    @Lillith HapmoucheCrystal. Tell AMD!!
  13. Aishagain
    I'm just a little wary of that statement. LL said EEP was fixed, complete and ready to roll out over a year before it appeared in a viewer that many could use, and we have it bugs 'n' all. So I am not holding my breath...yet. 🤫
  14. Aishagain
    @Lillith Hapmouche Nope. ATi/AMD applications to OpenGL are still and have been for as long as I've used computers, vastly inferior to NVidia. It's not an opinion it's a proven fact, notwithstanding the recent issues with an ATi GPU driver causing colour issues in most viewers to SL. If you mean we should not the calling AMD stuff ATi, tell them, not me. I am not purblind to the inadequacies of NVidia gear, it's just less problematical (and granted a lot more expensive).
  15. Aishagain
    I wonder if when interfacing with the latest AMD/ATI GPU driver this function is messed up? The question then would be "was it the driver or the viewer" that is at fault? Maybe one of the Firestorm devs who wander these pages at the weekend would care to comment? I'd be surprised if it is the GPU driver OR the viewer, frankly, unless there is some corrupted code in there. By the way, @PatricaC, just because you have the latest driver does not mean it cannot be bugged, both AMD and NVidia have issued badly bugged drivers in the very recent past.
  16. Aishagain
    Yes I did notice it, Solar, which is why I said it might be either the viewer or OS that was wrong....possibly due to being misled by the GPU driver software. Indeed WHY it is greyed out is what needs an answer. It being both checked AND greyed out clearly suggests an issue to me, but I do not know what the issue is.
  17. Aishagain
    @Qie NiangaoYou mention the "Firestorm 2GB VRAM cap". It isn't capped at 2048MB in the current version, 6.4.12. If your card has say, 6GB like mine, it permits 4096MB! This change for the current release was a significant upgrade, but whether some bug in the code that permits it is at the root of the OP's issue I do not know. Considering the bug-ridden mess that is EEP, anything is possible! And that thread you reference is one of the most confused rambles I've read in years, confusing GPU VRAM with system RAM on several occasions!😵
  18. Aishagain
    I think you are losing sight of the crux of the issue. The Viewer is not recognising the GPU VRAM. It can tell that the GPU has more than 2GB otherwise it would not even offer 2048MB as a limit. The issue must lie either with the card, its driver (which is my choice). Or the Operating system, which is clearly Windows 10, so the remarks about Linux, while interesting, are irrelevant.I am running this version of Firestorm on the same OS, using an NVidia GTX1660Ti 6GB card which is being detected fine. The GPU driver is not the most recent, or even close, since they have more bugs than I care to list. If memory serves it is 457.something forced on me by Windows update. I think the focus of this must be around the GPU and its driver.
  19. Aishagain
    @PatricaCnope that simply logs me into my Support requests and Bug reports. No matter I think FS support will be far more use to you than I!
  20. Aishagain
    Hmm weird it won't let me see it when I log in. Perhaps since it is a SUP number only support personnel and the originator are permitted to see it.
  21. Aishagain
    @PatricaC Well there is nothing in that to my eye that looks wrong. It seems that for some reason your viewer is not seeing the VRAM of the Radeon card. Now I tried to see your FS JIRA but it says either it has been deleted or I do not have permission to see it...no idea why that should be but I cannot assist in this issue further, sorry. There have been so many issues with AMD/Ati GPU cards over the years that I simply avoid AMD GPUs completely for SL. Now I realise that is no help to you but might explain the roots of the issue. ☹️
  22. Aishagain
    I may be missing something here but as I see it the GPU has 8GB VRAM and should permit at least 4GB to be used by the viewer. There would (or at least "should") be no texture thrashing if the VRAM was being correctly allocated. @PatricaCIn the top bar help tab "About Firestorm" is the GPU being detected correctly by the viewer? A Sapphire Nitro RX580 8GB card should run SL at high/Ultra settings with no issues. If the viewer is only seeing less than 4GB VRAM and the thrashing suggests it is seeing a lot less, something is not right, either with the viewer or the GPU. Further, I've looked at those two Imgur photos and I cannot see the texture thrashing that you refer to.
  23. Aishagain
    @Solar LegionMy fault then, senses of humour do not always cross borders successfully! A bit like SL sailing!
  24. Aishagain
    Ah @Solar Legion, you just don't "get" irony, do you?
  25. Aishagain
    @Solar Legion I see...so they hadn't enough code names with what they had, so we got Apples and Oranges as well as Snack... well I guess you're right but all that tells me is that LL spend more time dreaming up fancy names for their test packages that they do fixing the World Map!
×
×
  • Create New...