Update, November 24th: This issue now has a fix, please refer to my update article.
Note: this issue was discussed at the TPV Developer meeting on Friday, November 18th, together with wider issues around llTakeControl. You can follow he full conversation via the meeting video, between the 10:16 and 36:22 marks. In this report, I have attempted to focus solely on the Horizons Experience issue.
The TL;DR short form of what follows is that if you playing the Horizons Experience using a TPV, you may find the gun required for Quest 3 in the game – the forest shoot-out with robots – doesn’t work (Firestorm and Alchemy have the issue, for example). If so, you’ll need to switch to the official viewer to complete that Quest. When you have done so, you can then switch back to using your preferred viewer.
For those interested in the background, as in as small a nutshell as possible: the function llTakeControls has a long history of not behaving well. One of the issues was that it prevented interaction (left-click touch) with objects when in Mouselook, prompting SVC-7532 to be raised.
A fix for this problem was implemented in February 2016. However, while it fixed the left-click touch issue, it broke many weapons systems (see BUG-37693) as well as causing other problems (see BUG-11602). As TPVs tend to be a used a lot by people involved in SL combat environments, some – such as Firestorm and Alchemy – didn’t implement SVC-7532.
The Horizons Experience gun used in Quest 3, however, is designed to work with the SVC-7532 behaviour change, and so may not work for everyone using a viewer which does not have SVC-7532 implemented. Note the “may not” there. If you happen to be on a TPV viewer without SVC-7532, but are wearing an attachment already using llTakeControls when you enter the Horizons Experience, then the gun might work for you (this has been my own experience).
The problem now is what to do. Rolling back the behaviour change implemented in SVC-7532 is not seen as ideal, as it breaks expected functionality elsewhere. Similarly, any “blanket” implementation of SVC-7532 is going to completely break a lot of weapons systems, which the Lab would rather avoid. There’s also the fact that this is one issue among a number caused by llTakeControl (see BUG-8265 for other issues with it), so the Lab is going to have to spend time in further investigations to determine how they’ll handle things going forward.
At the moment, two possible short-term solutions for the “Horizons gun problem” were suggested at the TPV Developer meeting on Friday November 18th (video):
- Re-scripting the Horizons gun / shooting system
- Implementing some kind of toggle via the Advanced or Develop(er) menu so that users can switch between the two llTakeControl behaviours depending on the weapon system they are using.
At present, the Lab might be leaning towards the second option. However, and as noted, no decision has been made as yet.
In the meantime, if you encounter the “Horizons gun problem” when using a TPV, you’ll need to switch to the official viewer to complete Quest 3.
With thanks to Whirly Fizzle.