| Age | Commit message (Collapse) | Author |
|---|
|
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.
|
|
|
|
|
|
|
|
|
|
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
|
|
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
|
|
|
|
disappear in CHUI builds.
Added check in LLVOAvatar::idleUpdateNameTagText() to account for case where mNameString is literally "" (two quotes)
|
|
|
|
|
|
|
|
|
|
We were using an indicator of whether there *was* a baked texture to whether we
were *using* a baked texture. Switched to one of the (several) proper indicators
of whether a baked texture was in use. This should allow local texture data to
get marked for download when we enter appearance mode.
Local testing confirms that old apperances linger for a second or two, but are
soon replaced by the correct local renders.
|
|
host bake, map tile, etc - down the chain so LLTextureFetchWorker can adjust behavior as needed
|
|
time when nametag is changes
|
|
|
|
|
|
|
|
|
|
Adding a new visual param that allows users to manually adjust an offset for
how far off the ground (+ or -) their avatar's root bone is.
Supports the +-2m range people are used to adjusting in their viewers, but
new implementation should support server-generated appearances.
|
|
|
