Announcement

Collapse
No announcement yet.

Unreal Engine Bug Submission Form

Collapse
This is a sticky topic.
X
X
  • Filter
  • Time
  • Show
Clear All
new posts

    #16
    Originally posted by Amanda.Bott View Post
    Why did we do this?
    There were a significant number of bug reports coming in with insufficient information, so this form was created to increase the likelihood that we'll be able to reproduce bugs that have been submitted and increase the rate at which bugs are processed.
    Im not the biggest fan of AnswerHub but I do agree with everyone that the collaboration is an important part of resolving issues. With that said why not have a stream on how to report bugs and give people who arnt at Epic the required vocabulary to communicate more effectively. That seems to be the biggest hurdle is Epic seems reluctant to trust the community and some Q/A staff are less experienced with the engine than community leaders, it could even be a chance to employ some of these experienced UE4 users from the community who already have a rapport with us.

    I appreciate the move to try and refine the process and make it more cost effective for everyone, overall though Epic need to show people that correctly reporting a bug is worthwhile by not treating the community like minions, Ive seen some pretty poor attitudes towards people who are taking their own time out to try to help Epic. On the flip side Ive seen some really poor attitude from the community but those people are weeded out quickly and not taken seriously by the community or Epic so I dont see this as problematic.

    My solution would be making badges worth something and trusting some community members (as they are with forum moderation) to do official bug reports, to act as technical community leaders who can be a go to for people wanting to make serious requests and/or bug reports. Even if these people were Epic employees but on a whole I dont see much socialising and team building from Epic in the community and thats what it takes to build trust, its entirely possible that Epic employees are incognito but that doesnt really help. I would just like to see less barriers and more sharing of not just knowledge but intellect

    I believe thats the best way to bolster not only bug reports but the community and UE longer term.
    Last edited by MonsOlympus; 01-10-2018, 04:38 AM.

    Comment


      #17
      Lots of times I'll find a bug, go to report it, and find someone else already reported it. Then when I find a workaround, I post it on their Answerhub thread so that everyone can benefit. The same thing happens on my bug reports. I feel like this change is going to kill off a lot of discoverability, communication, searchability and community problem solving.

      And it is going to make following up on your own bug reports difficult if you find out more information. There will be nowhere to post the additional information until things have gone through several steps.

      I don't really mind if it is through Answerhub or not in the end, but it would be nice to be able to comment on the bug reports and easily keep track of them. Otherwise this is almost just like the crash reporter.

      Comment


        #18
        I would think a simple solution would be to make this form auto-post to AnswerHub. That way all bug reports get posted to AnswerHub and everyone would have access to new and existing bug reports via AH, but Epic would still get reports sent directly to them with this new system, and it would have the added benefit of standardizing initial information AnswerHub bug reports. Just a thought.

        Comment


          #19
          I'd guess Epic is using Jira(like a lot of other companies) for BugTracking. Is there any consideration of making a mirrored public Jira?
          Embarcadero does this for their products, for example. So you can report a Bug in Jira, it gets a mirrored entry to their internal Tracker. And once done, they mirror the result back to the public one.

          This allows proper discussion in a detailed Ticket.

          I use Unreal only for sparetimeprojects but work at a NonGaming-Softwarecompany. We use Jira, and the options for organization and filtering are great.

          Comment


            #20
            [QUOTE="Amanda.Bott;n1410564"]Why did we do this?
            There were a significant number of bug reports coming in with insufficient information, so this form was created to increase the likelihood that we'll be able to reproduce bugs that have been submitted and increase the rate at which bugs are processed.

            In many cases, I've seen where a number of people will have the same issue, but Epic can't reproduce it because they don't have access to the sort of complex project where the problem occurs. The old standby, "reproduce it in a clean project" is meaningless in most contexts.

            What about visibility and collaboration?
            Bugs will be visible on the Public Bug Tracker after we're able to reproduce them and it is determined not to be a design request. You can always create a public thread on AnswerHub discussing the issue and reference the ID of the bug, once it becomes available. You'll still be able to collaborate, discuss issues, and work on solutions together.

            Again, Epic can't reproduce them so this presumes that the issues don't exist. Sorry, that's completely bogus.

            What if Epic needs more info?
            If an email address is provided in the form and the team needs clarification around the bug, then they'll reach out to do so.

            Meaning, Epic plans to stop communicating directly with bug submitters.



            WIP Thread

            Comment


              #21
              What happened to Chance? I liked that guy. Also finally, a real bug form.

              Comment


                #22
                I also think that the collaboration and public tracking of unconfirmed *bug* reports on answer hub from others has been essential at times. It would be a shame to lose that.

                Comment


                  #23
                  Originally posted by Raf View Post
                  I also think that the collaboration and public tracking of unconfirmed *bug* reports on answer hub from others has been essential at times. It would be a shame to lose that.
                  The answerhub is a joke, no reason the person posting the bug couldn't post it here as well.

                  Comment


                    #24
                    Originally posted by John Alcatraz View Post
                    As I said, I reported probably more than 100 bugs on the answerhub. I got a response from Epic on every single one of those. Epic always said they will respond to your bug report on the answerhub within a few days, and if they don't, you should bump it until you get a response.
                    I would say you are lucky. If I didn't ping a developer on Twitter I would never have got an answer on my entries, I'm still waiting for answers on some of them by the way. To my point of view, the AH is a mess, it's very hard to track down problems and also see if other users already reported a bug I'm facing.
                    - [Marketplace] Sci-fi and Glitch Post-process
                    - [Tutorial] Anamorphic Bloom
                    - [Tutorial] True First Person Camera

                    Fabrice Piquet - Technical Artist, Product Designer @Allegorithmic
                    Twitter - LinkedIn - Portfolio - Maya Scripts

                    Comment


                      #25
                      bug when spawning player

                      Hi, I started a new project a week ago and I encountered problems when I added two beginnings of players on the same level, the first player appears in the correct place of the beginning of the player, plus the second appears in another place far away and in below the already dead level and when I go back to the screen of the first player who spawned correctly appears as if I was seeing the second player in the correct location but through another place, how do I solve this ???? It's a bit confusing, but watch the pictures closely

                      Comment


                        #26
                        This is awesome; The engine support team told me they got "19" crash reports coming from "ChangeState()" function which invokes "SetState()" of my UFSM Plugin...
                        However, my plugin doesn't have any "ChangeState()" function whatsoever. These reports are coming from a modified version of the plugin.

                        I wish the bug report include more details about third-party libraries, my plugin in this case, and the report should explicitly tell if the library has been modified or not.
                        I just went bug hunting and saw that those reports didn't make sense after I realize they've modified the plugin's source code and the crash was coming from something that doesn't officially exist in my code ^^

                        But still, the fact they are tracking these reports, and contacted me with a resume of these reports... Made me happy! the guys are working hard to make things better.
                        Last edited by BrUnO XaVIeR; 01-13-2018, 06:23 AM.
                        | Finite State Machine | Auto-Save Plugin | USQLite Plugin | Object-Pool Plugin | Sound-Occlusion Plugin | Anti-Cheat Plugin |

                        Comment


                          #27
                          So, now it just feels like we're firing bug reports into the void.

                          There's no way to even see the bug you've just submitted, let alone do any of the things you're likely you want to do after submitting a bug such as editing it, adding more information, etc.

                          Being able to submit bug reports through a dedicated channel would be a good idea if we were actually submitting into the real bug tracker, but it seems that they don't trust us enough to let us do that.

                          So...
                          Pros:

                          - More structured entry form.

                          Cons:

                          - No more feedback for submitting a bug
                          - No ability to edit or add to bug reports
                          - No way to tell if the bug has already been submitted (until it reaches the verified bug tracker)
                          - No way to know if the bug has been rejected for some reason
                          - No way way to find the bug in the tracker if it does get raised
                          - No way for Epic to ask for more information about a bug from anyone but the original submitter (if they entered an email)
                          - No way to discuss the bug with others (except making a separate thread)

                          How is this an improvement for anyone?
                          Am I missing something?
                          Last edited by Nameless Voice; 01-15-2018, 01:48 PM.

                          Comment


                            #28
                            Originally posted by ronm6667 View Post
                            I would think a simple solution would be to make this form auto-post to AnswerHub. That way all bug reports get posted to AnswerHub and everyone would have access to new and existing bug reports via AH, but Epic would still get reports sent directly to them with this new system, and it would have the added benefit of standardizing initial information AnswerHub bug reports. Just a thought.
                            I posted a response and then I saw the above. GREAT idea! Also, people can post work-arounds.....general information for all to see.

                            teak
                            "A little bit of nonsense now and then is cherished by the wisest men..."
                            -- Willy Wonka

                            twitter: @teak421 -- Smooth Zoom Camera Plugin for 4.14+: here.

                            Comment


                              #29
                              Originally posted by teak421 View Post

                              I posted a response and then I saw the above. GREAT idea! Also, people can post work-arounds.....general information for all to see.

                              teak
                              I would think a simple solution would be to make this form auto-post to AnswerHub. That way all bug reports get posted to AnswerHub and everyone would have access to new and existing bug reports via AH, but Epic would still get reports sent directly to them with this new system, and it would have the added benefit of standardizing initial information AnswerHub bug reports. Just a thought.
                              ​​​​​​​
                              Good idea indeed.

                              Comment


                                #30
                                Another thing I noticed - the bugs that do get posted to the tracker don't have any reference to the original bug report.

                                Assuming that's the same ticket that the developer working on the issue sees, it means that they don't have easy access to the full information about the bug.

                                The description in the ticket itself is a brief summary of the ticket, which doesn't necessarily include all the information that the original reporter put into their report.

                                Comment

                                Working...
                                X