BIGNEWY

When we are ready to share news we will, if we need more time we will let you all know. 
So come on Limepartician, please be patient. 🙂
thank you 

Hi, 
this is correct as is in game. 
We have updated the manual, however the highlighted part was not present in the latest manual update, but will be included in the next 

thank you 
 

I would suggest waiting for the next patch, if you still have issues after you will need to provide short track replay examples. 
thank you 

I will ask the team if it is correct again, but it has been this way for some time. 
 

this has been reproduced and reported 
thank you 

No problem if you can get a track that would be great, but so far we are unable to reproduce. 
thank you 

Thanks 
please remove custom mods 
Custom Mods
Iron Dome,Hercules,A-4E-C,Military Aircraft Mod,Civil Aircraft Mod,Massun92-Asset Pack,LLH_Counter_Insurgency
Then run a slow repair of DCS and retest 
thank you 

Hi, 
your track seems to end quickly and does not show the issue, can you try and reproduce another. 
When we test all seems ok, ensure you are in CCRP or LADD and not CCIP. 
thank younull 

Its been discussed many times, and not planned. 
thank you 

Hi, we are not able to reproduce this crash. 
I dont think you have any mods if you do remove them, run a slow repair of DCS. 
If it continues to crash please add fresh logs 
thank you 

Custom Mods
A-4E-C,Kaiser Class Oiler,Military Aircraft Mod,Project_205_OSA Class BETA,M142 HIMARS 1.3.2,EF-111A-main,IDF Assets Pack,FRENCHPACK 491 CORE,USS_Blue_Ridge,Civil Aircraft Mod,Vietnam Assets Pack,FRENCHPACK_5.0,Tacview,SMAO 2.0,SAMSitesAssetPack,SH-60B,UH-60L,DCS-SRS,M198 HOWITZER 1.0,Hercules ver 6.8.2,P-14 Tall King,Project_956_Admiral_Ushakov
 
Error
unexpected symbol near ','
Line
161
Script
C:\Users\cblou\Saved Games\DCS\Mods/tech/FRENCHPACK 491 CORE/Fr...

Error
attempt to index global 'c' (a nil value)
Line
133
Script
C:\Users\cblou\Saved Games\DCS\Scripts\Export_BEH_Motion_Cls.lua

Error
'=' expected near 'dofile'
Line
2
Script
/sounds/51/Sounders/GroundUnits/IFV/amx10rcr.lua

please remove all unofficial mods and run a slow repair 
thank you 

Hi, 
we have reported this internally already 
as you can see it is FLT - FLT - CMBT currently
instead of FLT - CMWS - CMBT
It will be fixed in a future patch 
thank you 

Looks like I am wrong so will delete my previous post. 
With the old AAQ-28 Litening the reboot was required.
With the new AAQ-33 ATP it is not required.

this has been reported, 
thank you 

We are not able to reproduce the gear down issue, so please check your bindings and attach a track replay example. 
thanks 

please be sure to read our change logs and this post, the mission may need a tweak 
thank you 

Hi, 
thank you the team have reproduced and reported the issue. 
 

reported
thank you 

Hi all, just a few points, raptor probably touched on them in previous comments, but here we go. 
1) The colour of a bugged target tracked by the onboard FCR without datalink contribution can be altered by DTC colour settings, and the current FCR chapter in the DCS manual is from an earlier version of the DCS F-16 that was using a different colour (yellow) than what exists now in the game (white). Neither is incorrect, but it represents a pilot-configurable item within the DTC settings.
2) The Air Target Data Table (ATDT) rules that govern the colour and shape of an FCR symbol as Friendly/green, Unknown/white, Suspect/yellow, or Hostile/red should be the same regardless of whether it is detected by the onboard FCR or not. The only bug that is present is that these rules are being applied for targets detected by the onboard FCR but not for offboard datalink tracks. This is intended to be addressed along with the corresponding DTC feature.
The FCR chapter is being revised and updated to the current DCS F-16 state, and future DTC settings in development should provide players with the ability to configure symbology colours and select which rules the ATDT uses to affect the target symbol colour and shape.
additionally:
When datalink is applied to the FCR display, the scheme of what governs "solid" vs "hollow" target symbols is altered, to include TWS mode. As Raptor stated above in his explanations, you must still have sufficient radar track data to bug a target for an engagement, but if datalink information is applied to the FCR display, using the "hollow" symbol state as an indication of this will not be available due to how the datalink correlation is represented on the MFD.
Again, a more thorough explanation will be provided in the revision of the FCR chapter. 
 
thank you 

Hi 
I would start by removing unofficial mods and running a repair, but a BSOD is usually signs of bigger problems, if possible attach your dxdiag also. And check your event viewer for clues about the BSOD. 

Some advice below based on what is in your log. 

Custom Mods
Hercules ver 6.8.2,DCS-SRS,SAMSitesAssetPack Beta 19,Civil Aircraft Mod v0.87.7,Large Nationa..."],CH Military Asset Pack China 1.1.4,Military Aircraft Mod v1.7.1a,A-4E-C,SMAO 2.0

Error
unexpected symbol near ','
Line
27
Script
C:\Users\jstoe\Saved Games\DCS.openbeta\Mods/tech/Large Nationa...

Remove the OH6GunnerExport script for performance reasons.

Windows 10 will be EOL Oct 14th 2025. Upgrade to Windows 11.

If you are overclocking your cpu, ram or gpu try defaults. 

Hi all, 
I have checked with the team, and we currently most accurately support Mode 1A. It’s quite possible that something has changed since Wags originally recorded that video.
There are a couple of carrier recovery items to fix that we are aware of for manual approach, that should then address the Mode 1 issues you bring up.
Thank you.

Hi
page font outlines are already planned for a future update. 
thank you 

Basic life cycle of a bug

Bug is presented,
We try to reproduce in public builds,
If we reproduce we then check internal builds,
Create an internal report with all data and tracks and which builds are affected,
Dev will be assigned the task by a project manager,
Fix is made,
We test internally and merge if fixed or send back to dev,
If fixed its merged, we test again once in closed testing,
Closed testers will check also,
then if fixed it will be in the patch notes for public patch day.
 
Project managers decide the priority of bug reports, they have the full picture of what is involved and if the bug or report is tied to other issues or new features. 

Some issues can take much longer than others, it wont always be obvious to the end user why, but all the fixes we make will be in the change log. 
thanks

Ive just checked with the team a sub menu is being created to allow for the longer list. 
 

this has been reported. 
thank you