1. Avatars, the latest QA release is upon us! Please use this forum for bug reporting of this QA release ONLY. Do follow the format below, because it will help us out greatly in responding. If you do not, it's possible your bug report will be misinterpreted, or worse, lost!

    Read BEFORE submitting your first bug: Reporting Bugs… QA 101 Document
    • Search for your bug before posting in order to avoid duplicate reports.
    • Only reply to an existing thread if you have additional information for the reported bug. ALL extraneous commentary will be deleted to avoid cluttering the reports.
    • Keep your bug report short and factual.
    • There is no need to submit crash logs. Crash data we require is automatically logged.
    Bug Report Template
    1. Title:
    2. Reproduction Rate:
    3. Blocker?
    4. Details:
    5. Steps to Reproduce:
    6. User Specs:
    To get started, use /bug in-game (/devbug if on QA) to auto-create this template. It will even auto-fill some of the required information and open the browser for you. Then take the information that was just saved to your system's clipboard and paste it into a new QA forum post. Thank you bug hunters!
    Dismiss Notice
  2. We have a QA initiative where we work with the community more closely than ever to get your bug reports into the hands of the developers. Please use this forum for LIVE Server bug reporting. Do follow the format below, because it will help us out greatly in responding. If you do not, it's possible your bug report will be misinterpreted, or worse, lost!

    Read BEFORE submitting your first bug: Reporting Bugs… QA 101 Document
    • Search for your bug before posting in order to avoid duplicate reports.
    • Only reply to an existing thread if you have additional information for the reported bug. ALL extraneous commentary will be deleted to avoid cluttering the reports.
    • Keep your bug report short and factual.
    • There is no need to submit crash logs. Crash data we require is automatically logged.
    Bug Report Template
    1. Title:
    2. Reproduction Rate:
    3. Blocker?
    4. Details:
    5. Steps to Reproduce:
    6. User Specs:
    To get started, use /bug in-game (/devbug if on QA) to auto-create this template. It will even auto-fill some of the required information and open the browser for you. Then take the information that was just saved to your system's clipboard and paste it into a new QA forum post. Thank you bug hunters!
Dismiss Notice
This Section is READ ONLY - All Posts Are Archived

[Resolved] Unity2018.x laggy performance when walking in heavy decorated instances.

Discussion in 'Critical Issues (Blockers, Performance, Crashes)' started by Feeyo, Jun 14, 2018.

  1. Feeyo

    Feeyo Avatar

    Messages:
    1,620
    Likes Received:
    2,383
    Trophy Points:
    113
    Location:
    Aelasar’s Forest
    6/14/2018 8:39 PM
    Title: laggy performance when walking in player owned towns and heavy decorated instances.
    Reproduction Rate: 100%
    Blocker? Kinda yes.
    Details: Having the shadow settings enabled and in heavy decorated scenes the character keeps walking when releasing your (A,W,D, S) keys. When I disable shadows completely it does not happen anymore.

    Steps to Reproduce: Enable shadows and walk in player owned towns or any other heavy decorated places. When walking for a little time, try releasing the walk keys. Your avatar will keep on walking for some time.

    User Specs:
    OS: Linux 4.17 unknown 64bit
    CPU: Intel(R) Core(TM) i7-3960X CPU @ 3.30GHz (6) System RAM: 32088
    GPU: Radeon RX 580 Series (POLARIS10 / DRM 3.25.0 / 4.17.0-0.rc1.git1.1.fc29.x86_64, LLVM 6.0.0) GPU RAM: 8105
    SotA.QA.Linux.64.697.Date.06.13.18
    Area: POT_forest_metropolis_01a_template/Aelasar's Forest
    Area Display Name: Aelasar's Forest
    Loc: (117.4, 38.0, 266.0)
    Debug: UE9UX2ZvcmVzdF9tZXRyb3BvbGlzXzAxYV90ZW1wbGF0ZXxBZWxhc2FyJ3MgRm9yZXN0fCgxMTcuNDI0LCAzOCwgMjY1Ljk1NCl8KDAsIC0wLjYxNSwgMCwgLTAuNzg5KXwtMjgzLjk4NDR8My4xOTcxMTF8Ny42MTEwMTg=

    Xorg config:
    cat /etc/X11/xorg.conf.d/20-gpu.conf
    Section "Device"
    Identifier "AMD"
    Driver "amdgpu"
    Option "DRI" "3"
    Option "TearFree" "true"
    EndSection
     
  2. Feeyo

    Feeyo Avatar

    Messages:
    1,620
    Likes Received:
    2,383
    Trophy Points:
    113
    Location:
    Aelasar’s Forest
    This bug report was added when testing for the latest Unity. I guess we know that 2018.x is bad for us Linux users. Putting it on Known.
     
  3. Alley Oop

    Alley Oop Bug Brigade – Bug Hunter

    Messages:
    8,387
    Likes Received:
    13,563
    Trophy Points:
    153
    @Feeyo, please don't flag your own bug reports known unless you have a jira number to reference to back it up.
     
  4. Chris

    Chris Tech Lord Moderator SOTA Developer

    Messages:
    2,289
    Likes Received:
    26,164
    Trophy Points:
    190
    Gender:
    Male
    Going to mark this as resolved as R55 will still be on Unity2017 due to the blocker input bug in all newer versions than 2017.2.