Search Issue Tracker

By Design

Votes

0

Found in

2021.3.33f1

2022.3.15f1

2023.2.4f1

2023.3.0a19

Issue ID

UUM-59302

Regression

No

A Column "Max Texture Size" in Search Window shows an incorrect value when a 2D Textures "Max Size" value is changed

--

-

How to reproduce:

# Open the “SearchFilterBug.zip“ project
# Open the “SampleScene”
# Open a Search Bar (Window > Search > New Window)
# In the Search window add a column “Max Texture Size“
# Type in “URP.png“ into the search bar in Search window
# Click on “URP.png”
# Press on the highlighted “URP” asset in the Project window
# Change the Max Size of the “URP” asset in the Inspector window
# Observe the “Max Texture Size“ column in the Search Window

Expected results: The “Max Texture Size“ column value for the “URP.png“ texture changes according to the “Max Size“ of that texture in the Inspector window
Actual results: The “Max Texture Size“ column value for the “URP.png“ texture does not change according to the “Max Size“ of that texture in the Inspector window

Reproducible in: 2021.3.33f1, 2022.3.15f1, 2023.2.4f1, 2023.3.0a19

Reproduced on: Windows 11 Pro
Not reproduced on: No other environment tested

  1. Resolution Note:

    This is a tricky issue to explain:
    - the search window dynamically generates columns from available SerializeProperty in an object. But we do not "dig" into subobjects or array.
    - The property MaxTureSize maps to a property with path "m_MaxTextureSize" (See image)
    - In order to access m_MaxTextureSize property of the default platform settings you need to use the m_PlatformSettings.Array.data[0].m_MaxTextureSize property path (see image)
    - Using this proper path will update correctly (see gifs)

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.