Jump to content

Recommended Posts

Posted

It's a known 1.5 bug, happening when visibility range is set to anything below "high". Apparently fixed already in internal developer version.

i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...