#Anyway to Fix Stuttering
1 messages · Page 1 of 1 (latest)
So I was doing some testing, and I noticed when I was in my Windows Graphic Settings, it had 2 entries for Coral Island, one for a regular one and one for a ProjectCoral-Win64-Shipping.exe file. When playing the game with the Steam Shortcut, it shows both of those exes in the File Manager. They are both running in the Details tab, but if you run just one of those files by themselves, only one runs and the stutter is pretty much gone. If you run the Steam Shortcut, it has a ton of stutter
Here are instructions how to locate the issue while the devs are trying to fix on their end:
- Go the search bar on your PC and search "Graphics Settings". In the new opened window try and locate apps with coral island icons. They will probably be called "Coral Island" and "BootstrapPackagedGame".
- If you click on either of them you can see where each is located. And "BootstrapPackagedGame" is the shortcut used to run the game and is supposedly slows it down.
There are two options how to deal with this:
- If you run the game with the shortcut, each time you open the game open task manager (press Ctrl+Shift+Escape) and find "BootstrapPackagedGame" task and then close it.
- Or go to the location listed in "Graphics Settings" - "Coral Island" and make a new shortcut and open game with it.
@zenith cypress
Hi folks! May I ask something about the stuttering issue.
Can you set the render scale to 100 and see if it helps with the stuttering? Or is the stutter still happened even when the render scale is 100?
Hi. I think the question would be better answered in the similar bug report https://discord.com/channels/623097219628662784/1274549616947363861
I think stuttering occurs because of the high memory leakage. And is the game supposed to have two processes running in the task manager while playing?
Aha yes! My coworker Rachma is also checking the thread and also collecting info there!
Just checking to see if render scale also affecting y'all cause we have a stuttering issue, and it was fixed by changing the render scale from 200 to 100