Difference between revisions of "TPVD/Developers Group Agenda"
< TPVD
Jump to navigation
Jump to search
(Adding voice issues to the agenda, due to continued reports of it being a V2 migration blocker.) |
|||
| Line 2: | Line 2: | ||
Current and Open Items: | Current and Open Items: | ||
# 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]] | |||
# The Future of Search | # The Future of Search | ||
# 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) | ||
Revision as of 07:07, 2 June 2011
Current and Open Items:
- 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
- The Future of Search
- Minimap coarse location messages, any possibility on getting that updated to support avatars over 1000m --Kadah Coba 13:13, 21 May 2011 (PDT)
- Drop date for Region WL yet? :3 --Kadah Coba 17:32, 31 May 2011 (PDT)
- Any updates on SVC-6917 & SVC-6760 & 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)
[12:28] Kadah (kadah.coba): Joshua, any updates on those 499s and caps failures? [12:28] Josh (joshua.linden): no update [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. VWR-25840, STORM-703, 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. "
Previous agenda:
- Direct Delivery - new delivery mechanism; Brooke Linden, Marketplace
- Any updates on getting detailed stats? --Kadah Coba
- Looking for documentation of crashlog / minidump processing, such as example server code, build tool integration, documentation of process, etc. --(Arrehn Oberlander)