Lord Vader

@dutchili Again, please read what I wrote above. The object you are trying to hit is set on a bridge. The only way to correctly hit it in that condition is to aim at the bottom of that bridge. Remember we're operating coordinates, not visual locks. I took control of your track, aimed the TPOD at the bottom of the bridge, TMS up, dropped the JDAM and it hit the target.

Hey @ajoleary It's truly strange that I cannot reproduce the blocking issue you mention. Every time I tried, the mission progressed. Also, the track you supplied it also progresses to Mk-83 ripple drops. Perhaps you posted the wrong track. All I can think of is that you are not exactly hitting the trucks with enough damage to progress. The text does suggest you try again if you miss. Did you? As for the rocket quantity item, I've reported it as a low priority item. But still important to correct, thanks.

Thanks for this @ajoleary I've sent this internally for analysis.

Hey @Swson I've programmed the emergency JETT cover and button to keyboard commands on the collective grip, both on the Pilot and CPG positions. These animate correctly on my side. Are you programming the correct buttons? Please post a screenshot of your key assignments.

Hello @Vinny002 Unfortunately, your track doesn't help us see any issue. Taking control, the APU started correctly in our tests. Did you follow the procedures included in page 80 of our Early Access Manual for this module? Have you noticed it requires a special procedure with the switch position? APU switch – RUN for 5 seconds, START for 2 seconds, then back to RUN position. Again, we cannot find an error that makes the APU fail following the correct procedures.

Hi @Rongor Synchronization issues in multiplayer like these require track files when these events happen. Thanks for understanding.

Hi @dutchili The supplied track includes mods. Please try to recreate your issue in a clean mission for our analysis, preferably in Caucasus for simplification. Regarding the way you describe your issue, however, seems to indicate you're trying to designate the top of an object. It is advised to always designate the very bottom of the object. This is an optical "lock" performed by the TPOD, prone to be affected by parallax errors that can create an illusion the SPI is moving. In any case, we need to see what you are trying to do to be sure this is the case.

Hi @The_Nephilim Thanks for bringing this up. I reported it internally.

Thanks again for bringing this to us. I still maintain my opinion this looks (just looks) like a gimbal limitation on the turn but if we feel this needs an improvement we'll certainly address it.

Unfortunately, we can't be sure just by watching that video. We need to be sure this is correct behaviour for our simulation, based on the F-16C Block 50 CCIP. I will bring this to the team but, meanwhile, if anyone has that documented evidence, please PM it.

Can you try to replicate the exact issue in a single player mission? Perhaps place the Tarawa in a simple mission in Caucasus and attempt to do what you were trying to do before?

Hi @Ski11B Thanks for bringing this up. Reported internally.

Oh sorry, my bad. Voice Attack it is. Pardon me, I read it sideways.

Hello @bflo Can you explain exactly what and how you're trying to do this? If you are in single player, are you pressing the numeric keys 1 - 6? When you say you get a freeze, does DCS stop working or you just can't move the camera?

Hi @G-Tech Can you supply a track file demonstrating what you feel is the wrong behaviour?

Can you provide a track of this happening? Thanks.

Hello @mkel2010 Please reach VAICOM support about using this software. Edit: Moved to the correct forum.

Hi @The_Nephilim All Multiplayer trackfiles are automatically recorded in the Tracks/Multiplayer folder. We would appreciate if you could supply one of our analysis.

Hello again @Emme I have reported this internally for analysis. Thanks for bringing this burst issue to our attention. As for the gun missing, that is another issue we're investigating.

I can't make promises at this time. Rest assured we're aiming to make the DCS: F-16C FCR as realistic as possible.

Hey all. As mentioned in the changelog, some CDU pages and some features are still work in progress. This includes several xmit/receive features. Thank you for your patience, we're working on it.

Hello @Rongor Can you please supply a short track file of the issue happening? We appreciate your support.

Hi @Emme Can you supply a quick track demonstrating the issue? I tried bursts of 10, 20 and 50 with success. I cannot reproduce the issue you describe in that very same mission.

Hey @demon702 Can you make a screenshot of what you think is "very dim"? Also, what's your screen resolution? Sometimes this can also be caused by monitor brightness settings.

@Pillowcat and repliers. [edited] The false target depiction while in silent mode is correct as is. It's due to the ambient noise and receiver own noise generated over time. Thanks anyway for your input and thoughts.