Bug: Severe Frame Lag During Extended Korlok Tyrant Weed Fights
This issue
might be a
duplicate of #962 Korlok Lags and Stops Spawning Sprouts After Several Cycles.
Severe Frame Lag During Extended Korlok Tyrant Weed Fights
| Status: | Pending Moderation |
| Priority: |
High |
| Added by: |
|
| Assigned to: |
Unassigned
|
| Due date: | |
| Reported for: |
Steps to Reproduce
- Find a Korlok Tyrant Weed
- Initiate the fight
- Keep killing Sprouts for an extended period of time
- Do not kill the Korlok itself
- Repeat for an extended period of time (at least a dozen of minutes, depending on your CPU capability and/or fighting area)
- After killing enough Sprouts, whenever the Korlok reveals its weak spot, the host will experience a brief stutter
- Keep killing more Sprouts without killing the Korlok itself
- Keep going long enough and the host will start suffering severe frame lag the moment the Korlok reveals its weak spot
- In GPU-Z, the GPU usage drops drastically, whereas the CPU usage increases a bit
- It looks like the lag lasts as long as the game hasn't managed to find where to spawn more Sprouts
- If you keep going even longer, at some point, the Korlok will remain open forever
- I suspect if you damage the Korlok but fail to kill it at this precise moment, it will soft lock
- The reason is: if you inflict too much damage, it closes its weak point, but it hasn't finished computing where to spawn more Sprouts yet
- And as such, the game will keep lagging forever for the host, as it uses CPU power until the mission is over
- Included video shows a Korlok remaining open for more than 1 minute and a half while the game is lagging, because it hasn't found where to spawn Sprouts yet
- The longer the fight lasts, and the further away the Sprouts are spawning from the Korlok, eventually "running out of space"
- Two things can make this worse: a small fighting area, and a weak CPU
Explanation
Korlok Tyrant Weed is causing severe frame lags for the host when the game cannot compute where to spawn more Korlok Sprouts. This is especially troublesome for a fight that lasts too long, and for a host that has a weaker CPU
Full fight video (23 minutes long) with further details in description: https://youtu.be/GqD_QDWxeoc
Watchers
Screenshots
None
Video Clips
Log Files
None
Device
Device information is not visible to you
This project restricts device information visibility.
[ #1 ]
by
Loading comments...
Loading comments...
1 comment loaded
You don't have permission to comment on this issue.