Taff Nouvelle Posted March 18, 2017 Posted March 18, 2017 Has anyone heard any news on when, or even if, LL are going to add functions to control projector lighting ??
Rolig Loon Posted March 18, 2017 Posted March 18, 2017 SCR-163 was submitted back in 2011and is still unassigned. You might try adding any relevant comments (suggested feature improvements, ....) to that JIRA. Your question comes up often in my conversations with other LSL scripters, so I know it's on several people's wish lists.
Taff Nouvelle Posted March 19, 2017 Author Posted March 19, 2017 (edited) 6 years and still no functions, I guess that LL has more important things to do such as making money. This really kills creativity in theatre shows. Edited March 19, 2017 by Taff Nouvelle
Innula Zenovka Posted March 20, 2017 Posted March 20, 2017 As I understand it, at least part of the reason we can't script projector lighting is that there are concerns about how easily ill-intentioned people would be able to use it to trash region performance and crash viewers. 1
Rolig Loon Posted March 20, 2017 Posted March 20, 2017 1 minute ago, Innula Zenovka said: As I understand it, at least part of the reason we can't script projector lighting is that there are concerns about how easily ill-intentioned people would be able to use it to trash region performance and crash viewers. Strife made a comment to that effect in the JIRA, in fact. He may well be right. One common way around that issue is to build a cap into the function, or a delay. I imagine that LL couldn't do that selectively for one parameter in SLPPF, unfortunately. 1
Taff Nouvelle Posted March 20, 2017 Author Posted March 20, 2017 (edited) I really dont see what anyone could do to crash a viewer by adjusting the FOV, and that is the biggest need, most of the functionallity is already there in PRIM_POINT_LIGHT. Just add the FOV to what is already there, it will not break anythinmg since it is only effective when projector light is enabled. Edited March 20, 2017 by Taff Nouvelle
Rolig Loon Posted March 20, 2017 Posted March 20, 2017 8 hours ago, Taff Nouvelle said: I really dont see what anyone could do to crash a viewer by adjusting the FOV, and that is the biggest need, most of the functionallity is already there in PRIM_POINT_LIGHT. Just add the FOV to what is already there, it will not break anythinmg since it is only effective when projector light is enabled. That's not likely to be the concern, Taff. As Strife said in the JIRA, " This has likely languished this long because of the abuse potential of turning on an off this feature rapidly. Lights have traditionally been expensive, I imagine that blinking them on and off rapidly would be something that LL does not want to QA. " One of the most persistent complaints people have had in SL is about lag, so LL has tried to do whatever they can to avoid adding features that will increase it. It's possible that advances in server software and in user hardware will gradually make this less of a concern, but I wouldn't hold my breath.
Taff Nouvelle Posted March 21, 2017 Author Posted March 21, 2017 The ability to flash lights rapidly is already there, llSetLinkPrimitiveParamsFast(PRIM_POINT_LIGHT) does that, the only thing I am asking for is the ability to alter the FOV of what is already available. I think that the only reason it has not been implemented is lack of interest since more exciting things take over. 1
Remi Alpha Posted April 11, 2020 Posted April 11, 2020 3 years hence... is it still the case that you cannot dynamically set / change the *projector* texture UUID in a script? I can think of some workarounds but I just wanted to check.
Rolig Loon Posted April 11, 2020 Posted April 11, 2020 44 minutes ago, lostware said: is it still the case that you cannot dynamically set / change the *projector* texture UUID in a script? Right. Nothing has changed. My guess is that it's not going to happen. Taff may have said it best in that last comment back in 2017. 1 1
Kyrah Abattoir Posted April 11, 2020 Posted April 11, 2020 On 3/20/2017 at 1:55 AM, Innula Zenovka said: As I understand it, at least part of the reason we can't script projector lighting is that there are concerns about how easily ill-intentioned people would be able to use it to trash region performance and crash viewers. I'd be tempted to go with you on that one. I'm still hoping we will be able to restrict attached lights as a parcel permission someday. 1
Tathiane Follet Posted April 25, 2021 Posted April 25, 2021 On 3/20/2017 at 8:47 PM, Rolig Loon said: That's not likely to be the concern, Taff. As Strife said in the JIRA, " This has likely languished this long because of the abuse potential of turning on an off this feature rapidly. Lights have traditionally been expensive, I imagine that blinking them on and off rapidly would be something that LL does not want to QA. " One of the most persistent complaints people have had in SL is about lag, so LL has tried to do whatever they can to avoid adding features that will increase it. It's possible that advances in server software and in user hardware will gradually make this less of a concern, but I wouldn't hold my breath. I think they just don't want to do it. Since 2011 mesh created many laggy problems. Projector lighting control through script would not create that of a big issue... Only excuses. 😪 1
Recommended Posts
Please take a moment to consider if this thread is worth bumping.
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now