
| Key: |
VWR-3353
|
| Type: |
New Feature
|
| Status: |
Open
|
| Priority: |
Normal
|
| Assignee: |
Unassigned
|
| Reporter: |
ZigZag Freenote
|
| Votes: |
9
|
| Watchers: |
1
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Issue Links:
|
Duplicate
|
|
|
|
This issue is original of duplicate:
|
|
VWR-5291
New features requested (CG asked me to Jira this)
|
|
|
|
|
Relates
|
|
This issue Relates to:
|
|
VWR-3156
Bring back Bandwidth And packet loss meters
|
|
|
|
 |
|
VWR-3364 Statistics window enhancements (reorder/regroup)
|
|
|
|
 |
|
VWR-1701 Connection stats displays in the viewer are becoming outdated/useless
|
|
|
|
|
|
VWR-2796 Lag meter refreshes too quick to read
|
|
|
|
|
|
This issue is related to by:
|
|
VWR-3363
Statistics window - FPS does not update when viewer is in the background
|
|
|
|
|
|
|
|
|
|
|
| Linden Lab Issue ID: |
DEV-6714
|
2 reasons:
- There is an outcry in
VWR-3156 to bring the meters back.
- The lag meter is big and clumsy and should get a smaller counterpart.
I went through several designs and this is what I came up with:
- I want to have sim fps, ping, net thruput (+packet loss) and client fps
- The bars should not mix bigger is better and bigger is slower
- The bars need not start at 0 (of whatever), they should start showing something when it has an effect
- The colors should not be green/red. Each should have its own color so you can tell which one lights up without counting them.
So, left to right:
- Server: zero bar @ 22.2ms (45 fps), full bar @ 100.0ms (10 fps), always orange
- Ping: 200-1000ms, always yellow
- Throughput: 0-<max_kbps_in_preferences>, color nice blue if packet loss <5%(TBD LL), red otherwise
- Client: draw time 0-200ms, green <100, otherwise dark red
or: draw time 75ms-200ms, always dark red
+ FPS bar needs to turn grey as soon as any power saving sleep is in effect (umm, more on that in another issue).
I know that the entire color scheme seems a bit dangerous, but I think it will never happen that all the bars will be high at the same time, so it shouldn't look too colorful. Well, should see it in action to really judge. But I'd give it a try.
Mouse hover would show the actual value (as now) + the resulting FPS for server and client.
Clicking the meter should open/close the lag meter.
The lag meter needs to follow the color scheme at least a little bit:
- When in background, the Client light should not turn green but grey.
- The Server light could turn orange instead of red. This would indicate there is not much you can do
about it and give you a color clue what is going on (distinguish orange vs. red with peripheral view,
not needing to check which one is not green).
|
|
Description
|
2 reasons:
- There is an outcry in
VWR-3156 to bring the meters back.
- The lag meter is big and clumsy and should get a smaller counterpart.
I went through several designs and this is what I came up with:
- I want to have sim fps, ping, net thruput (+packet loss) and client fps
- The bars should not mix bigger is better and bigger is slower
- The bars need not start at 0 (of whatever), they should start showing something when it has an effect
- The colors should not be green/red. Each should have its own color so you can tell which one lights up without counting them.
So, left to right:
- Server: zero bar @ 22.2ms (45 fps), full bar @ 100.0ms (10 fps), always orange
- Ping: 200-1000ms, always yellow
- Throughput: 0-<max_kbps_in_preferences>, color nice blue if packet loss <5%(TBD LL), red otherwise
- Client: draw time 0-200ms, green <100, otherwise dark red
or: draw time 75ms-200ms, always dark red
+ FPS bar needs to turn grey as soon as any power saving sleep is in effect (umm, more on that in another issue).
I know that the entire color scheme seems a bit dangerous, but I think it will never happen that all the bars will be high at the same time, so it shouldn't look too colorful. Well, should see it in action to really judge. But I'd give it a try.
Mouse hover would show the actual value (as now) + the resulting FPS for server and client.
Clicking the meter should open/close the lag meter.
The lag meter needs to follow the color scheme at least a little bit:
- When in background, the Client light should not turn green but grey.
- The Server light could turn orange instead of red. This would indicate there is not much you can do
about it and give you a color clue what is going on (distinguish orange vs. red with peripheral view,
not needing to check which one is not green).
|
Show » |
made changes - 20/Nov/07 02:32 PM
| Field |
Original Value |
New Value |
|
Link
|
|
This issue Relates to VWR-3156
[ VWR-3156
]
|
made changes - 20/Nov/07 02:32 PM
|
Link
|
|
This issue Relates to VWR-2796
[ VWR-2796
]
|
made changes - 20/Nov/07 10:54 PM
|
Link
|
|
This issue is related to by VWR-3363
[ VWR-3363
]
|
made changes - 20/Nov/07 11:49 PM
|
Link
|
|
This issue is related to by VWR-3365
[ VWR-3365
]
|
made changes - 27/Nov/07 11:27 AM
|
Link
|
|
This issue Relates to VWR-3364
[ VWR-3364
]
|
made changes - 29/Nov/07 10:56 AM
|
Link
|
|
This issue Relates to VWR-1701
[ VWR-1701
]
|
made changes - 30/Nov/07 12:14 PM
|
Linden Lab Issue ID
|
|
DEV-6714
|
made changes - 22/Dec/07 02:13 AM
|
Workflow
|
jira
[ 17021
]
|
jira-2007-12-21
[ 24756
]
|
made changes - 22/Dec/07 02:24 AM
|
Workflow
|
jira
[ 24756
]
|
jira-2007-12-21
[ 25427
]
|
made changes - 22/Dec/07 03:16 PM
|
Workflow
|
jira-2007-12-21
[ 25427
]
|
jira-2007-12-22
[ 31662
]
|
made changes - 22/Dec/07 03:37 PM
|
Workflow
|
jira-2007-12-21
[ 31662
]
|
jira-2007-12-22
[ 33734
]
|
made changes - 22/Dec/07 08:29 PM
|
Workflow
|
jira-2007-12-22
[ 33734
]
|
jira-2007-12-22a
[ 38862
]
|
made changes - 22/Dec/07 08:54 PM
|
Workflow
|
jira-2007-12-22
[ 38862
]
|
jira-2007-12-22a
[ 40335
]
|
made changes - 22/Dec/07 09:45 PM
|
Workflow
|
jira-2007-12-22
[ 40335
]
|
jira-2007-12-22a
[ 42820
]
|
made changes - 22/Dec/07 10:08 PM
|
Workflow
|
jira-2007-12-22
[ 42820
]
|
jira-2007-12-22a
[ 44182
]
|
made changes - 12/Mar/08 05:26 PM
|
Link
|
|
This issue is duplicated by VWR-5291
[ VWR-5291
]
|
made changes - 13/Nov/08 11:02 AM
|
Workflow
|
jira-2007-12-22a
[ 44182
]
|
jira-2008-11-14
[ 62474
]
|
made changes - 13/Nov/08 11:18 AM
|
Workflow
|
jira-2007-12-22a
[ 62474
]
|
jira-2008-11-14
[ 68197
]
|
made changes - 13/Nov/08 04:33 PM
|
Workflow
|
jira-2008-11-14
[ 68197
]
|
jira-2008-11-14a
[ 88162
]
|
made changes - 13/Nov/08 04:49 PM
|
Workflow
|
jira-2008-11-14
[ 88162
]
|
jira-2008-11-14a
[ 93191
]
|
made changes - 13/Nov/08 05:00 PM
|
Workflow
|
jira-2008-11-14
[ 93191
]
|
jira-2008-11-14a
[ 97145
]
|
made changes - 13/Nov/08 05:10 PM
|
Workflow
|
jira-2008-11-14
[ 97145
]
|
jira-2008-11-14a
[ 101014
]
|
made changes - 13/Nov/08 05:28 PM
|
Workflow
|
jira-2008-11-14
[ 101014
]
|
jira-2008-11-14a
[ 108105
]
|
made changes - 13/Nov/08 05:49 PM
|
Workflow
|
jira-2008-11-14
[ 108105
]
|
jira-2008-11-14a
[ 114967
]
|
made changes - 13/Nov/08 06:04 PM
|
Workflow
|
jira-2008-11-14
[ 114967
]
|
jira-2008-11-14a
[ 120482
]
|
made changes - 13/Nov/08 06:25 PM
|
Workflow
|
jira-2008-11-14
[ 120482
]
|
jira-2008-11-14a
[ 128664
]
|
made changes - 13/Nov/08 06:43 PM
|
Workflow
|
jira-2008-11-14
[ 128664
]
|
jira-2008-11-14a
[ 135113
]
|
|