Rongor

Thanks my Lord. And thanks @Moonshine

When I created the report, I didn't even had noticed the box not flashing. Only you made me aware and now I see it too. This may in fact very well be the underlying issue and I was only connecting it to PB on Snowdrift because I didn't see this other clue. Doesn't solve my apparently corrupted track yet lets take it from your approach then. Again, thanks for also looking into it.

well thanks guys for looking into my stuff, will report back after further testing when repair is done.

While I will follow the advice to run a repair, here is what I was seeing ingame and do see when replaying the track: 0:05 flipping Master arm off and on again 1:44 launching on 11 defeating missile until 2:40 3:30 attempting to launch on SD 3:37 trying it with the alt release button

Ok, I did a repair only 2 days ago but can try it again. What would still interest me is if you see any HARMs launching at all in my very first track, since Master arm is allegedly off, none should launch. Yet they do in my replay...

only to be sure, you want me to run a system repair because a situation I experienced was exactly recorded in my track as I witnessed it and also replays correctly on my end, while it doesn't replay correctly on your end?

Sorry, but then your track replay is wrong. I just rewatched this very track I attached above (no HARM on SD.trk) and Master Arm on is happening right in the very first few seconds. You see it on when mission starts and then verifying me its state by flipping it briefly off and then on again within the first 10 seconds. The fact I then launched a HARM at an 11 is evidence Master Arm is on. Also Master arm remains on after I launched this first HARM. Then I redesignate on the SD and pull into the loft. This is a screenshot from this situation, made in the track replay, time code in the DED 22:03:30: you can even see me depress the Alt release button thereafter...

Then it might be a problem with Master arm? I'm pretty sure I had it on. In this first track you can see me redesignating to the 11 in the HAD when launch at SD fails and then the HARM did launch, without me touching the master arm at all. Also this is only the one attempt I did specifically to do the track. I had it exactly like this before, hand off to SD didn't launch, then redesignated to 11, launch occured. That's what made me replay the exact situation again to create a track.

this is also an issue when starting hot and 90/30 is set in the mission editor. 10 second track attached 88_28.trk

TMS right has currently no effect unless one does call up the SEAD DED page with TMS left before on a selected threat and keeps the page active. Only then target stepping with TMS right is possible. The moment you undesignate, the DED will return to CNI. TMS right then won't step targets anymore before or after designating a new threat. You are required to TMS left before. very short track demonstrates this HAD_notargetstep.trk

I also set up a test mission and can provide two very short tracks. Bottom line: If there is more than a single target (2 in my mission) on CRM-RWS, the antenna does begin to jump between two elevation bands the moment I bug any one of these two targets. It does not jump with no bugged target. It also doesn't jump when entering SAM after bugging the only single target on the screen. The moment there is more than one target detected in RWS, the jumping commences, regardless being in SAM or DTT. CRMRWS_singletarget_nojumps.trk CRMRWS_twotargets_antennajumping.trk

I hand off a SD of an SA-11 site from the HAD as SOI to HARM set to POS-PB-mode. Pressing weapon release doesn't initiate the launch, although I am inside the AMZ and on the optimal loft cue on the ASL. Not even the alt release button doest trigger the launch. When switching HAD-target to the 11-TELAR and handing off again, HARM does launch normally, only on the SD it doesn't. no HARM on SD.trk Tried the same situation with HARM being in POS-RUK. Again did the HAD handoff. HARM launched on the SD normally. HARM on SD in RUK.trk

According to the manual, selecting SP on the TGP should command the TGP's LOS at half the distance of current FCR range. This is currently not the case. Instead the TGP's LOS is commanded to the current steerpoint, into the sky if these points have altitude. In the attached track I select SP on a SOI'ed TGP while flying towards a steerpoint set to 6500 ft altitude at 12 oclock. It's commanded into the sky instead of the ground. After TMS up I have to slew the TGP down towards the ground. Switching to a second steerpoint roughly colocated with the 1st, yet on 40000 ft makes the SP command the LOS even higher into the sky. The FCR range is 40 in both cases, yet the LOS is clearly commanded to the steerpoint instead of half the FCR-range. TGP SP elev.trk

I can easily reproduce it. By moving the cursor to the frame. stuck. simple

updated with a video

- VHF frequencies show with a preceding U instead of V - entering of 2 digit frequencies with 3 zeros after the decimal are interpreted as times 10 (3 digits in front of decimal) and end up as UHF frequencies or as flashing error if the freqx10 is outside the UHF range - FM mode is unavailable. You can select it and it switches to FM in the UFC, yet in fact its stuck at AM under the hood. FM communication is currently impossible, so on many MP servers you won't have contact to other players working in the lower VHF range of 30-88 MHz 20230627_114150.mp4

Razbam felt like inventing something new instead of simulating RL

I didn't yet manage a takeoff without oscillating pitch angle after rotating. Also this doesn't get much better during cruise. Whenever I do pitch inputs with the stick, there is some odd reaction into the opposite direction after a few seconds. This is not happening with roll inputs.

I understand that the lady's fire callout is nothing one might want to ignore or miss, yet is it really that ear hurting loud in the real thing? I'm aware I can turn it down by lowering the DCS volume options, yet all other cockpit/helmet stuff seems ok and I don't want to decrease the volume of everything.

It's because AoA is displayed in "units", not in degrees. It's in the manual.

20230625_160434.mp4

please move thread to https://forum.dcs.world/forum/1173-bugs-and-problems/

please move thread to https://forum.dcs.world/forum/1173-bugs-and-problems/

PB9 in the radio setting is supposed to switch between AM and FM. Instead it only switches MAN-AM to MAN-FM being displayed without actually changing the modulation type. Tested with SRS, which reads out the data from DCS. So communicating with other players on FM radios in the 30-88 MHz range is currently impossible. Please move into https://forum.dcs.world/forum/1173-bugs-and-problems/

We had this similar in the Harrier when people needed to enter 30.001 to get to 30.000. It's the same annoying thing here. 45.000 can only be entered as 45.001, 66.000 as 66.001 and so on. If the freq is in the 30-39 MHz range and ending with 3 zeros after the decimal, entered frequency gets auto-converted to UHF by an added zero in front of the decimal, so 30.000 ends up as 300.000 and 39.000 as 390.000 MHz. please move this into this forum: https://forum.dcs.world/forum/1173-bugs-and-problems/