hi. i was wondering how long it takes unity to respond to a bug report. i reported a bug awhile back that covered two things: bad particles (fixed) which people would laugh at the cause, and the infamous terrain shadow bug in the editor and platform runtime. the shadow bug appears all the time and i am trying to make a high fidelity game that requires dynamic shadows for a day - night cycle and the shadows have to affect the terrain otherwise it looks like crap. i use the latest version of unity and the issue has not resolved with updates and i think i shouldn’t have upgraded from 4.5 as the bug was an editor only thing and i’m not about to downgrade it. i did get an automated response, but is that all i’m gonna get? is the two week wait worth it or is it time to think of an alternative interface (udk, or android studio) and scrap unity. i am some what new to unity but can whip up functional code like my grandma does a delicious cake! any response would be appreciated. thanks in advance i may be too busy in the following months to check back.
Most bugs are looked at within 2 weeks iirc.
That does not mean that they’ll be fixed by then. There is a longer process involved to prioritize and fix bugs depending on if they are even reproducible, critical or duplicate reports of some other reported bug.
There are quite a few threads on this. No need for a new one, especially with a poll.
If you are a Pro user, and have submitted a bug report that includes descriptions and projects that make the problem clear, then it’ll be processed as quick as possible. The Sustained Engineering team fix bugs reported from key customers and make patch releases many times a week. The R&D team currently are fixing more bugs than ever before.
If you are not a Pro customer you might feel frustrated or angry. The chances are that the bug you have reported with your project maps to identical bugs from Pro customers. If you do post the bug number here (the 6-digit case) I’ll take a look and give you some feedback.
hello, Graham.
i am a free user at the moment. (very strict budget) my first attempt was at a buddies place with unity 4.5 pro and got to learn the basics then returned home to download the free version. but as you stated, the dev teams are quite busy, i will wait a bit longer (5.3 update). would it be possible to override the default lighting in unity?
Well, if your buddy is a Pro customer, just ask him to submit your bugs for you. Yeah?
alrighty. i will have to ask em if he is still coding or not, he said a while back that he might leave the coding business.
I have bug reports from 2013 that are still “open”, and I’m a Pro user. Doubt they’ll ever be looked at - does Unity even use FogBugz anymore?
@CptDustmite - strange. If the bug report is complete and includes a project that allows the QA team to view the bug, then I’d assume it would be processed. PM me the bug number and I’ll take a look. Alternatively, if the bug still exists in 5.1.x then post a new one and PM me that bug.
that’s a good question.
well, i think it is time to throw the towel in on coding as my hard drive with my project corrupted its self and i do not have a back up of the project. this is not the first time that this has happened and my bad pc luck only started after i started coding.
@Graham-Dunnett - my hard drive with the project corrupted itself is there a way to recover it from the bug reporting site? if you would like to look at the project the case # is 714231
Might be worth replying to your bug, and providing a more understandable issue. I just looked at the bug report and I don’t completely understand what the problem is.
here. lemme post some pictures when i get the project back to a somwhat level of what it used to be. they do a much better job of explaining than i do 
Yes we do use Fogbugz.
It’s worth noting that our prioritised handling for Pro users was not in effect until March 2015.
If the same bug from 2013 is still present in the latest version of Unity, I would recommend submitting it again with a clearer explanation and repro steps.
@Graham-Dunnett - alright! the project is looking good again. i will post some screenshots of the bug later today.
That’s a bit unfair, because pro or not, we all use Asset Store and buy from.
And a small percentage from non-pro one day will go pro.
Why’s it unfair? Bugs need to get fixed. The QA, Sustained Engineering and R&D teams all handle bugs. The bugs need to be verified and prioritised. How do you think that should be done?
Pro and non Pro users should be able to report bugs equally I think, and all get same priority. Chances to get non valid bugs are the same for pro or non pro. If that’s the worry.
We’re not trying to be fair. The people who have given us a big chunk of cash - cash, btw, which we use to do things like employ QA staff - get better treatment than the people who haven’t (and no, spending $30 in the asset store does not put you on the same footing as someone who’s spent $1500+ on licenses). That’s just what happens when people pay for things: they get things in return.
We still want to give the people who haven’t a good experience as well, which is why we are giving you an entire world-class engine featureset for free.
Well, pay for fix, I can understand that, and I have no problems with.
I was talking about bugs in general. Statistically, is better to gather more reports to have a clear view.
Out of curiosity, from all bugs you have a percentage, what was sent from non pro and pro? And if same bug was posted by pro and non?