Current Project: HUD7

Note ID# 844:

User:	Lulu	Submitted:	05/04/2016
	Updated status to In Progress from New. Assigned to Lulu.

Note ID# 845:

User:	Lulu	Submitted:	06/04/2016
	Hey Miriam, I've dropped a beta uHUD your way. They should appear like this: [00:32] LULU Utility HUD [2.2-beta.1]: [LULU.HUD.utility.rlv.3.lsl]: 8106 bytes free. [00:32] LULU Utility HUD [2.2-beta.1]: [LULU.HUD.utility.rlv.1.lsl]: 7054 bytes free. [00:32] LULU Utility HUD [2.2-beta.1]: [LULU.HUD.utility.rlv.2.lsl] 23600 bytes free [00:32] LULU Utility HUD [2.2-beta.1]: Loading notecard 'LULU_AO Default'... [00:32] LULU Utility HUD [2.2-beta.1]: 5 animation entries found in Notecard. [00:32] LULU Utility HUD [2.2-beta.1]: Finished reading notecard 'LULU_AO Default'. [00:32] LULU Utility HUD [2.2-beta.1]: [ZHAO-II-core Lulu 0.98] 21208 bytes free The memory notification is allowed in uHUD (but not HUD etc.) because these are editable scripts, and we want the editor to know how much memory is left if they edit them. Would you be able to test whether the RLV relay works for you (you'll need some RLV relay toy of course)? The reason why we got the relay error was because I'd changed the way the relay worked originally, and I just want to make sure that it's working fine.

Note ID# 847:

User:	Miriam Himanez	Submitted:	07/04/2016
	Hi Lulu. On attach the uHUD's messages came up exactly like you posted them. Unluckily the relay seems to be very unstable. I tested by letting several devices trying to autograb me; used a relay-checker as well. After login the relay seemed to work well and the first device was able to grab me successfully, but failed attempts occured quickly afterwards and it seemed that the more successful attempts had been passed, the higher the failure-rate had been risen - until the next relog.

Note ID# 848:

User:	Lulu	Submitted:	09/04/2016
	Hey Miriam, Thanks for the update! Sorry I wasn't able to get the uHUD beta 2 ready in time. I've just dropped it your way. This new version still uses 2 cores, but hopefully I've sorted out the mess.

Note ID# 849:

User:	Miriam Himanez	Submitted:	09/04/2016
	I'm sorry, but I've got bad news: Like the last one, this uHUD didn't announce an error on attach either, but it's RLV-relay is still very unreliable. Many devices aren't able to recognize it's presence and even if they manage to do so, more than 50% of all grab-attempts fail. Furthermore does the relay tend to ignore other rlv-commands as well. (The release-command sent by a force-sitter for example, so I need to relog to actually be able to stand up again, because the "safeword" - option seems to have gone too, not just in this case - I didn't recognize it at all.)

Note ID# 850:

User:	Miriam Himanez	Submitted:	09/04/2016
	Like the 2 versions before, the Beta 3 didn't announce any error on first attach. In the case of ongoing problems with the RLV-relay, I'll open a separate bug-report for this.

Note ID# 851:

User:	Lulu	Submitted:	14/04/2016
	So... is the latest beta working properly now?

Note ID# 852:

User:	Miriam Himanez	Submitted:	14/04/2016
	No, it isn't. On first attach there isn't any error announced anymore and the relay is more stable than the ones before but it's failure-rate looks still way too high to me. (I guess about 30-40%.) Sorry for not posting this earlier but aboriginally I wanted to try to find a possibility to reproduce the malfunctions more regularly, before submitting the related bug-report. (Please view issue #203.)

Note ID# 860:

User:	Lulu	Submitted:	20/04/2016
	Updated status to Completed from In Progress.

Note ID# 861:

User:	Lulu	Submitted:	20/04/2016
	Thanks Miriam, I'll mark this as done as far as the initialization error is concerned. Will be deployed together with the major 7.3 update.