placsea

I'm also experiencing a severe degradation in performance with 2.9.15, prior version works great.

Yeah can confirm all of these. I also notice no difference with position/att hold, still bucks around like wild horse when activated at hover and unreliable at speed.

George switching to FLIR on his own is massively annoying and I don't know why they have done this. George needs to be babysat and verified because currently the targeting logic engages IAT before he's got the laser where you would ideally want it, thus causing missiles fired to go long, this behavior is exacerbated when trying to engage targets without much elevation difference.

Its not switching anything. Up short directs the bot to slave to the phs and find targets, down long directs the bot to search for targets where the tads is currently pointed. This is the same logic/behaviour prior to the patch, the AI rose is just now different graphically.

Things I noticed after a quick 20 min flight. Low speed handling in all axes improved, much less twitchy especially yaw Att hold low and high speeds still borked Really does not like to be dived at speed now, couldnt pitch the nose down more than 15 degrees at 100kts without it going nuts Still crabs the same amount in trimmed flight Overall, better than it was.

I freshly installed dcs today after a recent reformat to try out the new patch and noticed the AI rose looks different, I had no issues utilizing george as usual. Maybe try reinstalling the module. Tested on Caucasus live fire instant action.

Ah right, its just a case Ive gotten so accustomed to what the sas was doing for me and then struggling when it was absent. Thank you for explaining.

Hey Brad, In your updated force trim usage video you don't recommend holding the ftr at a hover because you loose the benefits of the scas and I definitely concur with that. My question is should we expect any major changes to the handling and feel at low speeds with the ftr depressed or is it about where it should be?

Also can confirm this issue is still persisting. Not being able to quickly designate with the tads and fire and instead having screw around with the radar, ensure the nts is actually the target I want is obviously not ideal in time sensitive situations.

Have a good one fellas.

Hey Lord Vader, thanks for your reply. The mission is the edited quick action persian gulf weapons range. Only changes are added fcr domes to the apaches and placed two shilkas. As you can see in my screenshot the shilkas are correctly showing rings but the in mission tsd placed t03 and sa8 markers don't. Prior to the patch the generic targets had a 3km ring and the others varied by id type, which is obviously useful for situational awareness. Track included, if it helps. rings.trk

Is anyone able to show/hide TSD threat rings since the FCR patch? Toggling the show > thrtshow > right mpd buttons doesn't seem to have any effect.

Apologies for the dirt, forgot where I was.

[Removed]. Anyways, I use this voice command to then either enter with the cursor or if I know the waypoint/target/controlmeasure number I want input in the keyboard unit and push on.

A screenshot isn't going to help since you have to bind it all anyway. It's just using a voice macro to quickly get to the input field for the DIR to. So when I say 'DIRECT' it pushes the buttons on the MPD to get to the point where I can steer the cursor with my stick and click and boom that's now my waypoint/target. It's just stuff a CPG would be doing independently.