Remove all ads & support the site - Go PurePremium!

Diablo 2 Resurrected AVX issue identified – Possible fix incoming

Diablo 2 Resurrected AVX issue identified

An update from Blizzard this evening regarding the Diablo 2 Resurrected AVX issues shines some light on the problems. It boils down to a change made in the release version compared to the beta.

I’m not sure how many players this may have impacted but considering not having AVX is below the minimum spec, there surely can’t be too many in the big scheme of things. Here’s what Blizzard has to say on the matter and the plan to sort it.

We wanted to provide an update on the Advanced Vector Extension (AVX) items from the dev team after some further developments from this past weekend. The team believes they have a potential fix, but this goes beyond just AVX specifically. The fix could potentially affect all users, even those outside of not having AVX support, so we are wanting to make sure we do proper testing.

While CPUs without AVX are below our minimum spec, we want to try to ensure as many people as possible can play. Setups without AVX were working in Beta. In optimizing the game, we inadvertently included the need for AVX for launch. QA is going to spend another few days of testing across all of these scenarios and setups in an effort to ensure we are not impacting existing players.

We will update this thread once we have an update from the testing over the next few days.

We apologize for the added delay and appreciate your patience.

For those that may have already purchased but would prefer to purchase post fix, we do recommend reaching out to Customer Service for a refund.

1 thought on “Diablo 2 Resurrected AVX issue identified – Possible fix incoming”

    An exception occurred: [ErrorException] [E_WARNING] call_user_func() expects parameter 1 to be a valid callback, function 'better_comments' not found or invalid function name in /var/www/vhosts/purediablo.com/httpdocs/wp-includes/class-walker-comment.php on line 184

    1. XF::handlePhpError() in /var/www/vhosts/purediablo.com/httpdocs/wp-includes/class-walker-comment.php at line 184
    2. Walker_Comment->start_el() in /var/www/vhosts/purediablo.com/httpdocs/wp-includes/class-wp-walker.php at line 146
    3. Walker->display_element() in /var/www/vhosts/purediablo.com/httpdocs/wp-includes/class-walker-comment.php at line 139
    4. Walker_Comment->display_element() in /var/www/vhosts/purediablo.com/httpdocs/wp-includes/class-wp-walker.php at line 389
    5. Walker->paged_walk() in /var/www/vhosts/purediablo.com/httpdocs/wp-includes/comment-template.php at line 2252
    6. wp_list_comments() in /var/www/vhosts/purediablo.com/httpdocs/wp-content/themes/generatepress_child/comments.php at line 105
    7. require() in /var/www/vhosts/purediablo.com/httpdocs/wp-includes/comment-template.php at line 1556
    8. comments_template() in /var/www/vhosts/purediablo.com/httpdocs/wp-content/themes/generatepress/inc/structure/comments.php at line 213
    9. generate_do_comments_template() in /var/www/vhosts/purediablo.com/httpdocs/wp-includes/class-wp-hook.php at line 307
    10. WP_Hook->apply_filters() in /var/www/vhosts/purediablo.com/httpdocs/wp-includes/class-wp-hook.php at line 331
    11. WP_Hook->do_action() in /var/www/vhosts/purediablo.com/httpdocs/wp-includes/plugin.php at line 476
    12. do_action() in /var/www/vhosts/purediablo.com/httpdocs/wp-content/themes/generatepress/inc/theme-functions.php at line 594
    13. generate_do_template_part() in /var/www/vhosts/purediablo.com/httpdocs/wp-content/themes/generatepress/single.php at line 29
    14. include() in /var/www/vhosts/purediablo.com/httpdocs/wp-includes/template-loader.php at line 106
    15. require_once() in /var/www/vhosts/purediablo.com/httpdocs/wp-blog-header.php at line 19
    16. require() in /var/www/vhosts/purediablo.com/httpdocs/index.php at line 17