Jump to content

BIGNEWY

ED Team
  • Posts

    41211
  • Joined

  • Last visited

  • Days Won

    603

Everything posted by BIGNEWY

  1. Hi Scommander2, as far as I am aware it is automatic based on IP. Which region are you in?
  2. folks just a pre-emptive message. Please stay away from politics in this thread thank you
  3. 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
  4. great to hear you have a new build, hope it works well for you, if you need any tips and you are on our discord server just message me. thanks
  5. Hi, we are coming closer to completing all of our development goals for the F/A-18C, currently working Additional MSI functions [In Progress] Continued refinements to the flight model and flight control system [In Progress] Updated external lights [In Progress] Updated radar performance [In Progress] Radar Terrain Avoidance (TA) mode. [In Progress] but even after our goals are complete development tweaks and bug fixes will continue. Check out our road map here
  6. folks I dont want to derail this crash report. Windows 10 is still supported for now, but it is going end of life. Windows 11 handles CPU management better. but its not the subject of this thread. thank you
  7. Hi, I have the same device and not having any issues, can you explain more? thanks
  8. when they become end of life, eventually it becomes difficult to support them. I am not aware of any date however
  9. please attach your dcs log from a session where it hangs. thank you
  10. 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.
  11. We will share news as soon as we are ready to, but for now the work continues. thanks
  12. 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.
  13. Folks we have been pretty lenient in these threads so you can discuss the situation, but please dont take it to far or we will have to moderate here. @Ignition please just stop, we understand its difficult not having the full picture but it isnt something we can discuss in public.
  14. we will check with the team thank you
  15. Folks please dont go off topic. Please note that we will be making adjustments in future updates. So please continue to be patient. thank you
  16. Until the dispute is resolved we do not know and can not say. We all continue to hope for a good outcome. thank you
  17. Hi folks, we have no new information to share. Once the dispute is resolved we will know more, until then we have to continue to wait. thank you
  18. I will ask Wags, it could be the video is incorrect.
  19. Thank you for the new tracks, you need to decouple when calling the ball for a manual trap. ACLS is NOT designed to be engaged all they way to the trap. Later systems like "magic carpet" allowed full hands off trap, but not ACLS when calling the ball, use the paddle to disengage ACLS hope that helps
  20. I own a winwing throttle and it is great for me. I appreciate you may not be having a good experience but posting here like this really does not help.
  21. There wont be a patch this week. As soon as I can share a date I will. thank you
  22. Hi page font outlines are already planned for a future update. thank you
  23. Hi all, sorry for not replying sooner, this is reported internally and on our list to fix. thank you
  24. cool thanks for sharing, I had a great visit at the aviation museum at Middle Wallop with my wife.
×
×
  • Create New...