With the release of Update 2.1.1, we've observed the reappearance of several bugs that had been resolved in previous patches. We are actively tracking these regressions to confirm the scope of change and begin implementing fixes into future updates.
Here’s a rundown of the regressions that we currently have confirmed for fixes coming in Update 2.2:
- Game Crashes During Streaming - Attempting to stream Hunt may result in crashes, interrupting your broadcast experience.
- Party Disbanding After Matches - Staying in a party after a mission does not work always as intended, this will now be resolved.
- Texture Loading Issues - Various objects, Hunters, and items at times fails to load properly, leaving grey placeholder textures visible.
- Invisible Weapons - The issue of weapons becoming invisible has reappeared, likely tied to the texture-loading problem above.
- Crashes During Gameplay - Some players experience game crashes or freezes during pivotal moments, including gunfights. These are caused by several issues, but we have identified multiple stability related fixes that will be implemented 2.2. We will be monitoring this closely on roll out to identify any remaining triggers.
- Extended Loading and Reconnection Times – For some players, starting Hunt now takes significantly longer. Various factors may affect this including player region, internet connection etc, but we are able to implement a fix that should result in faster loading times for most players.
- Ground Level Glitch - Reconnecting after disconnections leaves players stuck viewing untextured ground layers.
- Alt-Tab Cursor Bug - Mouse cursor remains permanently visible during a match after alt-tabbing.
- Hex Breaker’s Cloak - The texture of Hex Breaker's cloak at times appears corrupted
- Shadow Exploit - Resolved an issue that allowed shadows to be disabled through an exploit
- Wet Explosives - Fused explosives (such as the Frag Bomb) would still explode after tumbling into water upon hitting the ground
Update 2.2 comes with a ton of bug fixes already, and we’re confident this line up of fixes will improve the overall gameplay experience for many players. However, we are continuing to monitor for any additional regressions from 2.1.1 and will work to include as many more as possible to resolve these recently reintroduced issues.
Performance Drops & VRAM
We also identified some performance related issues regressions with the 2.1.1 rollout. Most notably:
- System Performance Slowdown When Running Hunt - Some players report that launching Hunt causes their PC to experience significant slowdowns, overloading their GPU.
- Overall Performance Degradation - Reports indicate a drop in average FPS across various configurations, affecting gameplay smoothness and responsiveness.
We are tackling these issues by improving the way Hunt manages video memory. In certain situations, the game exceeds the allocated memory budget permitted by the operating system, causing a noticeable performance penalty.
For Update 2.2, we’ve implemented a fix that resolves this issue in scenarios where the game is the primary application running on your system. This means that if your machine is running demanding software in the background, you may still run into issues.
Performance remains a top priority for us, and we are continuously monitoring and striving to enhance it. We are actively tracking additional edge cases that could contribute to performance degradation and are already working on targeted fixes to address them. A few follow-up fixes are in the pipeline already, which will be ready in time for the upcoming releases.
In the meantime, if you continue to experience performance drops, we recommend the following steps:
- Close GPU-Intensive Applications: Ensure no other graphics-heavy applications (e.g., video editing software, digital content creation tools like Maya or ZBrush, or web browsers running graphics-intensive websites) are running in the background. If these applications are necessary, open them before starting the game, not during gameplay.
- Adjust VRAM Usage Settings: In the settings menu, lower your VRAM usage target. While the default setting of 80 works for most systems, reducing it to 70 may help mitigate performance drops on affected machines.
Our Next Steps
The team is thoroughly investigating the extent of these regressions and are working towards implementing verified fixes as soon as possible. Some fixes are already in testing phase for roll out with Update 2.2.
Please continue to share your experiences via our social channels or community forums. Your input helps us prioritize fixes and ensure a smoother experience for everyone.
Thank you for your patience and support.
