Search Issue Tracker
Won't Fix
Votes
2
Found in
2017.3.1f1
Issue ID
1015220
Regression
No
UNetWeaver error is thrown when using Vector3Int as a parameter for UNET Command methods
How to reproduce:
1. Open "Vector3intBug" Unity project
2. Have a script with Command method and have Vector3int as a parameter
3. Unity throws errors after compiling
Expected result: Vector3int should be a valid parameter
Actual result:
Reproducible with: 2018.2.0a5, 2018.1.0b12, 2017.4.0f1, 2017.3.2f1, 2017.2.2p1
Note:
Vector3int was released in 2017.2 version so it can be tested on older ones
Comments (2)
-
Xypherorion
Nov 23, 2018 15:02
Easy workaround using an int array, but why is this native Unity type not supported?
-
AubryStrawberry
Jun 10, 2018 11:01
Same with 2018.1.2f1
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
- Unnecessary modifications clutter the Scene when using a RectTransform driven by a LayoutGroup in a Prefab
- Files in the target folder are deleted without a proper warning when building an iOS project
- Character animation freezes when toggling animator on/off in a coroutine
- Certain textures are incorrectly marked in the render pass list when observed through Render Graph Viewer
- "Assertion failed on expression" error occurs when multiple Animation Components are instantiated after changing the Culling Type
Resolution Note:
Mass closure of UNET Bugs.
As UNet is Deprecated we are moving to low maintenance mode, where critical issues can get fixes.
Closing this bug as part of cleaning-up the Bug List.
If you feel this bug is really a road-blocker, you can reopen the bug and we will work this one.