6.5 Beta Sweepstakes - Your chance to win a GPU!

[UnityJuju]

The submission period for the sweepstakes has ended and we will pick the winners as soon as all submissions have been evaluated.

Hiii folks,

We’re happy to announce our Beta Sweepstakes with the Unity 6000.5 release.
Unity 6.5 Beta delivers major upgrades across scripting performance and APIs, streamlined SRP/URP rendering, embedded DOTS (Entities) with new workflows, a faster, more reliable asset/import pipeline, and powerful UI Toolkit authoring and performance improvements. This Beta Sweepstakes is your chance to help us validate and fine‑tune these improvements!

We’ve updated our prize pool, and you have a chance to win one of the graphics cards below!

• First winner - NVIDIA GeForce RTX 5070 Ti
• Second winner - AMD Radeon RX 9070 XT
• Third winner - ASUS Dual GeForce RTX 4070 Super

Identifying and reporting at least one original bug during the 6.5 beta cycle while the submission period is open gives you an entry to the Sweepstakes. Make sure to add #BetaSweepstakes_6_5 to the Description section of your bug reports to make it clear that you’d like to enter the sweepstakes. Every additional valid submission increases your odds of winning, but no participant can win more than one prize.

The contest is open from Thursday, March 26, 2026, at 6:00 am PST, and the submission period ends Monday, June 1st, 2026, at 11:59 pm PST.

What’s an original bug?
An original bug is a bug that has not yet been reported at the time of submission and has been reproduced and acknowledged by Unity as a bug.

Reported a bug but didn’t add the tag? No worries! If you entered a valid submission while the submission period was open, you can still do that retroactively until the end of the submission period by replying with the tag to the confirmation email you received after submitting the report.

No purchase is necessary. Void where prohibited.
See the full rules here.

We will contact the winners directly.

Happy hunting!

[DevDunk]

That’s a solid upgrade over the last one :o
I’ll be upgrading my VR projects to 6.4 soon for on tile rendering, so I might have some reports there

[mgear]

nooo, there are no more bugs left (after spending days in the 6.4 bug hunt : ) !!

[koirat]

@UnityJuju

Identifying and reporting at least one original bug during the 6.5 beta cycle

This is bugging me — do bugs in packages count?

[bugfinders]

Well it seems your bug report crew are in fine form…

I logged

"While these are errors from a 3rd party asset who probably dont support 6.5 yet.. however

use GeyEntidyId as suggested instead of GetInstanceID (which I then changed as per error message) and you get errors such as

error CS0619: ‘EntityId.implicit operator int(EntityId)’ is obsolete: ‘EntityId will not be representable by an int in the future. This casting operator will be removed in a future version.’"

As it should not be an ERROR it should be a warning.

and Deividas Matonis decided that fixing 3rd party code is not their problem.. As always, way to miss the point ticket answering team.

[DaxodeUnity]

Hey, in 6.4 we made it a warning to both cast to and from int, and to use GetInstanceId, in 6.5 it’s now an error. You should not be using either of the two. Instead use the EntityId type, and store it. It is a valid key in your dictionaries, it’s valid as a parameter in all the functions that previously took an InstanceID (int), and it should be updated by every Unity Package.

The reason for the change is that EntityId is now 8bytes (which for obvious reasons we can’t store in an int)

In case there’s any problem with the upgrade do let me know! I’m currently working on a Discussion thread with help and examples to everyone using instanceid that wants the help on how to upgrade to using EntityId

[bugfinders]

Thanks, but there was an error saying dont use GetInstantID, use getentityID, and then having changed it to that, this error appeared but if it is not an int yet, it should be a warning - oddly i dont remember any of these warnings in the 6.5 alpha

[DaxodeUnity]

Apologies, what do you mean by “then having changed it to that, this error appeared but if it is not an int yet, it should be a warning”??

[bugfinders]

initially all code using GetInstantID errored saying use GetentityID.. so I changed them all.. and then it moans that “This casting operator will be removed in a future version.’” but if its not removed yet, it should still be a warning.

[runner78]

Maybe there’s some confusion because in 6.5 the warning was turned into an error, but the old warning message was kept?

