- Sonic -

wait...but in AA mode using ATP you can engage enemy aso with AIM120/AIM9 using only the pod?

Thanks to MBucchia!

Absolutely in favor. This is a solid and well-thought-out proposal that would bring real improvements to gameplay, especially in terms of communication efficiency and realism. Adding integrated radios to Tactical Command, Game Master, and JTAC roles—following the FC4 model—is a smart move. It eliminates the need for external tools like SRS and streamlines coordination with air assets. Including three configurable radios covering AM/FM/VHF/UHF is a practical and flexible solution. Extending functionality to the F10 map, with command units or repeaters to simulate signal coverage, is a great way to give currently underused vehicles a meaningful role. The fallback option of full map coverage for simplicity makes sense for initial implementation. The suggestion to link radio behavior in first-person vehicle use to realistic NATO and USSR radio types is a nice touch, adding immersion without overcomplicating things. Overall, this would make Combined Arms more appealing and functional. Fully support the idea—hope to see it implemented soon.

After updating DCS and optimizing settings, the CPU load improved, but the last core still hits 100%, causing occasional CPU-bound warnings. However, DCS runs smoothly without stuttering, while the GPU has room for more load.

After updating DCS to the latest version, removing the "Run as Admin" flag, and adjusting some settings to reduce CPU load, things seem to be improving. On an online server (up to 30 players), stuttering has disappeared (though I need to test more thoroughly). All cores are running well. The internal DCS Frame Rate Counter (locked at 120, as I use a 120Hz G-Sync monitor, 32") sometimes turns red, indicating a CPU bottleneck. The last core appears to be running significantly higher than the others (100%). The GPU is running at 70%, so I assume I could push it further with different settings. I don’t think I can optimize much more—while the RTX 2080 Super has some headroom, the CPU (i5-9600K) seems to be the bottleneck. Maybe I can offload more from the CPU and shift more load to the GPU, but I need suggestions for additional settings

mmm interesting...I will update Dcs and remove admin from start DCS MT

I've to check with new update; tested with version before last after change pagefile (min32-max64). Well, freeze remain a issue. May could be a USB device (I want to change my rudder port, back port of motherboard have issue) and I have to test. Maybe could be AITrack issue? I use a cheap webcam and could be intensive with CPU. I've register the running of session, and how you can se CPU decrease in the same spot ok a freeze: all cores running at 100% and GPU ad 90%...this mean bottleneck (and freeze) I suppose

Hi, I also made this upgrade. I studied a bit, but I can say that in the end, trying and trying again, the result is excellent. I can only recommend these things: 1. be careful to choose the hall sensor compatible with the system (whether it is analog or linear, supply voltage, etc.) 2. be careful with the wiring: the hall sensor has the GND and VOUT inverted compared to how a CTS251B15F104B6NB potentiometer is structured In my specific case, I made the modification partly as an experiment and partly because the potentiometer was starting to have some gaps in the axis reading at the beginning of the throttle (after a bit of forward movement, the reading began). After a couple of attempts (due to what was said above) I also succeeded in the undertaking with excellent results. I used: • Allegro 1324 hall sensors (linear) • 2.54mm 3-pin JST cables • 5*5*5mm cubic N52 magnets • 3D printed support (I attach the STL file) • N52 magnet orientation As I mentioned, the potentiometer (and how it is read by the throttle board) are organized as VCC-VOUT-GND, while the hall sensor is structured as VCC-GND-VOUT. I'll recap with this connection diagram: nullnull So (in addition to being careful with the standard colors that change), the GND and VCC are inverted. For the rest I printed a 3D support that contains the sensor and fits into the metal support of the old potentiometer; to solder I used a simple soldering iron (I put the corresponding sensor and on a paper tape, then I soldered with simple points), covered the solder with heat shrink and placed everything in the support. I glued the magnet in the support for the axis, be careful with the orientation: Then I connected, tested and calibrated and to my great surprise everything works well! The necessary (what is necessary to make 3 new sensors) paid (with shipping) a little less than € 15 from Aliexpress. Two small suggestions: • the STL file may not be perfect; I myself had to file the printed object to make it fit correctly in its seat. • The 3-pin 2.54mm JST connector that I took is different from the one on the peripheral PCB: I also solved this problem by filing some parts to make it fit correctly STL Preview (file attached) the sensor housing has a snap-on cover that you put on top (you can also glue it on if empty); the housing for the magnet has a space in the wide part at the bottom (not visible here) to house the 5*5*5 mm N52 magnet. Use glue to secure the magnet in the housing: braket_hall_sensor_tqs_cougar_V3.stl

ok I will try to increase it (I remembre something about this)...in meanwhile I found a .lua file in script about Tacview; I've disinstalled it (I remember also that it give load problems), but this script remain...maybe it could be the problem also.

I have similar problems too: I think they appeared after installing Tacview (immediately uninstalled with Revo Unistaller), but in any case the stutters so massive that they prevented the game or even froze during server loading. I inserted exclusions to the DCS folders in Windows Defender (which I then disabled) but I only had a partial improvement. There are still heavy stutters/freeze in the game. I downloaded the DCS log and analyzing it with ChatGPT a few problems came out, including the suggestion to empty the DCS cache (fxo and metashaders folder in Saved Games\DCS). I also generated a log on Process Lasso and it shows a lowering of the priority of aitrack.exe (perhaps due to Process Lasso, which I never use but I only used to see how it went) and a strong presence of GIGABYTE AORUS ENGINE (which I don't think is good for the PC in general at this point). what do you recommend I do? via I attach the logs dcs_log.log log_lasso.CSV

no per Steam VR serve sempre WMR

Ciao a tutti. Sapete se esiste un modo che non sia il rolback al 23H2 di Win11 per usare il Reverb G2? Ho letto parecchio e a quanto pare non esiste nulla si "sostitutivo" in questo senso.

Hi I suppose that head position (and for head i mean the natural Eyes posiotion) is al little back in the neck: When I look down, I can look inside the neck; IRL if I look full down i an look my chest. I suppose because the eyes poision it attached to Longitudinal Axis maybe. How I can move it a little forward and save the posiotion?

the parts could be done also in metal?

se non sbaglio il paghi al corriere che te la consegna; all'atto dello sdoganamento la Dogana elabora il conteggio e poi il corriere (Poste, DHL, etc) alla consegna deve riscoutere il dazio doganale (o in contrassegno o online credo avvisando prima).

can you considered shipping to EU?

@rel4yI want to buy from you some items. I drop you a mail. let me know tks

thank you rel4y; actually I'm trying to repair my broken roll gimbal of cougar (i suppose you have nothing for this) but after this I think to replace all pots and give to throttle a usb adapter.

hi...you still product items?

my roll gimbal just left me. I have to try it tks!

hi dude! my gimbal is just broked...may I buy the whole pack (also with hardware) to replace it?

Hi! my cougar gimbal just left me Can you sell me you original TM gimbals?

Hi to all I'm a pround owner and user of Hotas Cougar. Time and use, however, mean that it requires maintenance, specially on parts like brake pad and bearings that produce the sticktion. Firts of all, I change the grease with an NLGI 3 grease (silicon synth based) available in europe (Nyogel 767a is hard to find with high cost); I suggest OKS 1110, a product Made in Germany and easy available in EU. But despite the greasing, sticktion continue. The issue was the bearings; those two rings, plastic on plastic, are a worse choiste for hold a moving axis. Following a online old tutorial about it (cougarfoxy) I've applied tu small picese of alufoil between bearing and axis, putting some OKS 1110 grease also. Same trick on friction pad: little alufoil on pad and a glossy tape on axis, also with grease in the middle. Result a smooth throttle, but I wuold change glossy tape with ptfe tape in future. By the way, my question is the following: the bearing are a very weak and cheap part of this throttle; possible that no-one produce an aftermarket compatible bearing? I find on web a lot of slim/thin bearing (also with carbon). Bearings mod is also a thing you can do in other product, like TWCS. Anyone know if can do similar mod on Cougar of have data information for try this experiment?

then if you suffer a tank wing hit the plane is gone?

yes I read about it, but I want to know if the switch (in the real world) can save fuel shutting of section of tanks