Zomba

I was in SneakyBastd's server as a client doing the same thing. He's my log. dcs.logdcs.20220129-042025.crashdcs.20220129-040913.crash

I've encountered this from time to time. Moving the mode knob back to it's alignment mode and redoing the alignment clears it. I'm not sure what the cause is.

I'm not sure why people are saying they're unreliable in TWS. I've been flying CAP a lot online lately and the net result is the missile is far more reliable than before, especially at longer ranges of about 30nm+. You get the occasional successful notch but that's about it. This is after shooting down well over a hundred aircraft.

Like above just put it ahead and then go to PTRK mode and let it capture the unit. If it misses and you've been scrolling around a bit from DESG point it sometimes works best to hit TDC depress, drag the offset curser to infront of the vehicle again and then SENSOR back to ground mode and it will move the TGP to the new DESG point.

Terrain following and waypoints is in PP mode, which will probably get fleshed out later.

I came here to report the TGP bugs, but all the ones I've found have already been listed here comprehensively already. On a side note there's some daylight between the patch notes as they relate to the TGP and how it actually functions post patch. It might pay to review patch notes prior to release to make sure it's reconciled correctly.

I think a problem accumulates and ends up breaking the atc comms and also the deck crew. Last night my sqn did an MP test in case 3 with over a dozen people. It just got progressively worse until nothing worked, including deck crew for launching. Repeated request for launch made no difference. Every so often the crew would wake up and direct someone onto the cat, but mostly they didn't. We tentatively think it's due to the atc comms on recovery getting overwhelmed and not clearing stale marshall slots. It also seems to assign the same bort numbers to multiple aircraft causing confusion. Comms get mixed up and stop responding. If the CVN transition from case 3 to case 1 it can leave some people stuck forever in case 3 comms even though the cvn is now working case 1.

Is the bug where the wings rip off when it flies through wake ever going to get fixed? I was watching a dogfight tournament yesterday and saw a few Mirages lose from an offensive position because their wings came off. I remember this bug from ages ago and incorrectly assumed it would have been fixed way back then.

I've felt the rate of development to be ok with the Hornet. I jumped on before DCS World was even a thing over ten years ago and the process was similar with the Ka-50 and A-10C.

Good stuff guys. I was worried I was doing something wrong.

No directional control over the spotlight. Although the animation responds correctly the actual light beam is stuck pointing straight down.

It appears that the link between UI setting and each aircraft's OptionsDb.lua is broken. OptionsDB no longer respects the UI setting for rudder assist checkbox and takeoff assist slider.

Is the Hornet able to use the radio expansion feature to create a third radio?

Some really nice work implementing wake turbulence. I struck it the other day when I accidently delayed my rotation on takeoff behind two Hornets and passed through both their wakes. Very cool.

Almost looks like an unexpected CG issue the FCS is dealing with. Your gun drum wouldn't be empty by any chance, would it?