Hi everyone,

I recently noticed that my AppData\LocalLow folder was using an unusually large amount of disk space. After checking it with a disk usage analyzer, I found that Broken Arrow had generated almost 12 GB of log files in this folder:

C:\Users\<username>\AppData\LocalLow\SteelBalalaikaStudio\BrokenArrow\

The files were:

Player.log 10.5 GB

Player-prev.log 1.4 GB

I checked the log with PowerShell and found that the following warning was being written repeatedly:

Virtual texturing warning: W1003:

Transcoded a tile but no space was left in GPU cache of type BC3 UNORM

to accommodate it. This probably means that the GPU is too small

for the requested data.

The warning starts appearing around line 808 and seems to repeat continuously, which probably explains why the log reached more than 10 GB.

The game itself was still running, although I have occasionally noticed performance issues. The end of the log also contained Unity allocator statistics, including high ALLOC_GFX_THREAD memory usage, but the repeated W1003 warning appears to be the main cause of the enormous file size.

I have now closed the game and deleted Player.log and Player-prev.log, which immediately recovered almost 12 GB of disk space. However, I am concerned that the files will grow again the next time I play.

Has anyone else encountered this issue?
In particular:

Is this caused by insufficient VRAM, or is it a virtual-texture cache configuration problem?

Does lowering texture quality or render resolution stop the warning?

Is there a known fix from the developers?

Is it safe to use the Unity -nolog launch option as a temporary workaround?

Should I report this through an official bug-reporting channel?

My GPU is: RTX 4060 8GB VRAM
Resolution: 2560x1440
Texture quality: Medium with some high and low combos

I would recommend checking your own Player.log, especially if your system drive has been losing space unexpectedly.