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

Networking

-

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

  1. 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.

Comments (2)

  1. Xypherorion

    Nov 23, 2018 15:02

    Easy workaround using an int array, but why is this native Unity type not supported?

  2. AubryStrawberry

    Jun 10, 2018 11:01

    Same with 2018.1.2f1

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.