Hi,
in this kind of problems, measuring is king. Assuming things and blindly tweaking parameters will lead you to a different experience but it is not certain it will be better or sustainable.
The thing with wifi is, that it works, because it slows down until it works. The condition in which it must work is very variable and hostile to its working. That hostility can be measured to some extend. Assuming the condition is clear is very dangerous. It also varies with time. Busier wifi spectrum in the evening is very normal. It has many consequences: you share your bandwidth with others and there is more interference that make you wait or disturbs your communication (lower CCQ).
There a few steps everyone should make, certainly with Mikrotik. You probably know and do most of them. (Sorry for bringing obvious things)
1. Scan your environment. There are 3 usefull tools in the Mikrotik. Besides the SCAN function that searches for other APs by listening for beacons. There is also "Freq Usage" that will detect all freq usage, also for non 802.11 wifi. And "Snooper" will listen for all wifi transmitters, including non-AP transmitters like clients.
(There is one some devices also the terminal CLI line : "/interface wireless spectral-scan")
Point is to understand the current usage in the spectrum, and to find a free band of 20MHz wide. 20 MHz is 4 channels wide, and so only channel 1, 6 or 11 should be used. But (2,3) will distrurb channel 1, (4,5,7,8) will disturb channel 6, and (9,10,12,13) will disturb channel 11.
Find your best channel. Don't skip this measuring step. And decide on the channel to use.
2. Do NOT use auto channel select. And do not use 40 MHz bandwidth unless there is clearly free space in the measurements. Your LDF will wait for everything that is above -96dBm. Actually that is everything that Snooper sees. Set your channel center frequency manually (2412, 2437 or 2462) at the AP side.
3. Check what you get in the "registration" tab of the wireless table. Watch how: "TX/RX Signal strength, SIgnal to Noise dB, TX/RX CCQ, TX rate, RX rate , P Throughput" vary over time. TX rate and RX rate give the inferface speed like 130Mbps/20MHz/2S/SGI. (Dual stream 20MHz and Short Guard). Convert the speed to the MCS used with known tables like
http://mcsindex.com/ . We are here at MCS6 (high end of the range). The quality of the connection is seen with the ratio of "TX/RX frames" over "TX/RX HW frames", as the HW includes the retransmits. This in converted in CCQ and P throughput (which is averaged over time).
4. Depending on what is seen in 3 , some tweaks can be taken. No general rules here, and no copy/paste from another known good tweak in a setup in another location or direction. E.G. just one exemple, dropping to CCQ 50% shows a disturbed communication. The first step should have learned who the possible root cause candidates are. But maybe it is just your own setup like obstructions in the fresnel zone of the antenna beam. Mikrotik can be tuned a little bit to perform better in difficult conditions. Like limiting the highest MCS to be used (do NOT remove the lower here), setting HW_retry to a lower value to make the drop to lower MCS faster, or set hw_retry higher if higher retransmits allow to stay in that higher MCS, reducing the A-MSDU size from the default 8192 to 2048 will help in reducing the retransmit volume, setting hardware protection mode, adaptive noise immunity, TX poxer reduction by using a higher antenna gain setting ,....... All these tweaks can make it somewhat better, or can make it much worse. So change only one at a time, and check again step 3 (even step 1 to verify conditions have not changed in the mean while, also setting the original back and checking again helps to estimate the correlation between the tweak and the outcome). To know what to tweak to do first is based on the observation in step 1 and step 3, and the correlation you get with the (improved or reduced) working.
Disable the "station roaming" in the station side WLAN setting. Because enabling it will cause to reconsider the link to that far away AP, and might drop the connection while scanning for other AP's. (At least that's what it did in my setup). But if there is only 1 AP to connect to, don't bother to reconsider the association every x minutes (x depending on the signal strength of quality))
5. NV2 and Nstreme will lead you away from those 802.11 AP's and clients. They will not see NV2 or Nstreme. So they will not even wait for it. They will treat it just as non-wifi noise, and they will be noise to NV2 and Nstreme. The way I do this is to set the "station-bridge" to "any" protocol, and prepare all settings. The AP can then just switch between 802.11, nstreme and NV2. The client will automatically reconnect with the proper protocol. Stability with NV2 for my setups (! my setups!) gives more stability but is slower than 802.11ac. So I leave it on 802.11ac but can switch remotely over internet if there would be some need. (I'm 1200 km away from the setups, and border crossing travel is forbidden in corona times)