You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using NavigationAgent3d with NavigationRegion3d, physics tick gradually consumes more and more time.
After about 20 mins of the game running, FPS drops to 1 and the the game crashes.
Steps to reproduce
Open the minimum repro project below.
Run the game and let it run for 5 mins.
Look at the Monitor and notice how physics_process() milliseconds nearly tripled by 5 mins versus the 1st minute, even though nothing is changing in the scene.
There is no cap to this either. If you let the game run for 10 mins, physics milliseconds would increase 6fold.
And so on until you have 1 FPS...
Godot version
4.0 alpha 6
System information
Win10, GLES3, RTX 2070 mobile
Issue description
When using NavigationAgent3d with NavigationRegion3d, physics tick gradually consumes more and more time.
After about 20 mins of the game running, FPS drops to 1 and the the game crashes.
Steps to reproduce
Open the minimum repro project below.
Run the game and let it run for 5 mins.
Look at the Monitor and notice how physics_process() milliseconds nearly tripled by 5 mins versus the 1st minute, even though nothing is changing in the scene.
There is no cap to this either. If you let the game run for 10 mins, physics milliseconds would increase 6fold.
And so on until you have 1 FPS...
Minimal reproduction project
4 navi bug.zip
The text was updated successfully, but these errors were encountered: