[Bug] CreateColshapePolygon not working as intended js runtime

[trhi2409]

Summary

CREATE_COLSHAPE_POLYGON is unusable from the JS runtime: passing the points as a plain array throws "arrays should be
vectors (wrong number of values)". It only works if the array is msgpack_pack'd first, which is undocumented.

Issue type

Both / Unsure

Repro rate

Always

Server build version

FXServer-early-access b98 win32

OS

No response

CPU

No response

GPU

No response

RAM

No response

Storage type

None

Connection type

None

ISP and bandwidth

No response

DxDiag

No response

Network graph

No response

Platform

None

OS version / distribution

No response

CPU

No response

RAM

No response

Using txAdmin?

None

Hosting provider

None

Machine type

None

/perf endpoint output

No response

DDoS protection

No response

ulimit -n value (Linux only)

No response

Docker Compose file (Docker only)

No response

Steps to Reproduce

1. Create a js/ts resource
2. Call the native with the points as a plain array (like in examples of docs) in either server/client
3. Creation of the colshape fails with error: "Error: Script error in Native CreateColshapePolygon: arrays should be vectors (wrong number of values)"

const colShape = CreateColshapePolygon(28.0, 32.0, [293.089, 180.466, 303.089, 180.466, 298.089, 190.466]); //Error
console.log(`created colshape with id ${colShape}`); //Wont run

Expected Behavior

The native accepts the array from JS and returns a valid colshape handle

Actual Behavior

Error: Script error in Native CreateColshapePolygon: arrays should be vectors (wrong number of values)

Evidence

No response

Additional Context

Running msgpack_pack on the array before passing it into the native and providing the length seems to fix the issue and create the colshape as intended, for example:

const packed = msgpack_pack([293.089, 180.466, 303.089, 180.466, 298.089, 190.466])
const colShape = CreateColshapePolygon(28.0, 32.0, packed, packed.length);
console.log(`created colshape with id ${colShape}`); //works

[wolfram-cfx]

Thanks, we are looking into this.

[dBozee]

May be related to the same issues as the .NET10 runtime. The C# runtime expects a byte[] instead of something like Vector2[] or float[][].

[Gogsi]

A fix for this bug has been implemented and is available in August 11 Patch. Please try again and let us know if the issue persists. Thanks for your help!