sounds to me like a timing issue. By using the proton log you might slow down to the point the timing issue doesn’t give you problems anymore. Try disabling vsync and enabling a fps limit (warframe has both settings itself).
Another possible cause could be filesystem going to a powersaving mode during normal gameplay and by writing logs you keep the disk in high performance.
It’s quite a bad UX, but generally error 2 from make means the called program resulted into an error.
Usually this is accompanied with another error somewhere up the log. Multiple cores can make this a challenge to scan the log for however, so maybe try compiling without the
-j
argument, that should get the actual error closer to the end.From my experience, it’s usually an outdated config for the kernel (like using a config for 5.1 while compiling 6.7) or a missing dependency. However the real error will be somewhere among the logs, who knows, maybe it’s a missing processor instruction (it’s really bad UX).