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

crash data

Discussion in 'Release 32 Bug Forum' started by tomelectric, Jul 29, 2016.

Thread Status:
Not open for further replies.
  1. tomelectric

    tomelectric Avatar

    Messages:
    65
    Likes Received:
    34
    Trophy Points:
    8
    I crashed and was asked to send the crash data.











    Loc: (401.6, 11.9, -359.5) Area: NoviaSotA.EarlyAccess.Win.64.449.Date.07.28.16GPU: NVIDIA GeForce GTX 650 GPU RAM: 994CPU: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz (8) System RAM: 12237OS: Windows 10 (10.0.0) 64bitUser Specs:Steps to Reproduce: Details: Blocker? Reproduction Rate: Title: 7/29/2016 7:52 AM
     
  2. Attenwood

    Attenwood Portalarian Emeritus Dev Emeritus

    Messages:
    6,910
    Likes Received:
    5,864
    Trophy Points:
    153
    You can send the crash folder to rromero@portalarium.com. Additionally, if you could describe where and what you were doing when the crash was observed. Thank you for reporting.
     
    tomelectric likes this.
  3. tomelectric

    tomelectric Avatar

    Messages:
    65
    Likes Received:
    34
    Trophy Points:
    8
    thanks will do and done.
     
    Attenwood likes this.
  4. tomelectric

    tomelectric Avatar

    Messages:
    65
    Likes Received:
    34
    Trophy Points:
    8
    Crashing seems to happen more frequently now in game, I am sending the crash data from the past few days in individual emails. Should I perhaps try the no cloth trick from last release? I am getting a new PC so my i7, 3rd gen, 12 GB DDR3 RAM, Nvidea 650 GTX, 1 TB SATTA HD will change maybe that will help fix it. I seem to be crashing at least 2-3 times per session and always when zoning out of a zone.
     
    Last edited: Aug 4, 2016
  5. Attenwood

    Attenwood Portalarian Emeritus Dev Emeritus

    Messages:
    6,910
    Likes Received:
    5,864
    Trophy Points:
    153
    Thank you for reporting. We are aware of the issue and are monitoring its progress as we work on potential solutions.
     
Thread Status:
Not open for further replies.