sed1917

Had to uninstall as when I use this I get regular lag spikes, dropping from 60 to 30 fps, every 2 seconds. Went through mods comprehensively and narrowed it down to this.

Hello, yes, still having this issue. What mods did you disable, @Sinda?

I have tried getting more info from the logs, using /debug logticks 60, but there doesn't seem to be an obvious pattern to what is causing the 1000+ ticks.

Some examples:

• gmleVintagestory.GameContent.EntityPartitioning: 1708.44ms
• entity-done-bh-controlledentityphysics: 1589.05ms
• entity-done-bh-repulseagents: 4868.37ms
• ss-tick-Vintagestory.Server.ServerSystemLoadAndSaveGame: 1681.39ms
• entity-done-bh-harvestable: 1759.23ms

Hi, thanks for the reply. On, off, on + sleep, off in game but on in Nvidia Control Panel, etc. No difference regardless I'm afraid.

I tried upgrading to 1.17.3, and whatever I do, I get constant fps spikes like this:

It doesn't matter if I update to 1.17.3, or uninstall and install from scratch. It doesn't matter if it is on a new world or existing one, with mods or without. When I switch back to 1.16.5, everything works fine. I updated my Nvidia 2060 RTX to the latest drivers, no difference. Checked all performance issues, nothing is under stress. Checked logs, nothing seems to be happening.
 

For now I'll stick to 1.16.5, but thought I would mention this problem as can't seem to find much information about it anywhere.

So, I managed to capture the message that pops up for a second. "Host not responding. Possible causes: Server overloaded or crashed". From my investigation I can see in the server-main.txt that these drops coincide with this message: "[Warning] Server overloaded. A tick took 6522ms to complete.".

This is a singleplayer world so I'm not sure what server is being overloaded. I feel like this may in some way be connected to autosaving, but I'm not sure how.

Any further advice would be appreciated.

2 hours ago, Tyron said:

You could also look into the task manager if anything consumes all of your cpu time during that freeze.

Thank you for your suggestion, I will try that. I just actually noticed that when it happens, for a split-second after the freeze a message box pops up in the top right corner, but I so far have not been able to get a screenshot of it. I will perhaps try screen recording and see if I can capture it.

Phenomenal game by the way @Tyron, my favourite in a long time! A real work of art!

1 hour ago, Streetwind said:

Profile your system RAM and video card VRAM. Smooth FPS with occasional hard stutters can be a symptom of memory filling up and then getting cleared out in one big chunk as an emergency measure. If you see this pattern in the graphs - gradual rise, then abrupt reductions, repeating - then that's a good indicator.

The main driver for VRAM consumption in Vintage Story is view distance. To save on system memory, there are optimization options in the settings menu.

A system with good specs should not have issues with either, normally, but because your description of the issue sounds so much like it, do check it anyway.

Thanks for your suggestion. but I don't think it's a RAM issue tbh. I have 16GB RAM and 6GB VRAM. The graph doesn't gradually rise, it stays around the 100-140 range and then just has one huge spike to 0 every so often. I have also tried adjusting view distance and it has not had any effect.

2 hours ago, l33tmaan said:

Do you use mods?

I do, and have tried removing them in batches and testing, seeing if I could narrow it down, but no luck so far. Obviously I could do them all, one by one, but was just wondering if there was a quicker way using the logs.

Mod does not function at the moment, crashes to desktop when trying to use a book, no recipe for book, etc.

Frequently my game will drop to 0 fps, causing it to freeze for 1-2 seconds. My specs are good, I get 100-140fps most of the time, I'm not overheating etc. I have tried using the logs to identify the issue, but so far have not discovered anything. Could anyone assist with how to possibly diagnose what is causing this? Would the logs tell me? Using the debug overlay tells me that when it happens my draw calls shoot up into the 400-900s, but I'm unsure what that means.

Thanks in advance.