# Game still crashes when activating ultimate gems

**URL:** <https://community.puzzlequest3.com/t/game-still-crashes-when-activating-ultimate-gems/4861>\
**Category:** Bug Reports\
**Created:** [July 9, 2024, 9:03pm UTC](https://community.puzzlequest3.com/t/game-still-crashes-when-activating-ultimate-gems/4861 "2024-07-09T21:03:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kushcloudz1clips](https://sea1.discourse-cdn.com/flex019/user_avatar/community.puzzlequest3.com/kushcloudz1clips/32/6113_2.png) [@Kushcloudz1clips](https://community.puzzlequest3.com/u/Kushcloudz1clips)\
**Post date:** [July 9, 2024, 9:03pm UTC](https://community.puzzlequest3.com/t/game-still-crashes-when-activating-ultimate-gems/4861/1 "2024-07-09T21:03:02Z")

</div>

This was supposedly fixed but suprise suprise it was not!!! Im Still frequently crashing when activating mercenary treasure gems and necro death gems this is absurd. Im getting extremely frusterated co op still dont work right, longer load times than elden ring and so poorly optimized. P.S. I STILL CANT SEE WHAT SPELL PAGES I GET FROM QUEST PASS

---

<div class="post-metadata">

**Author:** ![Jeto](https://sea1.discourse-cdn.com/flex019/user_avatar/community.puzzlequest3.com/jeto/32/6326_2.png) [@Jeto](https://community.puzzlequest3.com/u/Jeto)\
**Post date:** [July 9, 2024, 10:19pm UTC](https://community.puzzlequest3.com/t/game-still-crashes-when-activating-ultimate-gems/4861/2 "2024-07-09T22:19:27Z")

</div>

Can you attach a new video of this occurring, so we can check what has caused this issue to reappear?

As for the Quest passes, this is still [a known issue](https://puzzlequest3.zendesk.com/hc/en-us/articles/10017403613839-Quest-Pass-Spell-Page-collection-animation-missing) and as mentioned in your thread, it will be fixed in 3.2

> [@\[Fixed in 3.2 - visual issue\] Collected Quest pass spell pages and got nothing](https://community.puzzlequest3.com/t/fixed-in-3-2-visual-issue-collected-quest-pass-spell-pages-and-got-nothing/4801/10):
>
> It will be fixed in 3.2 at the earliest as it requires a client fix
