Linden Lab® just announced that Havok™ 4 simulator code has been updated and that it has been released to both the Beta Preview and the currently more than 500 Main Grid simulators in the Early Adopter Program.
It would appear that they’ve fixed some security exploits, as well as the following bugs:
- SVC-1680: llGetMass() now returns correct values for child prims after rez without having to recompile the script
- SVC-1700: Non-physical child prims of physical root prims now behave correctly with llTargetOmega()
- SVC-1469: Items no longer deleted or returned from off-world above 768m after region restart
- SVC-1299: Sit targets adjusted to more closely match release simulator placement
- SVC-1488: Prim.Docker automatic prim alignment no longer leaves gaps
- DEV-10635: Personal Hugger (90 sec) and Lost Dog Hugz Sphere hug mis-alignment corrected
- DEV-10702: Push-based weapons are now functional (the previous deploy had code that would penalize attempts to push “overly hard” to the point that many weapons displayed zero push - whereas now they are simply capped to the max push allowed)
- SVC-1542: Many concurrent shape changes no longer causes physics to stop being applied to objects (a.k.a. “the bunny problem”
- SVC-1688: Simulator now recognizes changes to child prims without waiting for a change to the root object
- SVC-1261: Avatars standing on sloped terrain no longer slide down the slope slowly
- SVC-1066: Temp prims no longer count towards region prim limits
- DEV-10985: Discrepancy between visual and physical collision location resolved for fast-moving object
- DEV-11599: Removed new crash mode discovered in final QA process
I had previously written a rather nasty and overly hasty post stating that I didn’t think Linden Labs had any intention of fixing what I thought were extremely serious issues. Sidewinder Linden personally commented on that (now deleted) post and reminded me that development on the Havok™ 4 codebase has not stopped, and that there is still some work to be done.
Because of the security exploit, there is a sense of urgency getting this update out to everyone without going through the more usual beta period, and they have a contingency plan if it turns out that the rollout doesn’t work as expected
I apologize to Linden Lab® for the tone of the previous post, and I do hope that this rollout works as expected. (And please, please please do fix the issues we’ve been reporting before final release).
Popularity: 33% [?]
Yeah, now I really feel like an ass, because that previous post sent two pingbacks to the LL blog and I can’t delete them.
I should never write a post when I have low blood sugar, it just bites me in the ass.
I’m disappointed that my pet issue has not been resolved yet, but I still hold out hope that it will get fixed eventually.
Any word on the kick issue being fixed? I noticed something there about push with weapons but not sure if it actually fixed anything.
Atrus - This comment was left by SideWinder Linden on the SL Blog :
I was just in-world seeing if anything was different, and it would appear that this latest update did indeed change the behavior, though it’s still not correct. But that’s probably a good sign, since my guess is that the issue is multifaceted, and they are working on some of those facets now.
Well that good news. I was kind of confused we I saw the blog about the update and I asked Aya to restart edo and there didn’t seem to be much of a change.
I checked out the new code at Edo. The kick/push bug is still there.
yeah
I did create an extremely simple object that uses code very similar to (if not the same as) the C:SI kick code and made it so that you can just click it to test, and handed that off to Sidewinder Linden, so that he’s got a very simple and easy-to-use repro case for the dev team.
I tested it in both Havok1 as well as Havok4 sims, and it nicely demonstrates the issue without (in my opinion) any ambiguity, so that might help make up for my crappy explanation in the JIRA issue.
I know that Sidewinder has received the object, but I do not know at what point they will look into it. I did my part, now I guess we get to wait for them to do theirs