Bug: Heavy FPS Drop/Spikes with Korlok Tyrant-Weed in Restricted Spaces
Heavy FPS Drop/Spikes with Korlok Tyrant-Weed in Restricted Spaces
| Status: | Pending Moderation |
| Priority: |
High |
| Added by: |
|
| Assigned to: |
Unassigned
|
| Due date: | |
| Reported for: |
Steps to Reproduce
- Start a sandbox room with mod
- Spawn Korlok Tyrant-Weed in the room
- Kill the Sprouts and let Korlok open its heart
- Observe that there are no major frametime spikes in the open room
- Spawn Korlok Tyrant-Weed again in the same room
- Place one enlarged platform above Korlok, with its size multiplier set to 144, blocking most of the available space
- Kill the existing Sprouts
- When Korlok tries to open its heart and respawn Sprouts/Healing Pods, heavy frametime spikes occur
Explanation
Korlok Tyrant-Weed causes heavy FPS Drop/FPS spikes when there is not enough valid space around it to spawn or respawn Sprouts/Healing Pods.
I reproduced this in a sandbox room using mods only to create controlled test conditions and spawn Korlok. In a normal open room, Korlok works normally and opening the heart does not cause frametime spikes. But when I block most of the available space around Korlok with platform, then kill the existing Sprouts, the game starts producing heavy frametime spikes when Korlok tries to open its heart and respawn plants.
The same type of FPS issue has also been observed in normal missions, although it is very rare there. When it does occur, it almost always persists until the Korlok is killed. The video demonstrates a relatively mild version of the issue that can occur in normal gameplay, while the screenshots show the same problem occurring inside a normal mission in a much more severe form, with substantially larger frametime spikes visible on the frametime graph. In some cases the effect can be even worse, causing direct FPS drops instead of the typical sawtooth frametime pattern.
Watchers
Screenshots
Video Clips
Log Files
None
Device
Device information is not visible to you
This project restricts device information visibility.You don't have permission to comment on this issue.