Lord Vader

Hi @f22raptoradf I have reported this internally, thanks.

Hi, @konradb3 I've tested your tracks and launched a server with your miz. I cannot reproduce the issue.

HI again @ChaosRifle Not only did I watch your tracks but also tried the same circumstances myself. You must take into account that sometimes, in certain circumstances, the target may temporarily be lost if it enters a radial velocity threshold. That's only a temporary loss and usually the target is reacquired. This has been recently tweaked to be more accurate. But if you still feel it's not correct, please do report it.

Hi @FalcoGer I think you were describing an issue with commands on buttons not being refreshed when autopages kicked in, retaining previous commands. That would be an issue, for sure. However, we did try to replicate the issue you describe in multiplayer, but didn't find any issue. We followed your instructions of the ASE autopage from ground threats being detected and the ENG autopage from a rotor RPM warning. In both cases, the CPG had no buttons to press, nor did we see any desync pressing the FMC options on either cockpit. All I can suggest right now is to perform a repair, check you bindings. We are always compiling sync issues to address them properly. So we appreciate your help gathering these findings.

Hello @Lekaa I have reported this internally. Thanks.

@ChaosRifle I followed your track and honestly couldn't see anything serious, there were some locks that got dragged behind but it appeared to be an acceptable radial speed degradation. @LekaaI also can't see any issues with the third engagement. You destroy the aircraft and then you move around and fire an AMRAAM against no one. What am I missing?

Hi @Michel0079 We require a track of this bug occurring if you can reproduce. I tested myself and found no issues.

Thanks but with that size it's quite possible we won't be able to use it anyway. Please continue to monitor and record it if you stumble upon it again. We'll do the same on our side.

We will be investigating this internally, thanks. It is always advised for something so specific to supply a track file of the bug occurring. This allows us to observe several different items, including how the mission was prepared. If you are able to, please add it here.

Hello @Voy This has been reported internally.

Hello @Voy This has been reported internally.

Hello @Voy This has been reported internally.

Hi @some1 I have reported this internally, thanks.

Hello again @AlexCabooseand @Se1ko I have reported this internally, thanks for your support.

Hi @Se1ko Thank you for the track, we'll look into this.

Hi @ChaosRifle We appreciate your description, it's valid, but like I said in your other threads, the best way to report this is with a track file, as short as possible and in a simple map like the Caucasus.

Hi @ChaosRifle Again, we will require a track file of what you are observing so we can analyse the events.

Hi @ChaosRifle We will require a track file of what you are observing so we can analyse the events.

Hi @travissgrey Like it was previously mentioned, we're still working on George's flight skills. Again, it's always recommended to properly trim the aircraft before handling the controls to George, especially when trying to hover.

Hi @DaveDewhurst Thanks for bringing this up. I have reported internally. @TheGhostOfDefi I didn't see this happening. If you have a track where a waypoint is actually deleted from the flightplan, please share it with us.

Hello @FalcoGer We are aware of some issues with multi-crew synchronization and appreciate all reports regarding this. Looking forward to that track.

Awesome @Pyrocumulous. Thanks for the feedback.

Hi @DCS FIGHTER PILOT(nice nick, ) The current implementation of the radar logic for the DCS: F/A-18C (and DCS: F-16C) is the result of an extensive study of several sources. Some of these changes may require some more tweaks to become even better. But, as it is, we're confident it is closer to a more realistic representation of the system, within the limitations of a simulation, of course. We always welcome opinions but these need to be supported by publicly available evidence. If you have documentation that shows, for example, that detections can't go that far, please feel free to send it to @BIGNEWYand we'll certainly analyse it.

Hi @Shimvolski Can you supply a track of this happening?

I'll have other people test on their side. Rest assured we're trying to figure this one out.