[DaxodeUnity]

@bugfinders

but if its not removed yet, it should still be a warning.

i see, that’s the part that’s missing, in fact deprecation works in two stages. one you put [Obsolete("some message", false)] this will put it in warning mode, and people should start to migrate away from it (we did this in 6.4). In 6.5 we changed it to [Obsolete("some message", true)] meaning you now get an error for using it.

The reason we don’t fully remove it, is to give people an authored message from us, instead of the compiler just telling you “that symbol doesn’t exit”.

[soleron]

Faced the same with at least a couple of popular assets as I was testing URP transition of a project in 6.5. Asset creators typically do not test on Beta versions because any action they take based on Beta testing may be a waste of their time.

I understand this is not a Unity issue. But I agree. These should not be breaking points. Just informative warnings. Instead the warnings became blockers. And that is a Unity issue.

[spiney199]

The change was announced well ahead of time: Planned breaking changes in Unity 6.5 [updated 2026-03-27]

InstanceID as a concept is fully obsolete in 6.5. It has to be an error because the old API doesn’t work anymore. It used to be an int but now it’s a long, so any code still treating it as an int needs to be updated as it won’t work correctly.

[bugfinders]

its odd because i have the same project ive moved from around 2015 through to now, and I dont recall the warnings before.. and its been through each version along the way. Perhaps because later a lot of things are “packages” not just asset drops and those all but get compiled on moving over and then never seen again… So only now is it an issue because now it wont compile.

Part of my bug was also the fact it says instead of instanceID use entityID, and then errors on that too

[spiney199]

@bugfinders

Part of my bug was also the fact it says instead of instanceID use entityID, and then errors on that too

Probably because something is trying to implicitly cast the EntityID into an int, which you can’t/shouldn’t do any more because it’s now a long under the hood.

6.4 was when they were warnings. 6.5 is now when they’re errors because they no longer work at all.

[bugfinders]

While I appreciate that alphas are raw and dirty and may eat your children for all you know.. 6.3 didnt say a thing, that I remember, if in 6.4 it was a warning (which I dont remember, but then it likely never recompiled so.. i guess an easy miss) but is gone for 6.5, that is a quick turn around, as 6.4 wasnt out when the bug became apparent to me. But as soleron said, many asset providers dont bother fixing their things until its out. So you get windows like this where in essence its gone from OK to error in 2 minor versions..

[spiney199]

I mean Unity has broadcasted this changes months ago. 5 months at this point: ECS Development Status - December 2025

6.4 has only just hit supported. 6.5 leaving Beta is still a while away. This is the point at which asset devs should be updating to the new API before 6.5 leaves Beta.

This is a locked and loaded breaking change that isn’t going to not happen. There’s already been plenty of time to make the change, and there still is plenty of time to do it.

If by the time 6.5 releases proper and an asset dev hasn’t made the change, I don’t think it’s Unity’s fault at that point.

[bugfinders]

OK so as an example Im looking at the package unitask

So, it initially says

So, I updated as it suggests all the treeview stuff to be .. only then each of those errors changes to

Library\PackageCache\com.cysharp.unitask@ad5ed25e82a3\Editor\UniTaskTrackerTreeView.cs(75,46): error CS0619: ‘InstanceID’ is obsolete: ‘Obsolete - Please use EntityId instead.’

putting my dumb hat on, surely it shouldnt tell me to use IsnstanceID when 6 edits later it tells me what it told me to use is obsolete?

[spiney199]

Okay but is the UniTask tracker using the identifier to store an InstanceID?

No it’s not.

So you shouldn’t be changing it to TreeViewItem<InstanceID> anyway.

That said the error is out of date and should be updated to say EntityID.

[soleron]

@spiney199

6.5 is now when they’re errors because they no longer work at all.

They should not start with the word “Warning” then And they should be ending with the phrase “they will be removed in a later version”

The information these messages provide is confusing, misleading, and plain wrong. And must change so people do not waste their time. I wasted half day trying to understand why a mere warning about something that is going to happen in the future, is blocking my progress and how to work around it.