Czar

I had once interrogated a friendly F-15C with the M-2000C in TWS, reply successful and friendly confirmed. I knew there was a MiG-29 in the area and it did popped up on the radar while I had the 15C still tracked. The MiG came right between me and the friendly, and instead of letting go the friendly 15 I mistakenly pressed IFF again to interrogate and turned out my aircraft did NOT receive the reply from the friendly. If I haven't interrogated the 15 before the 29 came into between us, I would assume there was two hostile aircraft in front. I think there is a bit more on that front. It is not super sophisticated but....

Was this on the ground with no airflow? If it was, it is an effect from CAS. When flying all control inputs are instantaneous. Look on the input graph with Ctrl+Enter to troubleshoot input parameters. CAS and other similar systems moving control surfaces on ground tend do mislead what the airplane can do in the air.

Also the looping sounds on cockpit as the Idle engine sounds or some startup sound keeps looping when on the ground at idle power.

Yeah, I never sat in a Strike Eagle. So I must accept the too high volume level from ECS because the first module iteration that comes in EARLY ACCESS should be deemed as exactly as it is in real life and missed values doesn't happen at all as the developers are pure gods... Some of us are just trying to point out things in order to iron out possible bugs. Over and over again folks points at "IRL the ECS sounds overwhelm every other sound" and "people got used to unrealistic sounds from other modules and they can't handle the real values". It is NOT the ECS mix against other sounds, is the DB levels of ECS that's way too loud on a headset. Same volume levels for all modules, no issue on hearing comfort. ECS is just too loud. Not as in: "I can't hear the aircraft like in a hollywood movie". It is: The output of ECS is too loud. <<<< I've never seen such defense on a brand new Early Access title. The module is pretty cool but is full of bugs as in the next OB patchnotes by Razbam points out. Great work on the dev side but gaslighting people trying to help make it better on the forum is bizarre.

Right inlet ramp seems to be off in comparison to the left inlet ramp. Any flight regime, on mission editor, wherever the model is viewed in sim. As well on promotional material.

Hands on Stick and Throttle at all times. The trim speed is fine.

The aircraft will often ask to re enter coordinates when it goes PP REQ on the HUD if you failed stored heading.

WSO has random animation but, I think, once you get on the back it locks the head to the view position you left. It also has arms animations when the virtual pilot looks back. It just need to be tweaked a bit to feel more alive and stay moving after you left the seat. Images when I left the WSO looking at the lower left panel. Poor guy was looking left the whole way back to base.

Pretty much. Also, don't rearm while aligning. The sudden center of gravity shift threw off the alignment process, I think. I just changed my startup flow last night to: Start Aircraft> Align> Rearn. Aligned flawlessly. Also Rearm can be made before initiating alignment, ofc. Not touching the ruder controls also a must during alignment. I found that you need to re enter all coordinates again after off and GC align. Wait at least 10 second to go from off to GC align, re enter the coordinates, or align via stored heading.

Perfectly put. XD Loving the SE so far with a few bumps along the way by the learning curve already ironed out. Delightful to have its capabilities. Big engines with a pre planned point in the earth to delete having just a massive radar as a flashlight in the dark. Just waiting for JDAMS, personally, for some SAM sites deletion. For now is a self escort bomb lasing machine with an immense payload and fuel tank. Excited for what's coming next for it!

Well...thanks... But I don't refer to ECS sounds vs other sounds. I just refer to the ECS volume itself on the Strike Eagle. Is too loud. (Bleed on 'Both' and 'Auto' Setting). Yes, the other cockpit sounds on the Tomcat sounds gamefied and holywood stilized. It is not what I was pointing at. Note: If that volume level is really just like how it is irl, whatever. Let it be it. No further complain. It is a very good tip. Also there is a switch that lowers the ECS power around the bleed knob, further decreasing the volume.

Castle switch long to display direction. I'd recommend 100% watching the tutorials on Razbam's youtube channel by Notso and reading the manual.

It is hard to believe the crew would fly high stress deep strike missions with complex comms and all the jazz of a modern strike fighter with a loud hair dryer noise near their heads. It is something wrong with volume levels, not really what the noise is. All my modules, including F-18C, F-14 A&B, A-10CII, M-2000C (from the same devs) sounds perfect and in realistic manner not tied to aesthetics of "awesomeness". Something is odd with the strike eagle that makes me adjust volume levels, something I haven't touched since 2014 in a wide range of different headphones.

There is a press and bump to a direction commands on the castle switch. But it is not like the Hornets TDC mechanics. That's exclusive for the hornet. Check Razbam's official youtube channel. Notso (SME) goes through almost everything on the tutorial videos.

Servers overloaded. F-15E released. Authorizations shouldn't be tied to game versions. Everyone who updated the game is locked out of it without the 3 day long valid authorization for the last successful log in.

Any plans to fix this issue? Every update, the 'mouse' folder is recreated with its .lua file inside that its only function is limiting possible keybinds to the mouse. I need some of those functions cleared to bind on mouse buttons and the only working solution is deleting the 'mouse' folder inside inputs for 'F-14B', 'F-14B-PILOT' and 'F-14B-RIO'. Other modules doesn't build that 'mouse' folder and everything is cleared to be bound to mouse buttons. It is a nuisance that serves no purpose.

You'll be breaking the main gear before the nose wheel unless you're landing nose first, which would be obvious as an answer to why the NWS wouldn't work. Unlock your wings (unstow wing folding handle at any position) to keep high gain nose wheel steering if that's what you're after. If nose wheel steering doesn't appear on the HUD with weight on wheels after recovery, check your bindings. Perhaps you're hitting the NWS disable command instead. Hard to tell with scarce information.

It is still as designed. TWS will always auto lock/designate the highest priority target. In the end, the auto lock/designation is handy. You will want it. You can cycle contacts with 'undesignate' button. If you just want to scan, just leave at RWS. I was very used to live with the bug where TWS wouldn't auto lock/designate and when they fixed it to the real life behavior, it was weird. But today, I would keep it 100%. Want to lock/designate something ahead? Cursor to its vicinity> TDC pressed> TWS and soft lock will happen without losing time of fine scrolling the cursor onto a target> Hard lock it with AACQ instantly if needed. If you have two contacts, the highest priority will soft lock while the second is scanned, cycle between both with 'undesignate'. If you want to soft lock/designate both it will relieve you the first TDC press onto the first bandit. It is better/more efficient this way. It is also accurate to the real thing.

nullnull

Cleanpit does pass IC. Keep in mind it won't modify anything on the displays and gets a bit dull without the wear from the default textures.

Hi, I'm not OP but also have the same issue. Cockpit Displays at max setting (fonts are not affected by this setting), MSAA 2x or 4x won't make a difference. Anisotropic filter at 16x. The issue happens when you're zoomed out. The fonts on the displays starts getting fuzzy in comparison to the HUD. Which is very crispy regardless. I got used to this. I'm comfortable to an extent. There is a cockpit texture mod for the Hornet, called Clean Pit F/A-18C HORNET cleanpit (digitalcombatsimulator.com). I found interesting that, the fonts on this mod (outside the displays) are crispier than the default textures regardless of the zoom level without getting the fuzzy effect. I'm running at 1080p (I know the limitations) but I found interesting that it is possible to have a crispier text. Maybe on DDI are also possible. Two of my shots are from the default cockpit textures (textures that have wear bellow the HUD). One looking down the cockpit and the other is at sunset lighting. One is using cleanpit (textures without wear bellow the hud). Has the Hornet nose up with a lock onto a target. Just for comparison. On the Cleanpit mod, you can see the difference between the cockpit fonts and the DDI fonts.