Jump to content

Whirly Fizzle

Advisor
 View Profile  See their activity

  • Posts

    4,719

  • Joined

  • Last visited

 Content Type 

Posts posted by Whirly Fizzle

    Deploys for the week of 2013-04-01

    in Second Life Server

    Posted

    I have also been seeing missing prims with increased frequency since yesterdays roll. In particular certain prims of the building I usually login standing on.

    Location: Veil of Shadows

    sim9873.agni.lindenlab.com (216.82.46.15:13010)
    Second Life Server 13.03.22.272563

    Maestro Linden wrote:


    1) Note whether the missing objects are whole linksets or only certain prims in linksets.  Interest list issues would generally affect whole linksets.  A viewer rendering issue or maybe a message-packing/decoding issue would seem more likley if only certain prims in linksets are affected.  It sounds like you're seeing at least part of the linkset, since you're able to select it.

    1) Missing objects are only certain prims of a linkset
    One of the prims that always goes missing is highlighted here

    missing prim.png

     

    Maestro Linden wrote:


    2) While the prims are missing, enable Develop -> Render Metadata -> Bounding Boxes, and see what bounding boxes appear.  You should see a prim-aligned bounding box for each prim, as well as a world-aligned bounding box that covers the linkset.  If you see a bounding box where a missing prim is located, or if the linkset bounding box extends to include the missing prims, then it's almost certainly the viewer's fault.  

    2) I see a bounding box where the missing prim should be (shaded pink where prim is missing)

    BBox.png

     

    Maestro Linden wrote:


    3) While the prims are missing, enable Develop -> Show Info -> Show Updates to Objects.  With this setting enabled the viewer will render a particle from each linkset/prim that it got an update for:

    * Red means a full update was received from the server (which has a full description of the object's visual parameters)

    * Blue means a terse update was received (which only includes information about a few properties, such as position and velocity)

    * Green means that an 'objectdelete' update was received (meaning that the object was either derezzed or is out of range for the viewer)

    If you enable this feature, and observe that the missing prims appear without a full object update being sent, then it's probably a viewer bug (in that the viewer knew about the missing prims the whole time, but
    initially
    failed to render them).

     

    3) Enabled show updates to objects and clicked missing prim.
    I saw a couple of blue object update dots

    Maestro Linden wrote:


     4) If you leave a region, then return to it, the viewer will load cacheable objects from the local cache, instead of getting the object details from the simulator.  If the object was loaded from cache and the appearance has been either fixed or broken since the last time you saw it, this would indicate a viewer bug.  You can verify that an object was loaded from viewer cache by enabling Develop->Rendering Metadata->Update Type; objects loaded from cache are shaded blue, with this mode enabled.

    4) With Update Type enabled and the prim still missing as it was on login, the missing prim is not shaded blue. Edited prim so it appeared then TP'd to another region for a few mins and TP'd back to last location.
    Same prim was again missing and not shaded blue.

    20130403160831842.png

     

    All repros so far have been on Firestorm with this certain prim since the rollout. It may possibly be coincidence this started after the roll though because I have seen missing prims before in other locations on both Firestorm and various builds of Viewer 3.

    I will use Viewer 3 later today and see if I can reproduce this.

    But from what you describe, this looks like a Viewer issue from my results?

    Deploys for the week of 2013-04-01

    in Second Life Server

    Posted

    Heya Maestro,

    Main channel included this fix: Updates for objects that are out of view are delayed for a maximum of 5 seconds, at which point they will be sent (mitigates BUG-1779[c]).


    I can still reproduce BUG-1779 when using the original repro with the Meeroos. The sliding of the Meeroos is no better on a main channel region.

    However the repro you gave on BUG-1779 using the coloured boxes does no longer reproduce.

    I have updated BUG-1779.

     

    Dynamic Pathfinding & Region Rebake Button

    in Second Life Viewer

    Posted

    Ferawri Enzo wrote:

    ...it caused the memory allocation to reach in upwards of 200 - 300 mb's which in turn caused many problems such as inventory issues, rezzing objects on the land were returned and error messages to follow, script errors, heavy lag and attchments not working propely.

     

    Ferawri.

    This bug is unfortunately not fixed yet and is especially bad on Homestead regions where the region will shut down attemps to rez when the memory allocation reaches ~ 230MB.

    Each time the region is rebaked, the memory allocation will creep up a little more (by approx 20-30 MB per rebake in my experience) and if you are doing a lot of terraforming, it does not take long to hit the memory allocation limit on a Homestead.

    This bug is being tracked under BUG-772 / MAINT-1957 (Simulator refusing to rez objects after 10 hour timeframe) so keep an eye out for a fix for this one in the deploy release notes.

     

    Something screwed up with the restarts today

    in Second Life Server

    Posted

    Cerise Sorbet wrote:

    I sort of expected that one to get annoying.

    This was a
    this week --
     

    Fix for 'IM does not respect "allow user to see my online status" flag in friends list' (
    )
    • If a friend does not have 'See my online status' permission, they will now see "User is not online .." message following IM or inventory offer.

    No **bleep**  lol

    I can see why they made that change but it's already irritating after one day on an RC :smileymad:

    Teleport and Uploading Errors

    in Second Life Server

    Posted

    If that does not work, another thing to try is disabling HTTP Textures.

    If your connection/router has problems with HTTP data, it can choke and disconnect you and the symptoms can be very similar to the DNS bug symptoms.

    On Viewer 3 or Firestorm: From the login screen, use CTRL+ALT+D to being up the Debug menu in the top menu bar then Debug -> Debug settings -> ImagePipelineUseHTTP -> set to FALSE

    Restart the viewer and login.

    If this does not help at all, set ImagePipelineUseHTTP back to TRUE again as it is best left enabled if not causing you any problems.

    Teleport and Uploading Errors

    in Second Life Server

    Posted

    It sounds like you have the "DNS bug".

    Symptoms of that include inability to upload any asset and disconnection on teleport.

    The workaround is to switch over to using Google public DNS .

    Queen Kellee has some nicely written info on this bug.

     

    For reference:

    VWR-26759 : Avatar does not appear to be fully connected to inworld grid / major loss of functionality

    VWR-25426 : Friendlist displays users as Unknown or (loading), teleports fail, assets will not save

    Hope that helps  :)

     

    Deploys for the week of 2013-01-21

    in Second Life Server

    Posted

    Heya Andrew et all,

    Bit sketchy on details I know, but incase useful...

    One of the Firestorm support teams partners was suffering from the Magnum issue.
    He could reproduce on both his main & alt account and on both his computers connected to the same home network - which was an ethernet openreach router.

    He switched ISP today back to BT fibre. He is using the same openreach router but in addition now has a new BT Homehub (http://www.productsandservices.bt.com/products/broadband/wireless-hub-router).
    He can no longer reproduce the Magnum bug using the same 2 computers & accounts.

    So, in his case it was connection related in some way, even though he had no issues at all on non Magnum regions.

     

    Deploys for the week of 2013-01-21

    in Second Life Server

    Posted

    Shayne Hesten wrote:

    Suggestion... let us forget all this rubbish about packet loss, high bandwidth, poor internet connection and the whole range of technical things that has been put forward in this thread, let us see a hand raised in the air to say, Sorry, we got something wrong, version 13 is at fault, we will roll back and start over.

    This is not a viewer problem, it is not a user problem, it is clearly an LL problem that, it seems, can be resolved very simply, as already witnessed.

    You're missing the point here.

    They are trying to find what is triggering this bug for certain Residents and not for others. All those affected must have something in common - question is, what is it? Certain settings in their viewer, certain type of router?  If we can find what that commonality is, it may help to point to the cause of the bug.

    For those affected by this problem on Magnum regions, it is not intermittant. They can reproduce it 100% on any Magnum region and only on Magnum regions.

    For those unaffected, as far as I know, no one has been able to find a way to reproduce it at their end yet.

    For those of you having this problem and have a laptop, if you take your laptop round to a RL friends and test on their connection, can you still reproduce it?

     

    Deploys for the week of 2013-01-21

    in Second Life Server

    Posted

    Andrew Linden wrote:

     I wonder if Firestorm is using the a gradually increasing draw distance hack to help content get sorted near to far?  I've heard rumors of this feature in TPV's but do not know if Firestorm is using it.

     

    Yes Firestorm has this

    Under Avatar -> Preferences -> Firestorm -> General -> Enable Progressive Draw Distance Stepping

    Code is here: http://hg.phoenixviewer.com/phoenix-firestorm-lgpl/rev/f6b1dc9c6d32

     

    Andrew Linden wrote:

     

    Whirly, I take it that the packetloss is primarily happening on TP arrival?

    Not as far as I can tell. Their packetloss appears to stay constantly high while on Magnum regions.

     

     

    I am at the Skybox from BUG-1460 currently and I am unable to reproduce the problems on Firestorm. I have tried with a 1024 draw distance, a 64m draw distance and with both progressive draw distance enabled and disabled.

    I have been sending people affected by this to test on Viewer 3 also and they have the same symptoms.

    I have been unable to find anything in common between the people affected by this issue and those that arnt. But those affected appear to be able to consistantly reproduce on any Magnum region and those of us who cant reproduce it have not been able to find a way to trigger it yet.

    Could it possibly be only affecting people with certain router hardware? I have seen a couple of reports now of internet connections cutting out when entering  Magnum regions only.

     

    Deploys for the week of 2013-01-07

    in Second Life Server

    Posted

    Maestro Linden wrote:

    Ah, I see what you mean, Dora.  When I leave your parcel and cross the region border to the south, some of the objects in your parcel 'disappear'.  Usually just disappear temporarily, but the set of objects which disappear and the duration of the disappearance varies a bit with each crossing.

    When I crank up my draw distance to 256m, I see the problem - when the objects are 'missing', they are appearing in the wrong region.  For example, an object at 'Nautilus - Suniaton/25/8/23' is being rendered at the same coordinates in 'Nautilus - Sidobrim' when I cross into the latter region.  It's a little hard to see your objects since they're somewhat small, but if you make an object such as a 64m tall red 'pole', you can see it clearly in the horizon when it disappears from your parcel. I'm fairly certain this is MAINT-1341 (internal Jira), which is a viewer bug against the 3.4.1 development viewer (the issue does not appear in your sim when using the 'Second Life 3.3.4 (262321)' viewer).

     

    Heya Maestro,

    This behaviour is not new.  I am not sure if it is even a server bug because it does not appear to occur on Phoenix viewer, but does occur on Viewer 3 and Firestorm.

    I believe this behaviour is what was reported at BUG-621

    What seems to happen is is that when crossing to a neighbouring region, some of the objects from the previous region "follow you over" for a couple of seconds until you move your avatar or cam. The objects you primarily see are objects that occupy the same coordinates as you although in the previous region.

    Is this a viewer or a server issue?

    Further reports of this are on the Firestorm JIRA:

    FIRE-8626 Sim build ghosting to next sim during border crossing

    FIRE-7586 Some objects disappear from regions (become invisible) while user crossing boundary of region  (from the 13/Nov/12, 10:53 comment onwards)

     

     

    Deploys for the week of 2012-12-10

    in Second Life Server

    Posted

    What is the name of the affected region?

    If you bring up the stats floater with CTRL+SHIFT+1 and look at the "Memory allocated" reading under "Physics details" what is the reading when the region is having this problem?

    If it is in the high 200's the region may have disabled rezzing until it is restarted.

    What is the exact message the tennants get when .. "the msg says the sim is not accepting them, it happens when i logon" ?

     

    SL VIEWER wont let me upload more than one image at a time when im online

    in Second Life Viewer

    Posted

    Do you have Apple's iCloud with the PhotoStream component installed?

    This will cause the symptoms you describe.

    The LL JIRA for this is a BUG so unfortunately is not public but you can see the same bug on the Firestorm JIRA HERE

    We have  workaround for Firestorm (see Step #10 in that issue's description) but doing the same on Viewer 3 does not appear to work and just crashes the viewer.

×
×
  • Create New...