1. This forum is for bug reporting of current Live Game Server issues ONLY.
    Be sure to follow the format below, it will help us out greatly in responding. If you do not, your report may not be entered into the system.

    Read BEFORE submitting your first bug: Reporting Bugsā€¦ QA 101 Document
    • Search for your bug in all likely categories before posting in order to avoid duplicate reports.
    • Be sure to provide details of what the issue is and how to re-produce it, but keep your bug report factual.
    • Only report oneissue per thread, additional issues may be ignored.
    • Do not add, include or modify the thread moderator tags in the title of the thread. (indicators in the [])
    • Reply to an existing thread if you have additional information for the reported bug.
      Do not use this forum for commentary, your post will be deleted and you may be moderated, suspended or banned if the activity continues.
    • There is no need to submit crash logs. Crash data we require is automatically logged.
    NOTE: Important information including your location and system specs are automatically put into your clipboard when using /bug in the game (DO NOT add additional system specs unless requested). When starting your post, just use <CTRL>-V to insert the data and fill in the entries with no data.

    Please include Screenshots if possible. Images can be saved on our SotA Discord Server here

    If the clipboard does not work, use and fill in this Bug Report Template:
    1. Title:
    2. Reproducible?
    3. Blocker?
    4. Details:
    5. Steps to Reproduce:
    6. User Specs: (RAM, CPU, GPU and Operating System only)
    Dismiss Notice
Dismiss Notice
This Section is READ ONLY - All Posts Are Archived

[Fixed] Game crashes trying to login on Release 76, build 1156

Discussion in '*** Bug Report Archive (After R75) ***' started by Dereck Visaard, Apr 1, 2020.

  1. Dereck Visaard

    Dereck Visaard Avatar

    Messages:
    252
    Likes Received:
    443
    Trophy Points:
    40
    Gender:
    Male
    Location:
    Austin, TX
    Title: Game crashes trying to login on Release 76, build 1156.
    Reproduction Rate: 100%
    Blocker (crash, can't continue)? Yes!
    Scene Name: N/A
    /loc coordinates: N/A
    Details: I can start the launcher, start the main UX and manipulate options, but when I try to login, Unity crashes and I get the unhelpful crash banner.

    [​IMG]

    Corresponding Event Log Error (seems to be Mono barfing):

    [​IMG]

    Rig info:

    [​IMG]

    [​IMG]

    @Chris
     
  2. Ravalox

    Ravalox Dev At Large Moderator SOTA Developer

    Messages:
    1,202
    Likes Received:
    2,433
    Trophy Points:
    125
    Gender:
    Male
    Location:
    Dallas, TX
    Noting a few things from your screen shots. Looks like your CPU is below minimum specification for the game (Minimum is Quad core @ 2.4 GHz) [See Specs here: https://www.shroudoftheavatar.com/?page_id=19]

    Since you are using Windows 10 Enterprise, please be sure that your organization allows for the game to run and has not used Group Policy to block it.

    Also wondering what you are using for a GPU, there is not an indication if you are using the embedded GPU in the i7 or a standalone GPU.
     
  3. Dereck Visaard

    Dereck Visaard Avatar

    Messages:
    252
    Likes Received:
    443
    Trophy Points:
    40
    Gender:
    Male
    Location:
    Austin, TX
    Thanks for the reply, @Ravalox . However, I've used this rig for logging in for obligatory things like paying taxes for several releases with no issue. It wasn't until R76 that it crashed. Others have posted about similar crash behavior in R76, so I doubt it's my CPU speed unless you just raised the speed requirement in R76 ;) For your questions:

    1) Organization is not blocking anything. See my note above.
    2) Using the i7 GPU.

    Thanks,
    Dereck
     
  4. Dereck Visaard

    Dereck Visaard Avatar

    Messages:
    252
    Likes Received:
    443
    Trophy Points:
    40
    Gender:
    Male
    Location:
    Austin, TX
    To close the loop on this, patch 1159 fixed it. NO changes to my rig ;)