The submission period for the sweepstakes has ended and we will pick the winners as soon as all submissions have been evaluated.
Hi Everybody,
With the initial release of Unity 6.4.0b1 on December 11, we are also reviving and kicking off our accompanying beta sweepstakes, which give you the chance to win one of three NVIDIA GeForce RTX graphics cards.
First winner - ASUS Dual GeForce RTX 5070
Second winner - ASUS Dual GeForce RTX 4070 Super
Third winner - ASUS Dual GeForce RTX 5060 Ti
To enter the draw, all you have to do is identify and report at least one original bug during the 6.4 beta cycle while the submission period is open. The contest is open from Thursday, December 11, 2025, at 6:00 am PST, and the submission period ends Monday, February 23, 2026, at 11:59 pm PST.
An original bug is one that has not yet been reported at the time of submission and has been reproduced and acknowledged by Unity as a bug. Make sure to add #BetaSweepstakes_6_4 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.
If you entered a valid submission while the submission period was open but didnât initially tag it with #BetaSweepstakes_6_4, 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.
Make release version like Unity 6000.3.0f1 as RC instead of release for a month
And launch Sweepstakes for it. This way you will have plenty of community bug without complains and when you call it release community will be way more happy with stability
Are Swedish people finally allowed to participate? As far as I know, Sweden has not been allowed for several years due to some dumb law regarding giveaways.
Hi @Hertzole, thanks for reaching out. I checked in with legal and residents of Sweden are still prohibited from participating. Weâre working on getting the rules amended to make that clear.
Hi @koirat,
Thatâs what the Issue Tracker is for. That being said, do feel free to also post here for visibility and discussion. From the beta testing guidelines:
What matters is that itâs and unknown bug which affects Unity 6.4, is reported through the 6.4 bug reporter, includes #BetaSweepstakes_6_4 in the description of the report, and is recognized as a bug by QA.
If it turns out to also affect older versions, thatâs ok.
What is classified as a bug? Few weeks ago I merely reported that the default URP demo scene doesnât have a namespace in the tutorial script. Fairly obvious, trivial to solve. Should be done either way. Thatâs a no-brainer.
Itâs really not big. Create a new URP project and check this:
using System;
using UnityEngine;
public class Readme : ScriptableObject
{
public Texture2D icon;
public string title;
public Section[] sections;
public bool loadedLayout;
[Serializable]
public class Section
{
public string heading, text, linkText, url;
}
}
You know what happened? The bug report got rejected as âby designâ. Hereâs a quote:
This is tutorial/example code in a template project thatâs meant to be simple and educational. The ReadmeEditor is just a helper script to display a welcome screen and can be deleted by users. While using namespaces is a best practice, the absence of one here doesnât break any functionality - itâs a stylistic/code quality preference. If you have any questions, concerns, or additional information about this issue, feel free to reach out.
If your QA and your coders donât understand the effect of having no namespaces, especially with thousands of assets on the Unity Asset Store, then why report any bug at all? I actually stopped reporting bugs because itâs futile. No matter if itâs a severe one or not. I mean even the bug got rejected that Unity loads all 4K heightstamps in a system into memory for the terrain tools while Unity should only load the thumbnails for the heightmap picker, otherwise users will quickly get an out of memory exception.
Reporting bugs is futile. Unity doesnât acknowledge trivial bugs nor severe bugs.
I have no information who works at Unity, but if during a job interview someone tells me not having a namespace is intentionally âby designâ, coder job or QA job, Iâd just tell them âthank youâ and not waste my time any longer. Theyâd have no idea about the additional redundant time consumption their lack of knowledge has. Shall every publisher tell their customers after a 1-star review - because the code doesnât compile - to remove Unityâs own scripts?
I reported this today yet again with 6.4, I really donât care about the sweepstakes, just for a proper working engine. This is the reply as of just now:
It seems you have reported this issue multiple times, as your report IN-127659 Closed seems to describe the same issue. Iâll go ahead and close this ticket.
Thereâs no point of reporting anything at all if Unity ignores concepts of cause and implications. Itâs like itâs all syntax, no semantics.
I have one in about test cases. There are a couple of annoyances, so, for you to see the internals of the classes things need to be declared internal so that your test cases can set and test hings, second, if there is any compilation issue with the test cases then it doesnt tend to tell you just claim there are no test cases..
However, i have carefully setup my classes so only that which needs to be public/visible is, their advice was make everything internal all the time, so every class can change all the wrong things of other classes, i mean why not just say make em all public, its almost as half witted.. i dont want them ever to all be internal, but for the point of testing, i need to see some of the closed off variabless.
I also find it frustrating that they write to you and immediately close the ticket, so a response has to reopen it.. it just feels like everything is dismissed
I reported quite a few since 6.4 was first released, and still reproducible in the beta of 6.4 along with 6.5.
IN-121150, IN-121485, IN-125426 and IN-119309.
hunting!
, could be fun
