Bug Reports, no automatic message [Includes video of bug]

I submitted a few bug reports today with attachements but got no automatic responce with ticket number. Is Fogbugs down?

I guess it is down, I have now submitted 18 attempts since when I posted this message. I have a problem where the program completely crashes Unity in the editor or build of the application and I created a small project to prove how this is happening, I will continue to send in the bug report as many times as necessary until Fogbugz actually records the ticket.

Try fewer cups of coffee a day zumwalt :wink:

Sending the same bug report dozens of times isn’t going to like automatically wake the server out of some slumber. More than likely you’re either going to be fruitlessly sending the same report all weekend (yes, it’s the weekend, UT is closed on the weekend), or you’re going to get dozens of redundant tickets flooding into your inbox all at once.

Fogbugz appears to be up and running, but I can confirm that auto-responses are not working at the moment.

[Edit] - My test bug report took a little longer than usual, but the auto-response did arrive.

Thanks for the response, it seems to be a little more than that for me though, I used an old ticket to get into my ticket lists and my tickets don’t show any of the ones I have been submitting here recently through the “report a problem” in Unity 2.5 on the PC. I don’t know why. Each report I am submitting has a project attached to it to show and explain exactly when and where the crashes are happening. Unity itself is still not creating a trouble ticket like it used to in 2.1 when you first load back in after a crash.

I know you all don’t work weekends :slight_smile: I just want to get that ticket in :frowning: My first submission on it was Friday, I figured ya’ll might get a chance to look at it mid week or so. It would be so much easier if I could step through the game loop and identify where or why it is bombing out. I know where it is dieing, on which call to my own C# DLL, which works fine outside of Unity, but inside of Unity, well, Unity justs simply crashes, debugging the crash in assembly doesn’t do me much good, since it is on a ‘mov’ memory address segment, not a peek or pop or even a push, so that does me absolutly no good :frowning:

Once I see a ticket and get a ticket number, I will also submit the working C# project with instructions and attach that code to the ticket to help identify what is going on.

I submitted two reports today, both on a Mac, one from iPhone 1.0.3 and one from Unity Pro 2.5.1, and received the ticket confirmation for each within maybe 15 minutes. These weren’t crash reports, though.

Did you submit them with a 9+ MB attachment?

On the iPhone report, I attached the project, which I’m embarrassed to say was 165MB. I forgot that I still had the XCode build still in there (which accounted for half that space) and an entire font library, which was almost entirely unused. It did take a long time to upload. On the Unity Pro report, I had no attachment.

Very bizzar for me then, this appears to be only a windows issue since everything you are doing is on the Mac and not Unity Pro 2.5.1 on Windows. I will create a video of what I am doing and post the link here, this way you can compare how you are sending in the ticket vs how I am sending in the ticket. Mabye I am doing something bizzarly wrong. (is that a word?)

Video of the submission:
http://screencast.com/t/lZNlyeVuhH

Edit:
Further information about the actual bug that I am attempting to send in can be viewed via this video link.
http://screencast.com/t/CIxUnkZuC

Well this time it created the ticket of 252969 but it didn’t have my zip file attached to it, I then replied to the response with my zip that contained the server code and that went into the ticket as a response, but when I saw my ticket didn’t have my teleporter.zip I then did another response to the ticket and included the teleporter.zip again, and it still didn’t add it to the ticket. I don’t get it.

Edit: few more attempts and it finally showed up, so for some reason attachments or info is just disappearing as it gets to fogbugz, I think it has issues… Anyway, the ticket now has everything in it I think, hopefully anyway. I’ll see by next friday I guess.

Please add ticket 253773 to the list to look into, this one contained a detailed crash report also, different project, I allowed it to send the entire project folder since it was an import of a RAW heightmap of 8192 in size that crashes when you hit the play button. However, the upload notified me of a failure and gave a Unity error window, so I replied to the ticket with a snapshot of the error window. Unfortunately in FogBugz I can’t see if the original ticket that is created has any attachments to it, but I can see if I reply and have an attachment in the reply, that shows up.

I know this ticket just got created today, but it is a follow up to one I created back in April that was replied to today asking me to try again that there was changes between 2.5.1 and 2.5.0 that could have fixed the problem, so technically I think that ticket is now 3 months old, this one just needs amended to it, or joined or what ever. Unfortunately when we create tickets from crash’s, we can’t tell it to amend to an existing ticket (add to wish list probably) Just shoot me a IM if the project in its entirity is attached, thanks :slight_smile: