Does this "known bug" still present after the final SC patch mean that for many owners of Sub Command, the campaign itself was unplayable? That the fix posted here or any other was never incorporated in any patch version and essentially ignored? Or does this flaw only occur in rare instances and so not a real concern to fix?
Regardless, thanks for posting this, Juste.
__________________
i7-2700; ASUS P8Z68-V PRO; GeForce 1060Ti; Windows 10; 16 gig RAM; WinWingHOTAS
|