A Unity ID allows you to buy and/or subscribe to Unity products and services, shop in the Asset Store and participate in the Unity community.
Separate names with a comma.
For Sony platform specific questions you'll have to ask over on their forums.
You got a bug number just so we can ensure we are looking at the right one!?
Ok I think we are gonna need a bug report for this to be able to fix it! Can you submit one please?
Any chance you could try the 1.8 preview package '1.8.0-pre.2' and see if that fixes the problem?
Anyway we can get a repro for this? We haven't seen anything like this locally, so a repro would be really helpful.
That looks like a job system thing or something like that, way outside my wheelhouse (they only let me out to talk to users about Burst :D ). I'll...
It's the HashCode.Combine - it uses some managed static's within the implementation, which Burst cannot handle. We need to improve that error...
That's totally fine, we're here to try and point you at the right places to help!
This doesn't seem like a Burst issue - were you meaning to post this on the main scripting forum? https://forum.unity.com/forums/scripting.12/
With later Unity editors there are new package manager rules that we have to follow such that newer packages only appear in newer editor versions....
One difference between both is the int index in the NativeArray case, and the ulong in the pointer case. With the int, you see that before it...
Have you got some perf data running each one to show please? Just curious before I dive in what the delta is.
I've not seen this issue since I added the workarounds above. If you can submit a bug with a repro we can always take a look.
@dan_ginovker I think I managed to move it to scripting, but please shout if I did anything wrong since I've never actually done that before :D
This doesn't look Burst specific? I guess you want the main scripting forum instead? https://forum.unity.com/forums/scripting.12/
I can repro - guess who introduced an off by one bug in the slice-with-length safety check :D The bug is that your start + length == the original...
Oh and does HexagonsInRange return an int?
The case hasn't made it to the Burst team yet for some reason, I'm going to chase up why its not made it to us as we shouldn't have had to wait...
Please submit a bug with a repro for this and we'll look into it.
Can you give me the Length of hexagons as you enter that function, and the start and length you are using when taking a slice within the function...