Rongor

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.

Ok, good to know, thanks guys!

which it isn't, as you can notice instantly on the screenshot I provided. I very much hope so, as it is in fact a very important tool for practicing. It's an underrated feature I think.

At the end of a cold start (complete INS alignment, I intend to start taxiing. You can see me pressing the NWS button several times, yet NWS remains inactive... Any idea why? 20230324_101017.mp4 NWS.trk

the side view of the glidepath would have to bend then

According to the trap sheet the landing on the carrier deck takes place at around close to 200 ft. How is this possible? Carrier deck is at 70 ft above the water... I don't think the glideslope is suddenly bent downward in the last quarter of a mile, so this side view profile doesn't make sense...

Thanks man

Whenever I get into an F-14 training mission and no matter if cold start or commencing in the air, the horizon elevation line in the HUD in T/o and landing mode show a deviation of around 5 degrees to the actual horizon. Am I supposed to use the little dial next to the VDI to correct this deviation to zero or is there more to it? The deviation might be there by default on purpose so I'd really know what the story is behind this, yet unfortunately the manual again leaves me clueless on this topic. It's also weird that in cruise mode the maximum possible manual correction isn't sufficient to bring that 0° horizon line up to match the actual horizon... So, can please anybody bring some light onto this?

I did, by the book. Ground power gets disconnected right after right engine start is completed.

Tutorial tells me to observe stabilizer fluctuation. Yet there seems to be no effect at all, neither on the indicator nor when checking the stabilizers visually. There is no automatic trim. I have seen it working in several (older) tutorial videos on youtube but it doesn't seem to work anymore.

During a cold start, when the R engine is up and running, I briefly put the engine crank switch to left until comb hyd pressure indicated 3000 psi, then put the crank back to off. When the pressure fell below 2100 psi, I activated the hyd transfer pump (switching it from shutoff to norm). To my surprise the comb pressure continued to drop and is now at zero. So I guess I have to deactivate the hyd transfer pump and abort startup because some hyd line or the pump is apparently broken?

The issue seems to be connected to the speed of the actual handle movement. The mouse can overcome the detents only when moved very fast. Slow dragging will produce the jittering of the (pulled) handle. Using buttons bound to the Emergency Wing Sweep Handle move Aft and Fwd can't pass the detents, as the continuous holding of the button doesn't create the input the mouse is performing when dragged rapidly. Same for the use of an axis.

Here you see me attempting to move the emer wing sweep handle out of the forward end (0:20) When this doesn't work by button, I then use the mouse to drag it free (0:26). Then button control is available again. Moving the handle back to the front again locks the button actuation out, I have to use the mouse again (0:38). Even the mouse then faces resistance. Button control is then available again (0:55-1:02) until it ends in the forward position. Further inputs again show only the jittering of the handle, remaining in place. 20230318_144055.mp4 Caution advisory indicator shows "wing sweep" and "CADC" in the end. According to the manual "Wing sweep" is to be expected when using the emer sweep handle. No idea why the "CADC" shows up, the manual doesn't say any thing to a possible connection to actuating the emer sweep handle. Both lights went away when I actuated the master reset afterwards. This is while doing a cold&dark startup by the book, still on the ground. The Emergency Wing Sweep Handle is impossible to be moved out of detents by button control and if done by mouse then still only reluctantly. No double bindings, also checked all axis settings (none set for that handle).

This continues to be a problem. No matter if I actuate the emergency wing sweep handle by mouse or a key bound to the respective forward or aft command, the handle gets stuck and then is visually in a micro-vibrating state for the duration of the attempted actuation. This is outside of the HZ TAIL AUTH requirements and can even happen when attempting to move it out of the full forward position. Yes, I pulled the handle upwards before and it is clearly in the pulled position visually. I can then eventually drag it loose by using the mouse but there is no way to actuate this lever without issues by using keys or even an axis

Engine crank switch has left and right but not off. Off is needed in case you do the cold start by the book. So engine crank switch off position please.

yeah I did that so you guys could see I am actually attempting to move stuff Using my hardware lever on my Virpil throttle unit would have needed a second screen to document my inputs

So keeping my lever in that 68° and then waiting for the light to go out and only then pull the lever back beyond? Was a bit difficult when using a hardware lever as of course I slid is all the way back and then forth and back did never unlock the required HZ TAIL authorization. Never suspected this being a bug though, only problematic, depending on the way you actuate the axis.

Why is this so hard? Occasionally it works after some sliding up and down, often getting stuck with a jittering handle... 20230309_163436.mp4

Both the online and the installed manual are from March 2019. Would somebody be so kind and eventually update these? It's a bit embarrassing to even read in the manual that some aspects will receive more detailed explanation in the future yet apparently the team forgot about it since 4 years. Especially since the training missions like the startup procedures contain a whole ballet for the player to perform across dozens of systems and tests and there is no real sufficient documentation on what all this actually is supposed to mean. For people who only wanna autostart and get into the air quickly to blow up some stuff War thunder style this may be totally perfect. Yet for those customers around who take the "study" part in "study sim" serious, this is a real let down situation.

Is it accurate that the pilot has no way to override this forced slaving to the impact point?