Huge amount of errors showing up on error.log

[Xico26]

Hey all!

I was playing Victoria 3 vanilla with debug mode and I realised the number of errors didn't stop growing, reaching over 10k in less than 2 minutes. Despite this, the game did not crash.
When I check the error1.log file, I saw that over 10k lines were filled with only these two things:
[gfx_vk_swapchain.cpp:343]: Suboptimal
[gfx_vk_swapchain.cpp:407]: Suboptimal

Does anyone have any idea on what could be causing this? I'm on the latest Vic3 patch and I verified the game files using steam.

System Config:

CPU: AMD Ryzen 5 3500X
GPU: AMD Radeon RX6700XT
RAM: 16GB
OS: Fedora Linux 37 (using KDE and XOrg)

 

[Oglesby]

It is what ever is on lines 303 and 407 in the source file gfx_vk_swapchain.cpp. It is doing something that is deemed Suboptimal

Edit: checked into it more after my response

Might not exactly be this but this possible responses when determining the validity of a swap chain (which is used by the graphics API)

ERROR_OUT_OF_DATE: The swap chain has become incompatible with the surface and can no longer be used for rendering. Usually happens after a window resize.
SUBOPTIMAL: The swap chain can still be used to successfully present to the surface, but the surface properties are no longer matched exactly.

 

[Xico26]

It is what ever is on lines 303 and 407 in the source file gfx_vk_swapchain.cpp. It is doing something that is deemed Suboptimal

Edit: checked into it more after my response

Might not exactly be this but this possible responses when determining the validity of a swap chain (which is used by the graphics API)

ERROR_OUT_OF_DATE: The swap chain has become incompatible with the surface and can no longer be used for rendering. Usually happens after a window resize.
SUBOPTIMAL: The swap chain can still be used to successfully present to the surface, but the surface properties are no longer matched exactly.

Thanks for the answer! I assume I can't do anything about it, right?

I also added my system config to the original post, hopefully it is useful.

 

[Oglesby]

Thanks for the answer! I assume I can't do anything about it, right?

I also added my system config to the original post, hopefully it is useful.

That is my understanding.

It is just a validity check on an existing swap chain (something used in the graphics portion of the game) to determine if it needs to be recreated/adjusted before being used.

 

[Xico26]

That is my understanding.

It is just a validity check on an existing swap chain (something used in the graphics portion of the game) to determine if it needs to be recreated/adjusted before being used.

Thanks for the answer.

Would that explain the fact that the in-game error counter (the deer in debug mode) goes up like crazy? It gets like 1000 error in less than 10 seconds

 

[Alxe]

The same happened to me when playing on the Steam Deck, with similar specs to yours (amd chips, Linux)

 

[Xico26]

The same happened to me when playing on the Steam Deck, with similar specs to yours (amd chips, Linux)

That's interesting... We're you using XOrg or Wayland? I was on Xorg but switched to Wayland since I was having some issues with EU4, but I haven't tried Victoria 3 again.

 

[Alxe]

That's interesting... We're you using XOrg or Wayland? I was on Xorg but switched to Wayland since I was having some issues with EU4, but I haven't tried Victoria 3 again.

I don't know the specifics at the moment, but I'm guessing it's X. I can double check later.

Nonetheless, if this has to do with Vulkan, I don't think Wayland or not is a culprit here.

 

[Xico26]

I don't know the specifics at the moment, but I'm guessing it's X. I can double check later.

Nonetheless, if this has to do with Vulkan, I don't think Wayland or not is a culprit here.

Well apparently XOrg is really the one to blame here. I switched to Wayland and the error counter is stuck at 73, and that error isn't showing up!