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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
superpig
Nov 23, 2013 01:54
Note that the error described for modifying components directly doesn't occur in UnityScript.