1. 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

Map Alignment issue in Linux

Discussion in 'User Interface (Including Launcher)' started by AoiBlue, Feb 5, 2019.

  1. AoiBlue

    AoiBlue Avatar

    Messages:
    137
    Likes Received:
    98
    Trophy Points:
    30
    Gender:
    Male
    02/05/2019 22:18
    Title:Map Alignment issue in Linux
    Reproduction Rate:100% on towns, only some towns are affected.
    Blocker?
    Details: [linux] map layer alignment is incorrect in many scenes
    Steps to Reproduce:Load an affected town and note how the various layers (e.g. player housing and base town map)
    User Specs:
    OS: Linux 4.18 Ubuntu 18.04 64bit
    CPU: AMD Ryzen 5 1500X Quad-Core Processor (8) System RAM: 16032
    GPU: AMD Radeon (TM) RX 480 Graphics (POLARIS10, DRM 3.26.0, 4.18.0-14-generic, LLVM 7.0.0) GPU RAM: 8010
    SotA.Linux.64.906.Date.02.05.19
    Area: Novia_R5_City_Brookside
    Area Display Name: Brookside
    Loc: (-52.7, 50.0, 460.1)
    Debug: Tm92aWFfUjVfQ2l0eV9Ccm9va3NpZGV8fCgtNTIuNjUyLCA1MC4wMzksIDQ2MC4wNTUpfCgwLCAwLjI0NiwgMCwgMC45NjkpfDIyMi44NTE1fDguOTEyNjc3fDEuNjg5OTQ=
     
  2. Undone

    Undone Trap Master Moderator SOTA Developer

    Messages:
    327
    Likes Received:
    801
    Trophy Points:
    43
    If you visit the same map on www.shroudoftheavatar.com/map are the lots misaligned in the same way? I suspect this is not a linux-only issue, but rather a data issue I'll look into.
     
  3. Undone

    Undone Trap Master Moderator SOTA Developer

    Messages:
    327
    Likes Received:
    801
    Trophy Points:
    43
    Appears as though the Brookside lots are flipped on the x-axis data wise. Looking into a fix.
     
    Last edited: Feb 13, 2019
    AoiBlue, Barugon and Jaesun like this.
  4. AoiBlue

    AoiBlue Avatar

    Messages:
    137
    Likes Received:
    98
    Trophy Points:
    30
    Gender:
    Male
    Thank you. A LOT of maps have this bug. Can you either go through them all or better yet, look into what's causing it so a manual fix will be unnecessary?
     
  5. Undone

    Undone Trap Master Moderator SOTA Developer

    Messages:
    327
    Likes Received:
    801
    Trophy Points:
    43
    In the past I have detailed why this is not an easy (nor a quick) fix. It involves a lot of coordinate transformations and such that are non-trivial. I've slowly been trying to get the lots sorted out but my top priority for the map is making sure that the avatar location and rotation are working.
     
    AoiBlue and Jaesun like this.
  6. AoiBlue

    AoiBlue Avatar

    Messages:
    137
    Likes Received:
    98
    Trophy Points:
    30
    Gender:
    Male
    It's just a guess, but it might be that the orriginal transform metadata is being lost somewhere along the way between content creation and publication. The most likely case is if metadata stripping is after compression rather than before. This can cause this exact error, as some compression techniques use these exact lossless transforms then use metadata to reverse it.