Search Issue Tracker
Fixed
Votes
0
Found in
1.5.1b1
Issue ID
298399
Regression
No
Error is not generated if you use the index of the component instead of the letters.
iphone: There are some Vector3 properties that can not be modified by component. For instance, you can't set bounds.min.x, bounds.max.y, or transform.position.z. Trying to do this generates a helpful error, as it should. However, the same error is not generated if you use the index of the component instead of the letters. For example, setting bounds.min[0], bounds.max[y], or transform.position[2] will not do anything, but it also won't generate an error. Please make the error appear for the latter case as well.
This is a problem with both Unity and Unity iPhone.
Comments (4)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
superpig
Nov 23, 2013 01:54
Note that the error described for modifying components directly doesn't occur in UnityScript.