Dismiss Notice
This Section is READ ONLY - All Posts Are Archived

Launcher Issue Patch settings pointing to wrong server

Discussion in 'User Interface (Including Launcher)' started by Diego Mas, Feb 23, 2018.

Tags:
Thread Status:
Not open for further replies.
  1. Diego Mas

    Diego Mas Avatar

    Messages:
    131
    Likes Received:
    60
    Trophy Points:
    18
    Gender:
    Male
    Location:
    West Coast
    Title:Launcher Issue Patch settings pointing to wrong server
    Reproduction Rate: Many times restarting launcher, one computer
    Blocker? Yes it was, workaround seems to be found
    Details:

    The launcher would not fully patch Thursday morning ~8-11 PST ; it started then closed. When restarted it did not patch.

    Was not able to work the issue until now. After analysis the standalone patcher was downloaded and changed some things.

    One file was patchsettings.txt which pointed to the wrong server:
    Code:
    universalPatchInfo=https://www.shroudoftheavatar.com/update_service/patcher.php
    BuildTarget=QAStandaloneWindows
    
    This was on my Production installation not the QA directory version. The QA was patching fine but did not test, assumed the server was shutdown at that point.

    The version it patched up to this morning was 730.Date.1.30.18 but would not patch furthur, I believe this computer was previously on 0728 version before starting.

    Workaround solution: copy patchsettings.txt file from downloads/StandaloneWindowsPatcher_0_129.zip to main Launcher_Data directory (renaming the bad file to post). Restart Launcher patching as normal.
    Just started Client 0733.Date.02.22.18


    Steps to Reproduce: I suspect that the first version of Launcher Patch moved from QA to Production had not updated the patchsettings.txt The problem was probably fixed quickly, but my system caught the bug. This is posted for reference if anyone wants to avoid a full redownload as would be recommended. Its possible that there was some memory/storage crossover from QA to Production because QA Launcher was also running at the time.1
    Would not recommend reproducing this problem.
    Note: after seeing the patch size is more than half a full download it might have been simpler to just pull the whole thing, more download time, less patching time, less trouble. But it was a puzzle to solve.

    User Specs:
    OS: Windows 7 Service Pack 1 (6.1.7601) 64bit
    CPU: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz (8) System RAM: 32714
    GPU: NVIDIA GeForce GTX 1070 GPU RAM: 8085
    SotA.EarlyAccess.QA.Win.64.730.Date.01.30.18 (Read from screen this morning)
     
    Lexie likes this.
  2. Lexie

    Lexie Bear Queen Emeritus

    Messages:
    842
    Likes Received:
    2,903
    Trophy Points:
    93
    Thank you very much for posting this. Hopefully this won't happen again, but your post is informative.
    @Diego Mas
     
Thread Status:
Not open for further replies.