Age | Commit message (Collapse) | Author |
|
Viewer added a new callback when the avatar returned without resetting the
timer for last reference to the saved raw image. This created a time window
in which new callbacks could get cleared out due to the raw image getting destroyed.
Since the callback was removed, pants flare was not properly applied. Appears
to be working now.
|
|
|
|
probably not related to SSA rollout, but we were not triggering the
callbacks for baked texture loads, since the avatar object was adding
paused callbacks to the callback list without properly setting the
flag to indicate paused callbacks.
|
|
|
|
unused joint resetting code
|
|
|
|
Wrinkles have been a deprecated/non-functional feature for a few years now.
Removing the user-facing sliders to prevent confusion.
|
|
requests, removed many redundant calls
|
|
removing minimum height enforcement, as changes are local-only and would not
be visible by other users in this repro, unless the user explicitly saved
the changes. Since there are many ways to get around the enforcement, and the
enforced minimums won't be visible to other users, its simpler to allow
users to use the full range of the hover slider.
NOTE: this means that a user's avatar can be underground, leading to the
camera pointing up at the sky. this is a known issue.
|
|
Adjusted the startup conditions, and relogging should apply the enforcement
as appropriate now. Note that this affects the startup enforcement and should
re-test the macro avatar loading bug.
|
|
|
|
|
|
|
|
calculator instead of binormal calculator, convert binormal centric code to tangent centric)
|
|
|
|
Hover minimum enforcement was getting triggered on relog for macro avatars before
the joint offsets were applied when loading the avatar.
Added code to verify that all attachments in COF have been rezzed, and all
attached objects are not in the process of being rebuilt to the enforcement code.
This should verify that we only apply the hover value enforcement when all rigged meshes
are actually loaded before enforcing minimum hover value
|
|
increment folder version when a contained item is updated.
|
|
|
|
Preventing hover limit from being applied during startup or shutdown
when the rigged mesh may not be fully loaded.
|
|
Inverted logic meant that we would enforce minimums only while
in preview renders, not for actual user adjustments. This seems to fix it.
|
|
|
|
avatar hover was being temporarily set to -2.0 for the preview render, which
was triggering the minimum enforcement, even when the user's requested value
is no where near the minimum. Added a flag to disable the minimum enforcement
if we are temporarily changing the value.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Changing viewer limit for avatar height to match server limit, camera does not go underground.
Also clarified where we do not need avatar offset in the code, through comments
|
|
with nV mobile graphics cards
|
|
driver on mac 9400/9600 GT only
|
|
llviewerregion deletion. Avoid trying to send metrics when we're shutting down and it's too late anyway. Reviewed by Nyx
|
|
|
|
|
|
|
|
FTT_SERVER_BAKE images. This is needed because 'missing' is not necessarily permanent for such images.
|
|
|
|
|
|
|
|
Added a constraint to ensure that the avatar's height (with offset)
does not go below 0.1 meters. Camera was getting confused since the avatar's
effective height was negative.
Note the avatar is mostly underground/contorted even at 0.1 meters, but
most users setting values this low will be making ultra-tinies and would
be hiding the avatar mesh. Camera stays above ground when height is at 0.1.
|
|
|
|
|
|
|
|
Added the height offset in one too many places. fixing.
|
|
|
|
We were getting the texture ID from the type,index couple, but were not
passing in index, which defaulted to 0. texture ID is available from the
texture object itself, so using that and removing the index parameter
to prevent future confusion.
|
|
|
|
non-self avs
|
|
Using a boolean for existence and straight logic, no intermediate string
|
|
|