Improve radius jewel tooltip performance - #9863
Open
mcagnion wants to merge 8 commits into
Open
Conversation
mcagnion
force-pushed
the
bugfix/radius-jewel-tooltip-performance
branch
2 times, most recently
from
August 6, 2026 09:14
7ebd706 to
b5f7a20
Compare
mcagnion
marked this pull request as ready for review
August 6, 2026 14:38
mcagnion
force-pushed
the
bugfix/radius-jewel-tooltip-performance
branch
from
August 17, 2026 17:39
b5f7a20 to
c52198c
Compare
Avoid rebuilding radius-jewel comparison specs for repeated targeted tooltip hovers and skip limited-unique socket outputs that will not be shown. Preserve full multi-slot tooltip behavior when slot-only tooltips are disabled. Related local follow-up to PR 9746.
Tooltip comparison specs only need calc state, but radius jewel comparisons were still rebuilding passive tree UI paths for every temporary spec. Skip that path rebuild while preserving socket distance recomputation for Split Personality-style jewel scaling.
Reuse full radius jewel comparison outputs while the build output revision is unchanged. This reduces repeated Compare-tab hover work for slotOnlyTooltips=OFF without caching cloned specs or changing comparison behavior.
Keep the rebased regression tests compatible with the current class constructor API.
Include Shift in the tooltip update key and clear cached update parameters before drawing the Equip comparison tooltip.
mcagnion
force-pushed
the
bugfix/radius-jewel-tooltip-performance
branch
from
August 21, 2026 21:22
c52198c to
a50712a
Compare
Compare the first-pass tooltip text with the warm-cache result so the output-cache test covers semantic equivalence as well as reduced calculator calls.
Use the established slot-only vocabulary and document the cache-key sentinels and selective passive-path rebuild contract found during cumulative naming review.
Use the existing output cache for slot-only and multi-slot hovers instead of retaining temporary passive specs. Keep calculation-only specs free of UI path data while preserving socket distances. This reduces duplicate state and repeated calculations without changing tooltip content.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of the problem being solved:
Radius jewel stat comparison fixes from PR 9746 made Compare tab hovers expensive, especially when moving quickly between jewels. Full multi-slot tooltips could rebuild temporary passive specs and recalculate comparison outputs for every compatible jewel socket.
This PR keeps the existing tooltip behavior while reducing repeated work:
outputRevisionchanges.Measured locally, the output cache does not improve first-pass hovers over never-seen jewels, but it strongly improves repeated and bouncing hovers:
Cached outputs are scoped to one
outputRevisionepoch and discarded after build output changes. Temporary unstored items remain uncached.Steps taken to verify a working solution:
Link to a build that showcases this PR:
N/A. The change is performance-focused and was verified with local Compare tab testing plus the benchmark matrix.
Before screenshot:
N/A. No visual UI change.
After screenshot:
N/A. No visual UI change.