Search Issue Tracker

By Design

Votes

0

Found in

2021.3.32f1

2022.3.14f1

2023.1.20f1

2023.2.1f1

2023.3.0a15

Issue ID

UUM-56549

Regression

No

Some meshes can still provide their vertex data despite isReadable was set to false at build time

--

-

How to reproduce:
1. Open the “UVCoordProject“ project
2. Open the “SampleUV“ scene
3. Select the “CP_Infiled“ mesh assets from the “Assets/Sample“ folder and open it in the Inspector
4. Toggle the Read/Write property off
5. Repeat steps 3 and 4 for the rest of the mesh assets (“DeformedPlane“, “DoubleUV“, “SingleUV“, “TripleUV“)
6. Go to the "File > Build Settings..."
7. Toggle on Development Build and press the "Build & Run" button
8. Once the project builds, exit the Player, then open the "Player.log" file
9. Observe the “Player.log“

Expected result: No “SampleCoord. Hit:“ are logged in the “Player.log” by the RaycastHit
Actual result: “SampleCoord. Hit:“ are logged in the “Player.log” by the RaycastHit

Reproducible with: 2021.3.32f1, 2022.3.14f1, 2023.1.20f1, 2023.2.1f1, 2023.3.0a15

Reproducible on: macOS 13.5.2 (Intel), Windows 10 Pro
Not reproducible on: No other environment tested

Notes:
- Not reproducible in Editor
- “Player.log” locations are:
Windows - %USERPROFILE%\AppData\LocalLow\CompanyName\ProductName\Player.log
macOS - ~/Library/Logs/Company Name/Product Name/Player.log
Linux - ~/.config/unity3d/CompanyName/ProductName/Player.log
documentation page for log files - [https://docs.unity3d.com/Manual/LogFiles.html|https://docs.unity3d.com/Manual/LogFiles.html]

  1. Resolution Note:

    The behaviour in this case is by design, as all meshes in the project save CP_Infiled get dynamically batched and retain their cpu copies, which enables RaycastHit's to retrieve uv data.

    Built-in meshes such as Cube/Plane/Sphere/Capsule always retain their CPU copies.

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.