Difference between revisions of "TPVD/Developers Group Agenda"

From Second Life Wiki
Jump to navigation Jump to search
m (link jira issues)
Line 1: Line 1:
<!-- Add agenda requests at the end, and please put your SL Name in the request (use --~~~~ to insert your signature) so I know who to contact for any clarification -->
<!-- Add agenda requests at the end, and please put your SL Name in the request (use --~~~~ to insert your signature) so I know who to contact for any clarification -->


Current and Open Items:
'''Current:'''
 
'''Open Items:'''
# Any updates on getting detailed stats? --[[User:Kadah Coba|Kadah Coba]]
# Drop date for Region WL yet? :3 --[[User:Kadah Coba|Kadah Coba]] 17:32, 31 May 2011 (PDT)
# Drop date for Region WL yet? :3 --[[User:Kadah Coba|Kadah Coba]] 17:32, 31 May 2011 (PDT)
# The Future of Search
## Project viewer out, code pending --[[User:Kadah Coba|Kadah Coba]] 21:30, 6 June 2011 (PDT)
# V1->V2 adoption issue, V2's vivox implementation appears unreliable in Push-To-Talk mode (V1 default and behavior many users wish to keep) due to faulty speech detection delaying when the microphone opens. See http://jira.phoenixviewer.com/browse/FIRE-1154. Looking for possible advice on how to address this. Is it something embedded in the vivox binary, or is the behavior tunable in some way within the viewer source? Looking for a vivox point of contact at LL. [[User:Arrehn Oberlander|Arrehn Oberlander]] (also the gain/noise canceling/whatever cause most people using the V2 vivox to be either too loud or too quiet, we had this very issue when we back ported the newer vivox to 1.5 and had to revert it a week later as most of us were unable to hear others or be heard during meetings. --[[User:Kadah Coba|Kadah Coba]] 10:09, 3 June 2011 (PDT))
# Vivox issues:
## V1->V2 adoption issue, V2's vivox implementation appears unreliable in Push-To-Talk mode (V1 default and behavior many users wish to keep) due to faulty speech detection delaying when the microphone opens. See http://jira.phoenixviewer.com/browse/FIRE-1154. Looking for possible advice on how to address this. Is it something embedded in the vivox binary, or is the behavior tunable in some way within the viewer source? Looking for a vivox point of contact at LL. [[User:Arrehn Oberlander|Arrehn Oberlander]]
# Minimap coarse location messages, any possibility on getting that updated to support avatars over 1000m --[[User:Kadah Coba|Kadah Coba]] 13:13, 21 May 2011 (PDT)
# Minimap coarse location messages, any possibility on getting that updated to support avatars over 1000m --[[User:Kadah Coba|Kadah Coba]] 13:13, 21 May 2011 (PDT)
# Any updates on {{jira|SVC-6917}}, {{jira|SVC-6760}}, {{jira|VWR-25940}}, and the 499/caps failures? Can someone find out why do a few users see these issues so much? --[[User:Kadah Coba|Kadah Coba]] 12:38, 31 May 2011 (PDT)
# Any updates on {{jira|SVC-6917}}, {{jira|SVC-6760}}, {{jira|VWR-25940}}, and the 499/caps failures? Can someone find out why do a few users see these issues so much? --[[User:Kadah Coba|Kadah Coba]] 12:38, 31 May 2011 (PDT)
[12:28]  Kadah (kadah.coba): Joshua, any updates on those 499s and caps failures?
# Looking for documentation of crashlog / minidump processing, such as example server code, build tool integration, documentation of process, etc. --([[User:Arrehn Oberlander|Arrehn Oberlander]])
[12:28]  Josh (joshua.linden): no update
## Oz mentioned there was related docs on the internal wiki --[[User:Kadah Coba|Kadah Coba]] 21:30, 6 June 2011 (PDT)
[12:29]  Josh (joshua.linden): still in progress, still high priority
[12:30]  Josh (joshua.linden): re: caps - It's entirely on our servers; it affects hosts, and is intermittent even when a host has "gone bad".
That's all I can really say. It's not your viewer or ISP
# Getting really tired of LL support and developers blaming third party viewers for things like asset failures, delivery failures and dozens of other things that have nothing to do with TPV's. Eg. {{jira|VWR-25840}}, {{jira|STORM-703}}, {{jira|VWR-25276}} (inventory items outside of inventory folder) As well as blames by LL support that Phoenix is responsible for displaying region prim counts incorrectly and dozens more like this. Also a quote from one of LL's support "SydahneP:  It's very possible.. We have linked most of the server issues from the latest update with the Phoenix viewer. " -- [[User:Jessica Lyon|Jessica Lyon]]
## And if a problem '''is''' related to a TPV, then come talk to us, don't just complain about TPVs. -- [[User:Tonya Souther|Tonya Souther]] 08:16, 2 June 2011 (PDT)


 
'''Previous agenda:'''
Previous agenda:
# The Future of Search
# Direct Delivery - new delivery mechanism; Brooke Linden, Marketplace
# Direct Delivery - new delivery mechanism; Brooke Linden, Marketplace
# Any updates on getting detailed stats? --[[User:Kadah Coba|Kadah Coba]]
# Looking for documentation of crashlog / minidump processing, such as example server code, build tool integration, documentation of process, etc. --([[User:Arrehn Oberlander|Arrehn Oberlander]])


[[Category:Third Party Viewers]]
[[Category:Third Party Viewers]]

Revision as of 21:30, 6 June 2011


Current:

Open Items:

  1. Any updates on getting detailed stats? --Kadah Coba
  2. Drop date for Region WL yet? :3 --Kadah Coba 17:32, 31 May 2011 (PDT)
    1. Project viewer out, code pending --Kadah Coba 21:30, 6 June 2011 (PDT)
  3. Vivox issues:
    1. V1->V2 adoption issue, V2's vivox implementation appears unreliable in Push-To-Talk mode (V1 default and behavior many users wish to keep) due to faulty speech detection delaying when the microphone opens. See http://jira.phoenixviewer.com/browse/FIRE-1154. Looking for possible advice on how to address this. Is it something embedded in the vivox binary, or is the behavior tunable in some way within the viewer source? Looking for a vivox point of contact at LL. Arrehn Oberlander
  4. Minimap coarse location messages, any possibility on getting that updated to support avatars over 1000m --Kadah Coba 13:13, 21 May 2011 (PDT)
  5. Any updates on SVC-6917, SVC-6760, VWR-25940, and the 499/caps failures? Can someone find out why do a few users see these issues so much? --Kadah Coba 12:38, 31 May 2011 (PDT)
  6. Looking for documentation of crashlog / minidump processing, such as example server code, build tool integration, documentation of process, etc. --(Arrehn Oberlander)
    1. Oz mentioned there was related docs on the internal wiki --Kadah Coba 21:30, 6 June 2011 (PDT)

Previous agenda:

  1. The Future of Search
  2. Direct Delivery - new delivery mechanism; Brooke Linden, Marketplace