Announcement

Collapse
No announcement yet.

READ FIRST: Welcome to the UT Editor Bug Reporting Forum!

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

    [OFFICIAL] READ FIRST: Welcome to the UT Editor Bug Reporting Forum!

    READ FIRST: Welcome to the UT Editor Bug Reporting Forum!

    Welcome to the UT Editor Bug Reporting Forum!
    Here you will be able to report bugs found while using the UT Editor. For help/support with builds and other technical issues please visit your respective operating system sub-forum (links are located below).

    Before you report any bugs please attempt to search the forums and JIRA (This bug database is very much a work in progress) to see if anyone else has discovered similar issues. This will help us prevent duplicate reports from being generated. If the issue has been posted already please provide any additional information you may have about the issue in their thread.



    Preferred Method of Reporting Bugs
    Summary: Brief summary of the issue
    Version: Version or name of the build found
    Operating System: The OS of the machine that the bug was discovered on
    Description: If necessary a more detailed description
    Steps to Repro: Steps needed to reproduce the issue
    Attachments: Any attachments needed to help demonstrate the bug



    An example being:

    Summary:

    Using PIE crashes the UT editor when launched from the Epic Portal.

    Version:
    ++depot+UE4-UT-Releases-CL-2601606

    Operating System:
    Windows 7 Professional 64-bit (6.1, Build 7601)

    Description:

    Whenever using PIE in the editor the editor will crash. This is preventing rapid iteration and is impacting many users.

    Steps to Repro:
    1. Launch the UT Editor from the Epic Portal.
    2. Right click and select "Play From Here" in the example map that opens.


    RESULT:
    The UT Editor will crash.

    Attachments:
    Attach any necessary pictures, logs, or videos




    Tips for helping us track down bugs
    1. Provide a quick synopsis of the issue or bug you’ve discovered in the thread title. Try to avoid short titles like “Found a bug…” and “just crashing”.
    2. Include extra information about the bugs conditions. Does it only reproduce online, local games, dedicated server only, etc.. If you discover a bug during online play, it is very useful to see if you can reproduce it locally in a standalone game. This helps determine whether the bug is likely to be game code or net code related.
    3. Feel free to include any additional information that can help track down issues (Pictures, Videos, Logs, dxdiag, etc).

    Additional information to assist with tracking down crashes
    1. Providing us with the crash report or the game logs from the crashed session is one of the best ways to assist with tracking down crashes.
    2. Log/Dump files are saved within the game’s “Saved” folder and can be found at C:\Users\%username%\Documents\UnrealTournament\Saved\Logs or …\WindowsNoEditor\UnrealTournament\Saved\Logs
    3. Additionally, providing us with the DxDiag of your computer will allow us to troubleshoot issues more efficiently by being able to understand more about the machine that is being impacted by an issue.



    UTBugIt Information - UPDATE 1/6/2015
    We now have a new tool in our arsenal to help track down level specific bugs or acquire screenshots of issues in game. You can now use the console command "UTBugIt"!

    If you locate a bug within a level you can look at the issue in game and type "UTBugIt FileNameHere" (FileNameHere being what ever you would like the name of the folder to be). This will generate a folder with a screenshot of you were looking at in the game at the time the command was entered and it will provide a text document with various information about the map and location the screenshot was taken. Using this tool will help level designers track down various issues that might have been hard to describe before or would have needed a video to demonstrate how to get to a location.

    Folders generated by this command are by located by default at:
    C:\Users\%username%\Documents\UnrealTournament\Saved\BugIt\WindowsNoEditor on Windows
    &
    Documents -> UnrealTournament -> Saved -> BugIt on Mac

    If you are a level designer or someone working within the engine you can use the text file included with a UTBugIt to teleport straight to the location where the command was entered originally. To do this you will need to locate the UTBugIt folder in question.

    1. Open the BugIt folder and inside you will see the screenshot of the location of where the command was entered as well as a text file.
    2. In the text file there is a line that begins with "BugItGo."
    3. Copy the entire line that begins with BugItGo and then paste that into the console in the engine while you have the same map open.
    4. This will move your camera/player immediately to the location in question.

    A BugItGo will look like this for example "BugItGo 1019.630371 1469.357666 844.150024 -2.792053 20.861773 0.000000".


    Other Bug Reporting Forums:
    For any issues relating to general UT Development and Bug Reports/QA please post on this forum:
    https://forums.unrealtournament.com/...Bug-Reports-QA
    For any issues relating to the Windows x64 and Windows x86 builds please post on this forum:
    https://forums.unrealtournament.com/...roubleshooting

    For any issues relating to the Mac builds please post on this forum:
    https://forums.unrealtournament.com/...roubleshooting

    For any issues relating to the Linux builds please post on this forum:
    https://forums.unrealtournament.com/...roubleshooting





    Thanks everyone for your help and thanks for helping make Unreal Tournament better!

    -RZE
    Last edited by RZE; 07-07-2015, 05:30 PM.
Working...
X