Bug report response time

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.

 

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?

 

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?

 

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

 

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

 

@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.

 

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.

 

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?

 

i agree in some ways there. the bug team should look at bugs of all sorts and from all users as the same but superpig does have a point. you do get a fully functional game engine and a decent one too, there is one catch though. the infamous terrain shadow artifact. i myself do intend to buy a copy of unity but i want to see the terrain shadow bug gone first. and for $1500, that's not too bad where as if you were to buy something like cry engine you would pay several hundred thousand or maybe a couple million to buy a copy of the engine. i am debating myself though, wether to keep using unity or use udk, i want to keep using unity because it is easy to use and udk is quite confusing but has much less bugs in it (i have messed with it checking out its interfaces and made a rather complex test scene like i have in unity) udk does NOT come with a template package like unity and thus you must start from scratch. but back on topic yeah i agree that the unity bug system could use a little work, all bugs should be treated the same for all users. they analyze it (look at the scene) create a name for it then add it to a database where any duplicates are scrapped which could mean the new bug report as it was a copy of what was already in there.

 

I'd LOVE it if someone could explain to me in reasonable terms, why DOES IT take a lifetime to pack a report ?
I could turn old waiting I wonder how many bugs are missed for people wanting to get back to DEV TIME