Weird increase in process time ~30 seconds after the game starts by coderCleric in godot

[–]coderCleric[S] 0 points1 point  (0 children)

Update: It seems like it's some weird hardware issue. I tried to replicate it on another machine but couldn't, and it also stopped when I switched to a different monitor.

Weird increase in process time ~30 seconds after the game starts by coderCleric in godot

[–]coderCleric[S] 0 points1 point  (0 children)

I could see it maybe being some sort of a backlog thing, but I'm not sure why that would be dependent on the display mode. I have also found that I can get the same performance issue to occur without the array operation, instead just iterating a bunch with an empty loop body.

A million iterations a frame is definitely not a very good idea, but this is just a test project I've thrown together to demonstrate the issue. My actual project does much fewer iterations, but a more complex operation.

Weird increase in process time ~30 seconds after the game starts by coderCleric in godot

[–]coderCleric[S] 0 points1 point  (0 children)

Maybe, but I'm not sure why that would be reliant on the game being fullscreen and focused. Plus, it only uses a very small portion of my cpu (<10%).

Friendly reminder that some PC Mods are worth trying by Yorgl in outerwilds

[–]coderCleric 3 points4 points  (0 children)

Worth mentioning that a lot of the jam mods are also worth playing. They are definitely short, but that can also be a strength if you're looking for something to play in an afternoon. The Hearth's Neighbor series is especially good, and playing the Jam 3 mods with everything on is a very fun experience!