• All submissions to this site are governed by Second Life Project Contribution Agreement. By submitting patches and other information using this site, you acknowledge that you have read, understood, and agreed to those terms.
Issue Details (XML | Word | Printable)

Key: SVC-1073
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: kelly linden
Reporter: Kayla Stonecutter
Votes: 20
Watchers: 7
Operations

If you were logged in you would be able to see more operations.
2. Second Life Service - SVC

llGetStartParameter() always returns zero [Beta v1.18.3 (70780)]

Created: 15/Dec/07 12:26 PM   Updated: 29/Apr/08 01:03 PM
Return to search
Issue 3910 of 4962 issue(s)
<< Previous | SVC-1073 | Next >>
Component/s: Scripts
Affects Version/s: Havok4 Beta
Fix Version/s: Havok4 Beta

Environment: WinXP Pro, latest Havok4 build v1.18.3 (70780)
Issue Links:
Duplicate
 
Relates
 

Linden Lab Issue ID: DEV-9684
Linden Lab Internal Branch: hvok4-3


 Description  « Hide
Using llGetStartParameter() to retrieve the integer passed from a rezzing object always returns zero, while the integer param in the on_rez() event handler returns the proper number.

IN REZZING OBJECT:
default
{
touch_start(integer total_number)

{ llRezObject("test rez", llGetPos() + <0,0,1>, <0,0,0>, <0,0,0,1>, 123123); }

}

IN REZZED OBJECT:
default
{
on_rez(integer param)

{ llOwnerSay((string)param + " - " + (string)llGetStartParameter()); }

}

Results: Rezzed object says "123123 - 0" when rezzed by the first object. Should say "123123 - 123123".
llGetStartParameter() always returns 0, even in other event handlers.



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
WarKirby Magojiro added a comment - 15/Dec/07 01:12 PM
annoying.

Haravikk Mistral added a comment - 21/Dec/07 09:07 AM
I've always tended to assign start parameters somewhere myself anyway, but yes this is definitely wrong.

anthony reisman added a comment - 21/Dec/07 12:52 PM
What if the script is loaded with llRemoteLoadScriptPin()? does the start parameter come back there? I noticed that the on_rez isn't triggered for that but llRemoteLoadScriptPin does have a start_param so I wonder where that gets loaded?

Kayla Stonecutter added a comment - 12/Jan/08 02:22 AM
Just tested with the Beta Grid Refresh done on Jan 11, 2008 (Simulator v1.18.6.77074). The bug is still present and causes llGetStartParameter() to always return zero.

Jag Nishi added a comment - 27/Jan/08 05:29 PM
Tested it in the Stonehaven sim on the main grid (Havok4 Beta Server 1.18.6.78103) and still the same ordeal. Pretty annoying since we use the start parameters for weapons in the sim.

CrystalShard Foo added a comment - 28/Jan/08 04:13 AM
Many of my scripts - including the Rez-Foo - use llGetStartParameter in various points in the script. I'd say this issue is rather critical because this function is pretty wide spread in many scripts out there.

Now that Havoc 4 is being tested on the main grid the problem shows far more often then before.


kelly linden added a comment - 29/Jan/08 10:54 AM
Apparently some changes to the order of operations for rezing objects caused us to essentially lose the setting of the start parameter. Oops.

This will be fixed with the next havok4 deploy.

One thing to note is that this value is set when the object is rezed, there is no way to "fix" objects that are already in world. If you rez an object this way in the current havok4 it will have a start parameter of 0, even after the next update. However if the same object does the same rez after the next update it will work as expected. Given the general uses of this I don't think this is a huge deal, but wanted to let people know.


Adam Ramona added a comment - 29/Jan/08 05:18 PM
This is a very big deal for us on ACVA, the functionality of BabelSwarm relies on the start parameter working. What's the ETA on the next update?

chalky white added a comment - 04/Feb/08 04:49 PM
Sadly, not fixed in todays mono beta server refresh (according to my testing). Will it need the next client ?

This has totally broken a family of my objects.
I am assuming it's the same bug, but for me it manifests as the script in the rezzed object being found not running after the rezz.

I am hoping for a fix soon, or should I start the task of reprogramming to communicate another way, without using the startparameter ?


kelly linden added a comment - 04/Feb/08 05:09 PM
It is very important to note that this was a havok4 bug, not a mono bug. Havok4 and mono are sharing a grid, but not the same code. Mono beta updates will not effect the havok4 beta updates and visa versa. This fix for havok4 will be in the next havok4 update. If you found this bug in mono, please file a new jira with the appropriate Affects Version(s).

Adam Ramona added a comment - 04/Feb/08 05:41 PM
Is there an estimate on when the next Havok4 update will be?

darling brody added a comment - 13/Apr/08 11:52 AM

I have done some further testing on this bug and found that the llGetStartParameter is still loosing it's value when the script is reset.

I am sure the value was not lost when a script reset under havok1. ...and if it did, it shouldnt!

A lot of legacy items issue a reset in the on_rez event to get around memory leaks and other old bugs like llGetOwner not updating the owner.

Darling.


Kayla Stonecutter added a comment - 13/Apr/08 02:54 PM
This bug was fixed months ago and is working fine. llGetStartParameter should be cleared on script reset, it's most likely stored in script memory like any other variable. Everything in script memory is cleared on reset. If anything is left then it's a bug, since the whole point of a script reset is to clear everything out and start fresh.

From the LSL Wiki on llGetStartParameter: "If the script is reset (using llResetScript or other means), this value is set to 0".