Lord Vader

Appreciate your help, @Smashy.

Hello @Smashy I watched your track, also followed your instruction and tried it myself, what do you mean "swapped"? In my replays the elevation pitch carat continues to follow the bar sweep position and the B-line centroid is set above the target. Perhaps you can illustrate what you are experiencing with a video capture. I can't reproduce the mentioned issue. Or maybe I misunderstood something.

Hello @Nealius Slight change for the DCS: CH-47F, the view.lua file is located in DCS World\CoreMods\aircraft\CH-47F. Thanks.

Hi @xSerafin Thank you for the tracks. We're looked into them and we raised the situation internally for analysis. Thanks for bringing this to us.

Hi all, we need track replays to capture these bugs. If you can reproduce it in a simple mission, say in the Caucasus, please share it.

Yes, @prestupnik. It seems further fixes are needed. Thank you all for your patience.

Hello @falconzx I'm a bit confused with what you are reporting here. You are saying that "after a couple of tries" the antenna elevation no longer centers to 0 pitch when the target is lost. But I am seeing just that every time you drop the target beyond gimbal limits, the antenna elevation just recenters. I took control and it did the same every time I repeated the same manoeuvres. What am I missing here?

Hello @VampireNZ Obviously, reflections need to be somehow of a lower resolution and frame rate in order to keep performance acceptable. However, in our tests, we don't see it with that low refresh rate you mention. 2025-01-22 11-43-51.mp4 Can you capture a short video with what you see?

I will bring this again to the team, for the sake of continuing the discussion. However, it has been said several times that our JHMCS models have been designed and reviewed using internal sources and SMEs. Sometimes shapes differ between models, as mentioned before.

Hello @Hofftari Yes, we were able to reproduce and have reported internally. Thanks for your care.

Indeed, @Alpiinoo This specific crash has been reported and a fix is already incoming in a future update. Sorry for the inconvenience. For now just avoid using these options. If you wish to place the radar in a non emitting mode, just use the RF Switch or turn the FCR off on the right hand panel.

Hi @Alpiinoo When you say "radar mode standby", are you referring to the switch on the right hand console for "FCR On/Off"? Or the 2RDR ALT On/StandBy/Off"? In any case I tried both switches and got no crash. What are the conditions to create this crash for you? If you could list the steps it would be appreciated.

Hello @xSerafin We require a working track replay of the event in DCS and cannot use a third party recording to observe it. Thanks.

Again, we don't have sudden engine shutdown out of the blue events being reported. Aside from the already mentioned fuel starving events, key bindings or "noisy" axis or even damage explains some of the engine loss issues we've seen. However, in order to actually see what's going on, we do need a working short track. Please try a simple mission, perhaps a Instant Action mission in Caucasus and if you reproduce it, send us that track and we will certainly look at it.

We've heard about this before but unfortunately we could never catch it ourselves and all the supplied tracks were not usable due to length or scripting. In the past we've identified a possible issue with script generated threats. It seems some scripts activate or deactivate (spawn or despawn) threats differently from normal triggers and this seem to generate issues with the HTS. This could be causing your problems. Again, if you see this happening in non-scripted missions, preferably in short tracks, we would very much like to have those tracks.

Hi @v2tec Please supply a track replay of this event so we can analyse what is happening. Thanks.

Hello @perryverde This kind of look like a fog issue. We've had a few reports about it. Please wait a bit until the next update and try again, if you can. Let us know if the problem persists then, let us know.

Hello @71st_Mastiff Lots of things can happen to cause engine shutdown. A double engine shutdown sounds (just sounds) like a fuel problem. We've seen a lot of instances when, for example, users don't check the fuel and don't notice the AUX fuel tank isn't activated, for example. Of course, we would need to see it happening but your track fails to load. We don't have any other recent reports of a sudden engine shutdown, unless caused by planning error (mostly fuel) or damage. If you ever have this event again, please report it with just a track.

Hi @Sparrow-5 I just tested the trim for the roll axis and it seems ok. Like it was suggested, check your bindings. If you need help, post your binding for the trim hat switch so we can haver a look.

Hey @FalcoGer I've raised this internally for analysis. Regards.

Hello @Istari6 I have raised this internally for analysis. Thanks.

Ciao @perryverde We would need a track replay of the issue you are encountering to analyse the conditions and procedures. Thanks.

Hey @Hofftari What you are trying to do is select PDLT, a Primary Data Link Track to become a symbol on the HUD/HMD. I've followed your steps in the "Free Flight" F-16C Instant Action mission, used EXP1 and EXP2, TMS up to select one PDLT then cycle using TMS Right, no freeze or crash on my side. Was this on multiplayer? Was this on a scripted mission? The usual suggestions is that you disable any mods you may have installed and try again. If you don't have any, please run a repair or cleanup (available on your launcher). Let us know if the problem persists.

Hi @wwWolfcom Even though this advisory is a result of an incorrect procedure, we'll look into it.

@giullep I've checked your track, indeed I can see the switch being activated but the aircraft doesn't seem to respond. However, when I take control of your track, I am able to activate all modes, (ALT HOLD, ATT HOLD, HDG SEL and STRG SEL) either by pressing the switch with the mouse or via button assigned to my joystick. I suggest you run a repair and make sure you disable any mods you may have installed and try again. Let us know if the problem persists.