Search Unity

Due to popular demand, we have decided to open our bug database to the public. Take a look at the issue tracker and vote on the bugs that are most important to you here.

We want to enable you to search our known bugs easily, so you can identify problems in your games and find workarounds faster. As a user, you can also comment on bugs, vote on bugs that are important to you, suggest workarounds you found or add information. We will use this information in our ongoing prioritization of bugs, so you can have a very real impact on the future of Unity.

When you have logged in with your Unity Developer Network account, you will have 10 votes you can place on active bugs. If a bug is resolved or in other ways removed, the vote is returned to you. You can always see a list of your own votes on the site.

Privacy has been a huge concern for us, so ANY bug which reveals ANY information about the submitter will NOT be made public. It is a manual task for QA to mark bugs public and the default is that a bug is NOT public. Likewise, we are not sharing projects, logs, attachments or communication on any bug even though it might help others. We simply can’t risk any privacy to be invaded.

The bugs you will see on the site are all confirmed internally in Unity. They are reproducible and acknowledged. If you have sent a report to us, it will not be visible before we have processed it, so it may not even become public, depending on how we decide to handle it. The fields we use are set specifically by us, so no part of what you write will be public without editing and your email address is nowhere on the site.

We are very excited about opening up this new way to communicate with you. We hope it will result in an even tighter and more relevant prioritization of bugs. Enjoy, and use your voting power!

30 replies on “A vote for a bug”

Great news. Now I can look up if my bug was already submitted and if so just vote it! Saves all of us time. Yay! :D

Oh, and when double clicking on the error messages in the console it would go to the line where the error was, not anymore. That was such a nice feature! Why would you remove it?

The latest update for OSX 4.3.1 killed MonoDevelop code autocompletion for C#. I get a few for enums and some methods but I don’t get any suggestions for static classes, or even objects outside of the currently scoped variables. What happened?

@Thomas: Thanks for the reply. Please consider that my feature request. :)

For now, could you address the issue by simply changing the language from “Version” to “Affects Version” for clarity?

@marc: yes, version means where it was found. We simply don’t capture the data internally well enough to expose the “fixed in” in a meaningful way. Maybe some day, but not now.

Terrific addition, IMO, but there’s a bit of an issue with how bugs appear in your tracker. At the moment an issue I’m interested in is listed as “Status: Fixed” and the version reads “4.3.0f4”. To me this suggests that the fix version is 4.3.0f4, but I can most certainly repro the bug in this version. So I’m guessing that version represents the version that the bug affects/was reported in?

I suggest you clarify the field so we see both an “affects version” and a “fix version”. This will enabled us to better help you validate what is/is not truly fixed.


@Kyle: Yes, well, like I said: “So while we use the voting to gauge interest, it doesn’t mean it directly drives our priorities.”. ;-)

@Patrick: I really have no clue what you are talking about and if there is a bug somewhere, the blog is definitely the least effective way of submitting it. The forums are a much better bet.

Is there a problem as cannot play the Slots central game or the test version of Pokie Magic games? Keeps asking to install Unity over and over again

Still waiting for the Linux editor! You know, that thing that has been the #1 most-requested feature for a couple of months now, and is about to be 2,000 votes ahead of #2… :)

@Tiles: We have both priority and severity. Voting will not change that. But it will give us insight into what is important for many of you. This is your voice. If something from 2009 is giving you pain, use it to let us know.

I understand the idea behind. But still, a bug should be fixed when it is known. Not rated. This has the danger that bug reports simply gets ignored then when not enough votings arrives. A voting is no guarantee of the importance of the bug. And no user is crazy enough to go through all reported bugs here. So it is most likely that the bugs at the first two or three pages will collect votings while the other ones will sink in forgotten country.

if even then the sorting should go from showstopper across usability down to cosmetic issues.

Another thing, why are there still open bugs down to version 1.5 from the year 2009 in the tracker? Those are bugs that definitely nobody will fix anymore :)

TILES : human resources is limited. You need a way to prioritize bug.

The idea behind bug vote I think, is to acknowledge and pinpoint which bug is the one that stop the most of the community, which nasty bit should be fixed because it stop a lot of people. That don’t mean a small bug with a few vote won’t get fix. It just mean that it will be fixed in between two other bugfixe will awaiting assignment, or by an interns/junior. Bigger bug that are considered “important” by the community will get the better resources / time allocation.

@William Stallwood, that`s what this public bug database is good for. Most obviously your bug is not reportet yet. So go ahead and create a report for it :)

It is great to open the bugreports to everyone. This will hopefully reduce the number of duplicate reported bugs dramatically. Which frees resources.

The vote feature is a crazy idea though. A bugfix shiould be nothing where you have to vote for. A known bug should be fixed.

I looked everywhere, but I can’t seem to find the bug for: Unity crashes when trying to change scenes or generally open any file. This is a pretty major issue.

Comments are closed.