Lord Vader

Hello @LuseKofte I've tried to load cargo in a running helicopter in MP and saw no issue on my side. We really need that track if you can share it, thanks for understanding. Also, can you reproduce this issue in singleplayer?

Hey @T-B0NE Thanks for bringing this to us, indeed a strange one. Reported internally for analysis.

Hi, @Makla26 This indeed looks like a bug. thanks for the track replay, @grim_reaper68

Please share a track file of the event so we can analyse the conditions.

The false target generation is not taking into account actual other aircraft being picked up. It's generated due to ambient noise our even by the internal receiver itself. Like we've stated before: "They are caused mainly by internal receiver noise and ambient noises at receiver input. The radar internal circuits maintain false target rate constant with an average frequency of one false alarm per minute."

Thanks for bringing this to us. I've raised this internally for analysis.

Hello @darkman222 This was a fix for a very specific issue, an improvement. We are still investigating this matter.

You can make a short track, for example a clean mission in Caucasus and share it right here. Again, I tested turning using the correct procedures and it worked ok. It requires some practice since only one wheel is power steered (the right one) and the other is free turning. All turns should be slow and anticipating trajectories. With some practice it becomes easier. Most of the problems we've seen from users involve too much speed and oversteering.

Hello @Xhonas Thanks for the tracks. However, you must realise we cannot model a system comparing it with other aircraft, much less other simulated modules. I understand the comparison serves to show the speed at which such systems "usually" work but we need to model the aircraft according to its appropriate public evidence and/or documentation. We are aware the F/A-18C does need some revision in various areas of the radar logic and, like I stated before, this is being worked on.

Hello again. I would suggest you first reach whoever runs that server and/or created the script to see if this is something they can address on their side. Thanks for understanding.

Hello @The_Nephilim Sometimes, you may register kills, even George can confirm the hits, but if the unit survives, even if damaged, it's not accounted as a kill. Regardless, there could be an issue with the scoring logic. What we need, however, is a track file of the events, otherwise there is no way to verify if you did destroy units or just damaged them.

Hello @-Bob- When you have these issues to report, it's good practice to share a short track of what you are experiencing so we can analyse. We've tested internally and found no issues turning either side. Please read the manual on the ground steering section to full follow the procedure (turn on steer, turn off AFCS, etc). After following those procedures, if you still see issues, we will need a track to verify the conditions.

The fact that you cannot move the ramp is intended. However the position of the ramp will be reviewed in a future update to make it more realistic and practical for the gunner.

The AN/ARC-164 is indeed installed and its control is integrated in the CDU COMM page.

This was mentioned already and was reported. Asking to merge threads.

Hey @Tomcatter87 I've raised this internally for analysis. Thanks

Hello @NightstalkerNOR I've reported this internally, please understand this will be a low priority item and might not be fixed anytime soon.

Hello @Nealius Unfortunately, your track doesn't replay correctly as the mission requires mods. This could also be your problem, please disable these mods temporarily and try again to replicate the issue. I tried performing a couple of hard landings but could never get the results you mention. The damage model for the CH-47F is not yet complete and you could have encountered a small glitch. But, without a proper track, we just can't confirm it.

Glad it's sorted. Please return to us if you see it again and remember to include the requested items on your report.

Hello again @_Delta13_ There was no disregarding of an issue, I simply read your post and the description lead me to a possible misinterpretation of the procedure vs the fact our EA manual is being reviewed. It's not a matter or being "easier" and we take all reports seriously. Now that you clarify your point, I will take this internally for analysis. Thank you for your time.

Hello @super_soup We've tested this exact scenario that you describe and could not reproduce. Indeed the targets are shared between stations when either performs a FCR scan, including using C-Scope. Please supply a track from both the pilot and CPG perspective so we can have a look.

Hello @_Delta13_ As we've mentioned here before, the DCS: F-16C Viper manual is undergoing an extensive review to produce a new and more accurate document, based on the various updates and improvements we've done to this module over time. Therefore, that particular section and phraseology may require some polishing. Thanks for understanding. In the current version, the TWS hands-on azimuth selection (60º) is entered by moving the cursor to the left or right edge of the MFD (or using the OSB 17 and 18 as you did), and it is also exited with the same procedure. But this is only if there are no TOI selected via TMS up. If there is, the scan volume will "stick" to the TOI and will remain available.

Like we've stated many times for the DCS: F-16C (and DCS: F/A-18C), although the FCR is not radiating, the receivers are operational in Silent modes, therefore it will draw false targets occasionally.

This isn't a "problem" this is a feature added for those with VR and head motion devices to remove the head but replace it if necessary for screenshots or other situations. If you move the pilot POV forward beyond the threshold on the F/A-18C, it will also show the head:

This was reported internally, thanks for letting us know.