BIGNEWY

Patch notes discussion May 2025 Release Version Current version number: DCS 2.9.15.9599 Next planned update: 5th May 2025 Campaigns update only

Last warning for this thread, we have been pretty lenient here with the rules. Keep it to the thread topic and to DCS. thank you

Hi, The VSD/Gauge speed discrepancy and the bugs not moving is reported, but the green tape was removed previously due to a documentation refinement. So that's working as intended but the manual will be reviewed in the future. thank you for your report.

This has been reported to the team. thank you

this has been reported to the team thank you

Hi we have been getting reports of scripts causing HTS problems by interfering with the spawning and despawning of units, please check which scripts are being used in the mission, if you have a shorter track that would be the best way for us to look at it. Longer tracks with a heavily scripted server can cause problems for debug.

this has been reported but is a low priority currently. thank you

this has been reported to the team thank you

topic moved to hardware

Hello please remove any unofficial mods and run a repair. Delete metashader2 and fxo folders in saved games dcs and restart dcs attach your dcs log from saved games dcs log folder it might have some clues.

Folks I get there is a lot of conjecture out there, lots of misinformation from various source's after RAZBAM went public. But please understand we can not discuss it in public, to do so would be unprofessional and breach our NDA's. We continue to wait for a resolution, however long that takes. Thank you

As mentioned previously we have tested and we are not seeing the issue. We have already tweaked this and the values are correct. thank you

To clarify the ARC-222 is correct for our viper for the year we are simulating (F-16CM Block 50, roughly M4.2+, operated by the United States Air Force and Air National Guard circa 2007). The ARC-210 was being acquired and introduced but was more common later than the viper we are simulating.

Hi, we will ask the team about this. thank you

Hi, please take a look at page 244 in our manual it goes over the radios being used in DCS: F-16C Viper which is based on the United States F-16CM Block 50, roughly M4.2+, which operated in the 2007 timeframe. If you have evidence it is wrong for our block and year please PM me with evidence. thank you

Good to hear, enjoy!

make sure the cable from the monitor is plugged into the graphics card and not the motherboard. Check the caps lock key on your keyboard also, seems to be sticking

Hi darkman we are investigating this. A reminder to others please do not derail bug reports threads, keep it for the actual issue being reported. thank you

Hi, please give us some clues. Attach your dcs log and dxdiag we can try to assist you thanks

Hi, welcome to the forum, I have moved your post to a more appropriate area, Can you show a screenshot of the issue? You may want to remove your unofficial mods and run a slow repair of dcs thank you

Glad you have it worked out, enjoy!

Can you confirm that you have bound both triggers? The Weapons trigger on the left handgrip (LHG) and the LRFD trigger (Laser Rangefinder/Designator) on the right handgrip (RHG)? We only ask this to ensure there wasn't any confusion that there are two triggers on the TEDAC grips and each have two detents, but the left trigger only fires weapons and the right trigger only fires the laser.

Thanks, when I take control of the track all seems ok, are you sure your key bindings are correct?

the wind issue is reported but we are waiting for free dev time, at the moment the team is very busy. thank you

Hi, if possible can you make a track that does not include unofficial mods, I am unable to check the track with them included. thank you