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

transparent-screen-after-launch-but-things-are-running-behind-it

Discussion in 'Critical Issues (Blockers, Performance, Crashes)' started by GreyMouser Skye, Jul 30, 2018.

  1. GreyMouser Skye

    GreyMouser Skye Avatar

    Messages:
    1,168
    Likes Received:
    1,982
    Trophy Points:
    125
    Location:
    Wherever the Moongates take me.
    It was a good thought. But no, it did not work. I renamed the directly and watched a new get created as I started the game. Interestingly it did not run the opening cutscenes, so maybe there are other settings elsewhere.
     
  2. Feeyo

    Feeyo Avatar

    Messages:
    1,505
    Likes Received:
    2,196
    Trophy Points:
    113
    Location:
    Aelasar’s Forest
    There are 2 options left, 1. fully delete the shroud directory and uninstall, and delete the port roaming directory. Download the latest patcher and install SotA again.
    2. Most extreme option: reinstall your windows operating system...
     
  3. GreyMouser Skye

    GreyMouser Skye Avatar

    Messages:
    1,168
    Likes Received:
    1,982
    Trophy Points:
    125
    Location:
    Wherever the Moongates take me.
    I have contemplated option 2. Might be a good reason to move to win10 Pro instead of this stupid win10 Home that came pre-installed. Definitely need to free up time and get my ducks in a row if I go that route.
     
  4. Feeyo

    Feeyo Avatar

    Messages:
    1,505
    Likes Received:
    2,196
    Trophy Points:
    113
    Location:
    Aelasar’s Forest
    Yep, that route is pretty painful. :(
     
  5. GreyMouser Skye

    GreyMouser Skye Avatar

    Messages:
    1,168
    Likes Received:
    1,982
    Trophy Points:
    125
    Location:
    Wherever the Moongates take me.
    @Feeyo Latest update. I forced the nvidia control panel to use the integrated graphics card and I was able to see Shroud again. This was part of a fix in the Steam community for a game called Dark Souls. I was not able to make any changes in the video settings though to make it work again when I switched it back to nvidia card. But this is a step! It does happen to other people and other games and it might be linked to anti-aliasing. My guess is that a Unity change caused it since it happened after a patch.
     
    Jaesun and Feeyo like this.
  6. Feeyo

    Feeyo Avatar

    Messages:
    1,505
    Likes Received:
    2,196
    Trophy Points:
    113
    Location:
    Aelasar’s Forest
    Good to hear your a bit closer to resolving it. Thanks for the update.
    The AA setting in nvidia and or AMD sometimes does weird rendering in some games. When this happens I mostly just force application setting for AA. You could give that a try, or disabling AA in SotA settings. See if that changes anything?

    Try adding the option: -force-clamped in Sota Launcher and see if it runs.