Storm 1-1

I recently got back into the seat of the Su-25A and wondered if JTAC's could guide KH-25 missiles like with a hellfire. It makes getting rid of pesky SHORADS and AAA much easier. So, I set up a mission with a JTAC script and kept getting the same disappointing result. Call in JTAC, acquire target, launch override, launch, missile miss by either self-terminating (as seen in the "Su-25A" video) or by flying into the sky the last few seconds before impact. Tried it in a Su-25T and it worked just fine. If I had to guess what the issue is, it is that when launching laser guided missiles on the Su-25A the laser automatically turns on. This in turn causes the seeker to ignore the JTAC's laser entirely and freak out when the Su-25A breaks contact. Meanwhile on the Su-25T the laser does not automatically turn on causing the Kh-25ML to follow the JTAC's laser. Would there be a way to make it so that launching missiles on the Su-25A does not automatically turn on the laser? The Su-25T does not do it and I do not understand why the "A" variant would either.

I know this problem has been addressed in a different forum before, however the solution was in relation to a virtual machine of which I do not have on my computer. As the title states, when playing DCS my GPU usage drops to zero for a split second before rising back up. The length of time between these drops gets smaller the more units are present in a mission. The only modification I have to my system is a 32gb page file that I did when I first started flying to fix non-GPU related lagging. I really want to get back into multiplayer and the MI-24 but can't if I am taken from the controls every 15 seconds to wait for my GPU to catch up. I know the problem is related to DCS because even when I run Squad at max graphics it holds out at 60 fps and only drops to 30 fps in intense combat. Any help is appreciated. My system; CPU: Intel I5-12600KF GPU: NVIDIA GeForce 3050 1 TB NVME 32 GB of DDR4 RAM (just got upgraded two days ago from 16 GB)