ivanwong1989

I am experiencing this same issue on F14A, On F14B it seems fine. The way to trigger it in the F14A is ECS Air source all normal, means when u spawn in air. Then u decrease throttle to idle. You will hear the whine, i think from electronics. Fine. Then u increase to Afterburner, electronics whine sound cuts off abruptly Then u decrease to idle, the electronics whine comes back abruptly and loudly as well. On the F14B, it seems the mixing is done better. The electronic whine sound is still cutting in when engine rpm goes low. BUT it is much much more subtle. I think the distinction have to be made that i think the sound that cuts off is NOT the air source sound, but rather the general electronic/cockpit whine background sound?

Hi, Been trying out the F1. It's a nice bird. However something's bothering me. Is the severe roll imbalance after firing a missile correctly modeled or is it unintended? Loadout is Center 1x R530 IR, Wing 2xSidewinders. After just firing 1 sidewinder, the flight's a bit wonky.

Yes seems to be an issue as well. Not in patchnotes as well.

I am seeing this same thing. When pilot blackouts, the controls are "not released to neutral position" So the plane keeps doing high G loops and the pilot NEVER comes out of blackout

Maybe I'm thinking it wrong. Since the F1 has no "computer linked hud + QFE" setting. It's all manual. I think i need to set QNH then manually offset the elevation in my head

When turning the altimeter knob to set QFE, it can't go below 930. So when my calculated QFE requires lets say a subtraction beyond 930, can't do that.

I concur that i see this as well. The first part of the throttle is counted as movement from the inputs, BUT it doesn't reflect into the plane's throttles.

I also encountered the extremely overdone sunglare/flare through the cockpit canopy... Which solution could workaround it for now? Will it be in next update?

Same bug encountered. ={

Closing topic as I think it is operator skill issue LOL. Im expecting too much performance from jester + awg9. Was thinking in terms of f18 radar that picks up stuff reliably in tws.

I've tried it a few times more. I think it might not be a bug... i guess... Since the target is maneuvering, it might have got into doppler blindspot. Hmm. And at that moment the track becomes an extrapolated track. But then what I don't understand is, when the target got picked up again a moment later, why won't the extrapolated track become the newly picked up contact? I guess the question is, when a target track become and extrapolated track momentarily, is it basically a game over for that instance and that missile that is still in flight?

Close topic, i think is my own skill issue in operating the awg9+jester. as well as prior expectations cause i was using tws in the f18 nicely. ================================================================================================= Scenario/Setup: SP mission with 1 Mig-29 AI, hot towards player ship, at 30kft Player ship starts at 20kft and hot towards enemy ship Player ship uses radar auto/tws auto Player ship observes radar track and f10 map of the real location of the enemy ship Bug Description: There seems to be an inaccurate track file present, or sometimes creating ghost contacts as well. No way to hold TWS track reliably to guide missile to terminal. Here's the track file: f14ghostcontactssingleplace.trk

Bug report. When going into lantirn contextual menu, and set Que to some waypoint, etc. Very often, Jester will get freaked out about air targets nearby and switched back to use TCS to try and identify air targets, EVEN THOUGH the mode is still at A2G, and I have no way of accessing the LANTIRN/A2G contextual menu again to set another Que point. Edit: Additional info. If I turn off crew contract - set to No Talking. (Which shuts up Jester) Then he will play along to A2G and focus on using the Lantirn rather than freak out about air targets around us

And.. it crashed before i could land and end the mission properly. Here's the crash log Something ACCESS_VIOLATION??? I've had multiple crashes since 2.7, however today was the worse because i ran my mission longer, like 30 minutes to an hour. dcs.log-20210422-144643.zip