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.

Personally I find the most useful part of storing target points is displaying the threat rings ( I think 3km), it's easy to create a quick picture of where you need to be especially vigilant and expect enemy fire and can help you maintain stand off distance around a cluster or 'zone' of enemy units. I like to use voice attack to quickly do the DIR input buttonpushes then select a target point on the TSD with the cursor to orient myself towards the target area I'm focusing on next. With some practice you can use the TSD kind of like a FPS game minimap.

If you're getting shot at the only proper move is to drop the collective and evade. Try to keep a stand off distance of 5km+ to stay out of the envelope of most threats.

The only time I struggle controlling the aircraft with the ftr depressed is at a hover, so as Im bleeding off the last of my speed I let go of the ftr and bring it into a hover and land.

If the current version had the roll/pitch changes but the yaw remained unchanged it would be perfect. It wants ALOT more left pedal and even slowly putting in collective the nose just wants to go making even gradual decelerations sloppy, back to messing with controls I guess.

I wonder if this is the same issue with the AI bot being unreliable with the limas, some sort of desync occurring that isn't present when operating the CPG seat solo.

Yes this became an issue I think in the April patch. For now what I do is set the bot on gun and engage at will then I WAS and DEWAS the gun as the pilot and this seems to 'reset' the bot and it will do another burst. I repeat as necessary.

Additional track if required. Shots from varying speeds, altitudes and ranges with only a handful hitting. georgelima.trk

This needs to be addressed, there's no good reason for the discrepancy between self fire and getting the bot to.

Changes to the FM seem good, the reliability of the lima on the other hand not so good.

George will arm when you slave him to your los and safe when you tell him to cease fire (this also returns the tads to the fxd position forward). If you arm the aircraft prior to george performing it automatically via slaving he will not override this when you tell him to cease fire.