HOW TO REPORT BUGS

To simplify things for us we ask you not to submit bugs in the forum.

Instead, we ask you to use the Report Bug application that’s installed with Unity.

Include steps to reproduce and attach the project folder that was in use when the bug triggered.

Bugs reported get entered into our bug-tracker (so not lost) and the correct information get’s reported along with it.

Please :wink:

d.

Update April 9 2009 You can also access this feature from inside Unity from the Help menu / Report a Problem. Please read the following blog post for more details:

Bug reporting and you.

Hi David. I notice 2 things … to clarify.

This helper “Report Bug” applet feature in 1.1 basic is accessible from the Help menu under the slightly different name “Report a Problem…”.

And, a question on the types of bugs that should be reported by this mechanism: it explicitly says that it is to be used to report cases where Unity crashed the last time it was run. Is this truly the only sort of “stopper” bug it should be used for? I have several softer bugs to report… some dealing only with consistency issues.

tone

I’ve been using the app to submit non-crashing bugs. I think any bug that is noticeable, is worth reporting. Maybe someone should submit a bug stating that the bug reporting tool is only supposed to be for crashing bugs!

It’s fine to report anything you want with it… crash-bugs, usability bugs, feature requests.

d.

Is there a way that we can report bugs without using the applet?

I ask because sometimes I catch a bug when testing playback of Unity projects, on machines that do not have Unity installed, and when my Unity machine is not handy. This will become even more common, I would think, as many of us start testing stuff on Windows machines.

I’d like to be able to fire off a quick report to Unity while the bug is fresh in my mind. Could you set up a webform for bug reporting?

I would also like this. I will be doing much testing on windows machines. I never know if my bugs get sent with the app any way. I never get any confirmations. Shouldn’t that be automatic?

-Bill

Yet again we have some hiccups with our bug reporting system. This time no bugs should be lost and you can expect your confirmations soon (when the bug queue starts processing real soon now).

d.

Any chance we can get a web-based bug submission system going?

See above.

You can use bugs@otee.dk. We do prefer if people use Report Bug.app however. The advantage of Report Bug.app is that it sends the crash log and graphics card information.

bugs@otee.dk should be good if you are on a windows machine however.

Cool!

Thanks, David.

But when you do, please please remember to include details about the computer (Windows version including service packs, graphics card).

Please :slight_smile:

Without these, some bug reports sometimes are all but useless…

d.

What’s the best way to send just part of a larger scene with a bug report?

I tried selecting the relevant prefab, Exporting Package, creating a new project, and then Importing Package… but it seemed like creating a whole new project was overkill, and it didn’t work anyway: the prefab didn’t bring along its textures, meshes, etc.

So do I have to track down all the pieces manually? Or is there some easier method?

At the moment you have to select all used pieces manually, then use Export package.

My G5 is offline so I cannot use the internal reporting interface. Is the bugs address in this topic still the correct place to send the report?

support@unity3d.com is the new one AFAIK.

Sounds good. I’ll get my hard system crash that requires a power cycle on the default island mission reported to that address.

… and bugs@unity3d.com for bug reports.

Thanks! Just submitted it.

please have a look

140592--5137--$bug_155.jpg

That’s an example on how not to report a bug. Use the Report Bug feature as described at the beginning of this thread.

To ask support questions, start a new thread.