🛈 Announcement
Greetings! The Division forums are now archived and accessible in read-only mode, please go to the new platform to discuss the game
  1. #81
    Originally Posted by Sircowdog1 Go to original post
    Apparently AC Valhalla is also recently plagued by crashes. To such an extent that at one point the devs werd telling players to just not go to certain areas in the game.
    Didn't know that, I grabbed Odyssey on sale last month, or maybe January, and haven't had any problems. Division 2 is the only game I own that I ever have issues with it running, and it varies wildly. After they fixed the broken launcher, I was able to play just fine, prior to the broken launcher I was able to play just fine, too. Then they do a maintenance, and now I'm getting deltas, freezing, and ctd's in every session.
    Share this post

  2. #82
    I still crash the game after the update but it's not just me. A friend uninstalled the game because it fit four times in a row and he doesn't want to play the game until it's all fixed
    Share this post

  3. #83
    THE_Crazy_Hyena's Avatar Member
    Join Date
    May 2019
    Location
    District Union Arena
    Posts
    416
    Mine tends to crash straight to desktop once about one minute after connecting to the game. Then it runs fine on the second start.
    No idea why it acts like that. A friend of mine has the same issue where he would experience a straight C2D (no black screen or anything). Game just turns off by itself. And then it works fine after restarting.

    Don't think it has something to do with system specs, or I'm not really sure, because another friend does not have this issue, and he's running an AMD graphics card.
    My specs are: ROG Strix X570E, AMD Ryzen 9 3900X, GTX 1080 Ti, 32 GB RAM (@3000 MHz). Game runs off an SSD. and the one friend that's been having similar issues also has a 1080 Ti in his rig, though he's on the older X370 platforn, running a Ryzen 7 1700X.
    Makes me wonder if this is an issue related specifically to Nvidia hardware, or if it's just by random.
    Share this post

  4. #84
    well, i had the crashes on my pc too...they fixed it, yeah,,,and it worked for about a week or so...now my pc version is crashing again.
    Share this post

  5. #85
    Stardust.One's Avatar Senior Member
    Join Date
    Feb 2014
    Location
    Crocodile Pit
    Posts
    1,762
    CTD on hardcore... in the midde of a CP-takeover.
    Share this post

  6. #86
    HoHo_Gaming's Avatar Member
    Join Date
    Jun 2017
    Location
    Ontario, Canada
    Posts
    153
    @THE_Crazy_Hyena

    I've been having the same issue. Game crashing about a minute after starting. Works fine afterwards. I'm also using Nvidia, a GTX 1070. Maybe something to do with our older video cards.
    Share this post

  7. #87
    CategoryTheory's Avatar Senior Member
    Join Date
    Feb 2015
    Location
    Tokyo, Japan
    Posts
    675
    I'm using a GTX 970 and have experienced no more than a half dozen crashes to desktop in hundreds of hours of play, only two of which have occurred since I disabled the Ubisoft Connect overlay and used the disable "Use anti-cheat compatibility hook" trick.

    If anything, I'd imagine that older graphics cards would be more reliable simply because their drivers have had much more testing over time and are generally better understood.

    But also remember, two people with the same video card do not necesarily have at all the same system. Amongst any group of users with the same card there are likely to be a dozen different driver versions, a half dozen different versions of the DX11 and DX12 code, different versions and patch levels of Windows, and so on. Fifty different configurations in a hundred different users would not be at all unexpected.

    And also keep in mind that the results of possibly inoccuous-looking mis-usages of libraries (including drivers) and the like may be dramatic. Consider the following C code:

    Code:
    int *p = NULL;    /* pointer to an integer */
    int  i = *p;      /* deference the pointer */
    While a Java or C# programmer might think, "oh, this should throw an exception," this provokes what the C standard calls "undefined behaviour." If that code erases your hard drive or launches missiles and starts a global thermonuclear war, that's perfectly within spec (from a standards point of view) because when a programmer does the above, the system executing the code is allowed to do anything. Testing, however, cannot find all such situations because it's also perfectly acceptable to go on executing everything else normally, maybe just assigning 0 to i.

    Obviously nobody's going to write code that does the above directly, but it's very easy for situations in which undefined behaviour may occur to creep into code. We have good tools to help with this, and most developers (especially triple-A game developers) use them extensively, but it's quite normal for a driver to continue working fine for years with a call that's technically undefined behaviour and then with a new release start exploding in the same case because someone optimized it to get a couple of extra frames per second on some game.
    Share this post

  8. #88
    Licher.Rus's Avatar Senior Member
    Join Date
    Jan 2017
    Location
    Russia
    Posts
    937
    Originally Posted by CategoryTheory Go to original post
    If that code launches nuclear missiles at Russia, that's perfectly fine
    Excuse me?
    Share this post

  9. #89
    CategoryTheory's Avatar Senior Member
    Join Date
    Feb 2015
    Location
    Tokyo, Japan
    Posts
    675
    Originally Posted by Licher.Rus Go to original post
    Excuse me?
    Sorry, I clearly didn't think enough about that phrasing before I wrote that. I've edited the post.

    And I do recognise that the Soviet military was often more cautious with nuclear missiles than the world may always give them credit for.
    Share this post

Page 9 of 9 ◄◄  First ... 789