Rongor

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/

page 142 in the manual tells me to use the scratchpad to edit presets... yet entering a freq into the scratchpad only makes the scratchpad line flash when I then press PB10 to enter it into the preset.

As per the manual, VHF freqs should appear with a preceeding V in the UFC. Instead it's currently always U, regardless the frequency entered.

"Both" wouldn't work as the Jet fuel starter can only support one engine spool up at once. The finger lift decides which engine you want to spool up next. Procedure is to start the right engine first, then the left. So neither are you supposed to actuate both finger lifts nor would it technically work.

60/60 is fine. 90/30 and 30/90 will bring 88/28 and 28/88 120/0 and 0/120 are fine. Here you go:gulfWar_TPE_v1_RUN2-20230624-201254.trk

Whenever I load a combination of 90 chaff and 30 flares with the ground crew refuel/rearming service, actual load then is 88 chaff with 28 flares. Always. Do you need a trackfile?

Happy to see this area included in Normandy 2

I couldn't find it in the airport list released in the FAQ section, so I interpret that this airfield isn't planned. It's a bit sad and hard to comprehend though as 1. this airfield is a necessary location to give the southern tip of the Sinai peninsula some meaning 2. you already put the navaids of this airfield into the map and 3. this place is an example of the rich recent military history of Sinai as it had been build by the Israelis during occupation as Ofir Air base, saw action during the war and would certainly be appreciated by CW scenario builders even if the map itself is rather aiming to depict the 2000s.

Just had something like this, only I wasn't even attempting to DTT. After I had bugged a single RWS contact, the antenna altitude automatically flipped every 2 seconds or so. I have a track file, yet (of course) its not short.

exactly what I am experiencing. I am at a 20 cm stick extension and have to apply curves to dampen this issue. Feels odd. Many of my control inputs are needed because the SCAS forces me to counteract.

ramp start (cold/dark) vs air start (up and running)

Shouldn't this thread better go into https://forum.dcs.world/forum/534-bugs-and-problems/ ? I probably never landed at Akrotiri but I recall Hatay having similar ILS issues. edit: this thread here seems to cover the issue too

I wouldn't rule out ILS gets turned off to save power, especially on airports which face hours of no arriving traffic at all. It still depends on whether the runway is equipped with ILS for both directions. If ILS is only available for one direction and the wind demands approaches from the opposite direction, they would likely still leave the ILS active because you could still make use of it for backcourse localizer approaches. Even if this type of approach isn't published for that airfield, it still can help in emergencies.