Kula66

That's great, I'll test with your mission and update you with the result.

Hi @BIGNEWY was the track and video useful? Were the devs able to review it ok? Did it demonstrate the issue? If you need other tracks, please let me know, this can be reproduced fairly reliably.

Herewobble.trk is a track and it fairly easy to reproduce. In the video I don't think I was touching the peddles or putting inputs on the stick 2024-03-08-15-49-16.mp4

This wobbling seems to have become much more violent (seems to have a pitch component now, rather than just yaw previously) since the latest FM update. ill try and get a track next time, but for me it seems to be triggered by flying through the wake of another aircraft while in bfm with wake turbulence turned on.

Thanks ... I use the dark 'theme', and looked 100% here

Any plans to do a dark, low detail map to help with the visibility of info on f10 screen? Would greatly assist with comp streams. Current F10 views make it extremely difficult to see icon details on F10, especially when streamed. A dark/high contrast F10 view would really help for streamers showing comps etc. Thanks

I find if I keep the stick centred, so you don't stall the wing at high AOA, and just use rudder ... I've even increased the dead zone in the roll axes so I don't accidentally activate the spoilers.

This is the toned down version ... a few patches ago, it was far more pronounced.

Get closer ... when he fills the screen, fire! DCS AI defends like a demon.

I've certainly seen similar things a few times ... bandit visible visually as a dot (15-20 miles), closing head-on (so a good radar target), visible on D/L, LACQ selected, in the circle, correct PRF, etc and no lock. Very frustrating. I understand the 18s radar is going to be reviewed 'soon', so fingers crossed.

Given how distracting the green mirror adjusting symbol is, perhaps it may be an idea to limit it to just a small portion of the mirrors rather than the entire area? Also, they appear doubled up in VR. Many thanks

I never said it was ... just giving you my feedback as a long standing, and probable future customer

Can I suggest that when you add such a 'feature' (like battered cockpits or pilot body), the first thing to implement is a method of disabling it, rather than leaving this until last Then those that don't like it, don't have to suffer and have the inevitable extended wait for the enable/disable implementation.

So were issues like the radar failing after take-off, but I wonder how many people would want that in a sim? Me, no thanks. Please can we have a way of disabling it, I think its horrible. Oh, and tilting the mirrors is lovely, but can we please have a simple click to enable/disable them too?

Sorry to hear that, I see how that would be an issue.

Have you tried Viacom? You can just say it

Agreed ... VIACOM made 14/pilot/RIO work for me Lets hope there is a quick fix ...

Who mentioned putting CFTs on 15Cs? Not sure where you're getting that from.

Perhaps Razbam intend to release a 15C later ... If you could take the CFTs off, that would hit sales of the futureA2A bird Either way, day 1 purchase for me

Ok, here is the typical scenario: you are in a valley, flying low and Jester spots a bandit visually, somewhere ... out of radar scan, ie. left, right or behind; you want need to wait until he finishes to know which way to turn, ie. wait for his clock call. If he said, '7 o'clock, bandit, Mig 29 ...' you'd save yourself precious seconds.

Thanks, I understand that.

Is it possible to reorder the phases used when Jester announces a new bandit in close? I understand this is not a user change, but hopefully maybe a quick change for the devs. He currently says something like 'Bandit, Mig 29, 2 o'clock, 3 miles' when really the bit I'm interested in is the direction of the bandit! I have to wait a couple of agonising seconds for the key part of the message before I can react. He also sometimes adds pauses and stutters, which is not appreciated. Thanks, James

I too find WACQ mode inconsistent, but I put it down to the length of time it takes to complete a full scan … too many bars and too big an angle to cover; vertical scan and boresight just focus on a much smaller areas of sky. It just depends on where in the scan pattern the target is.

You want your pagefile on your fastest disk

Interesting. I have 32GBs of RAM installed and recently set my pageing file to a fixed minimal size ... DCS started crashing! I didn't put the 2 together, but the ED support guys spotted it. Scary to think that 32GB of RAM is not enough