If the issue is the same as MDCCLXXVI's video, I can confirm the exact same issue happening on 5th July (IIRC before 1.48's release), I only have a screenshot to prove it ( http://steamcommunity.com/sharedfiles/filedetails/?id=476038262 ), it started happening short before I had to go and last 2 weeks I haven't played a lot so I probably cannot provide more information.

My system is Windows 10 Pro Insider Preview (impossible to know that moment's compilation because I am on the fast ring), and at that moment I was using AMD Catalyst 15.6 BETA on an HD7970Ghz Ed. GPU, no custom malloc and totally vanilla game (with custom launch parameters such as maxmem=4096, maxvram=3071, exthreads 7, enableht, nologs, nofilepatching, skipintro... ), with the game on SSD...

Sorry for not having provided additional input on this, now I have more time and will do it these near days. The problem persists in the same conditions, will report in singleplayer vanilla conditions soon.

Thanks.

PS: And if you're right about the cause being third-party code, will do what yuo asked and contact the devs.

Hi, I have experienced this issue even on public Wasteland (and Domination) servers in at least BLUFOR and INDEPENDENT sides, without any mods and while being on Quadbikes, Tigris, Gorgon APCs, MBTs (don't remember which) and To-199 Neophrons, and the UAVs being both AR-2 Darters and Greyhawks (haven't tried UGVs but I suspect it's the same).

I have also experienced it while using mods (a lot of them in fact), but as I said it happens even without them. I use Arma 2 controls but friends that use A3 ones also had the problem. Will test deeper, hope anything I said could help meanwhile.

Thanks for fast response.

Edited on 17th June for a small really unimportant typo (200m instead of 2000m), just in case.