Jump to content

Aishagain

Resident
  • Posts

    1,446
  • Joined

  • Last visited

Posts posted by Aishagain

  1. This is a phenomenon that I have only just noticed so I don't know if it is seen regularly, nor do I understand how it occurs.  My home region suddenly displayed it last night and the ping, which is normally 150-200ms for my location in the UK had risen to over 600ms.  It found that several other regions that I visited showed elevated ping, anything from 300-400ms to over 500ms, but some showed what I would consider "normal" ping in the 150-200ms range.

    Mutiple relogs made no difference, so I restarted my region...no change.  2nd restart the ping was lower, around 300ms but still curiously elevated.  a third restart returned the ping to "normal" and so it remains today.  Several other regions are still elevated, 300-450ms, and one, Cerridwen's Cauldron, which was normal yesterday, is now elevated as well.

    Now I have no idea how such variability could arise, since I assumed that all regions withing a virtual system such as SL would share the final stages of any signal route.  This is presumably not the case!  Is this now a result of SL being "in the cloud" via Amazon Web Services or am I missing something?

    I am assuming that the issue is not "at my end" since I observe no increased latency on any other applications I run nor do I see any delay in functions entirely within my PC.

    Anyone else see this phenomenon or have an explanation for it?

    • Like 1
    • Thanks 1
  2. Two things to check.  First is to ensure that all the elements of FS are "whitelisted" in you AV programme.

    See https://wiki.firestormviewer.org/antivirus_whitelisting?s[]=fs&s[]=whitelist

    Secondly I notice that your texture memory is pegged at 512MB in your settings.  By enabling Texture Memory Management in your viewer graphics>rendering preferences you ought to be able to access at least 2048MB of VRAM.  above that FS will slowly encroach on your system RAM which since you have 16GB should not cause a crash.  I note your session packet looss is 0.6% which is a tad high but since the session length was short that may be a red herring.

    This ridiculous CPU use phenomenon is not unknown but rare.

    @Beq Janus?

    • Like 3
  3. Some time ago I had a similar baffling issue with a DJ stream that simply would not run in my viewer, yet ran perfectly in all other audio applications.  I never did find out WHY but when I was running the viewer it triggered my AV to block the url.

    I only found out what was occurring when I discussed it in detail with my AV support and they told me that the domain had been blanket-blocked due to a single rogue instance with one url! They checked the domain and a couple of days later the stream ran as normal in the viewer.

    I never got an explanation of how a single  rogue instance had caused the issue.

    In this case I'd  be inclined to see if the security settings of the two computers were identical.

    • Like 2
  4. Look in the "worn" tab of your inventory.  You should be wearing a minimum of four items: Shape, skin, eyes and brow shape/bald cap (it has verious names).  If ANY of those are not worn you will not rez and you may need to take action.

    One way, if your inventory is fully loaded is to create a very basic outfit containing the four basic elements, Shape, skin, eyes, and brow shape/bald cap. all wearables not appliers of anything.  Log in, select the outfit and click "replace outfit"

    ETA; as I was typing this Rowan Amore gave you a useful link which you should read.

    • Like 1
  5. @AkiraKagami as all the above contributors note; you do not need 400fps for a perfectly smooth SL experience.  It is frequently claimed that the eye cannot detect anything above 30FPS.  Of course it can, but anything above say 70FPS is just wasting energy and in your case superheating your GPU and proably the rest of your PC in the process, leading to thermal shutdowns.

    If You use Firestorm use the viewer's own framerate limiter (in Prefs>Graphics>rendering) or if not use the Framerate Limiter on the NVidia Control Panel...the former is much preferable.

    • Thanks 1
  6. @Naiman Broome

    One common problem with downloading from the FS website is the firewall or AV blocking the d/l due to a certificate issue.  Usually the OS will tell you that the d/l is not reccomended but if you then click on the "other action" or "other options" button it should present you with a "download anyway" option.

    The  precise message varies depending on your OS (Operatiing System...Windows 10/11 or equivlent Apple version) and your security level set in you browser.

    Once the download is complete (as it should then be) proceed as normal.

    It is imperative to only download the viewer (whichever you choose) from that viewer's official website.  Accept no substitutes.

    • Like 1
  7. Y'know, this all still leaves me pondering...yes, the render process uses (or CAN use) multiple threads and in my case does, but that still leaves me unconvinced thatthese other referred threads are on other cores.

    I have carefully, nay, obsessively, watched Task Manager on my 12 core CPU and I'm damned if I see any activity outside of almost transient spikes of activity in any other than the first core, which is running at or near 100% all the time I am using the viewer.

    What am I missing?

    ETA: I am a Firestorm user...I detest the UI and functionality of the Default viewer.  I only use it when I need to convince LL of a bug.

  8. The Absence of any info regarding restarts to Main Server regions today is puzzling.  I have understood the new system whereby we should expect Main Server restarts on Tuesday and RC Channel restarts on Wednesday, new information being disseminated via the Tools and Technology Blog, new Server versions being outlined on the release notes. 

    All well and good...but....

    I noticed the absence of a "heads up" for Main Server regions on the Status Page over the weekend (the  potential of some limited deploy on selected RC Channel regions is reported), so I assumed the Main Server Regions were just getting their weekly "bounce" restarts.

    Today, nothing!  Now maybe I'm just too picky but doesn't the absence of a restart of ANY kind class as an unusual circumstance and isn't THAT worthy of some/any comment?

×
×
  • Create New...