Floyd1212 Posted January 1 Posted January 1 I’ve noticed that since the latest patch (with the change to the George-as-CPG interface), he will actively switch the TADS back to FLIR when you command him to acquire and lase a target. As part of my startup routine, I will set the TADS to DTV so I can better see what targets he has found with the VID feed to the back seat. Once this was changed to DTV, he would not change it back. Have others noticed this new unwanted behavior? Is there a reason why he needs to be on FLIR now?
skypickle Posted January 1 Posted January 1 How do you set tads to tv from the back seat? 4930K @ 4.5, 32g ram, TitanPascal
ED Team Lord Vader Posted January 2 ED Team Posted January 2 Hello @Floyd1212 When you switch between stations you're basically handing full control to the AI when you leave that station. VID should be seen as a visual reference only as the CPG has full control over the sensors on his own station. I've asked if this was an intentional change, but I am pretty sure this is just George making his selection. 1 Esquadra 701 - DCS Portugal - Discord
Floyd1212 Posted January 2 Author Posted January 2 23 minutes ago, Lord Vader said: When you switch between stations you're basically handing full control to the AI when you leave that station. VID should be seen as a visual reference only as the CPG has full control over the sensors on his own station. I've asked if this was an intentional change, but I am pretty sure this is just George making his selection. If there were a human CPG in the front seat, I would totally agree, and I would let them decide how they want to use the TADS. And I would have some level of confidence that they are doing what they should be, and hitting targets appropriately. But George often requires a little "babysitting" as he has a tendency to lase bumpers, antennas, gun barrels, etc. With DTV I can actually see what he is lasing, and avoid wasting a Hellfire when there is a high probability of a miss, and then get him to reacquire the track for another try. Please let us know what the devs say about the change. And if it was intentional, if they would consider changing it back to the way it was; at least until George has been refined with more advanced target acquisition capabilities.
ED Team Solution Lord Vader Posted January 2 ED Team Solution Posted January 2 I've talked internally and the change was intentional to pave the way for upcoming improvements. Thanks for understanding. For now, you may need to trust George a little more. 1 Esquadra 701 - DCS Portugal - Discord
Floyd1212 Posted January 2 Author Posted January 2 Understood, and thanks for asking. Looking forward to the upcoming improvements. 1
Specter Posted January 5 Posted January 5 On 1/2/2025 at 1:33 PM, Lord Vader said: For now, you may need to trust George a little more. No chance. George has never been trustworthy! At least until the "upcomming improvements" arrive you could give us a key bind that allows us to override the AI's poor decision making wrt DTV/FLIR from the pilot seat. 1 i7-10700K @ 5Ghz | Asus Z490 Tuf Pro Gaming | RTX 3090 | 64 Gb RAM @3.6Ghz | 1TB Samsung 970 EVO+ SSD | 1TB addlink S70 M.2 SSD | 1TB Samsung 850 EVO | 4TB HDD | Reverb G2 | Thrustmaster Warthog HOTAS | Thrustmaster TPR rudder pedals | Thrustmaster Cougar MFDs
Floyd1212 Posted January 6 Author Posted January 6 7 hours ago, Specter said: At least until the "upcomming improvements" arrive you could give us a key bind that allows us to override the AI's poor decision making wrt DTV/FLIR from the pilot seat. There are a couple threads that already discuss this in more detail if you need more help, but here are the commands you want: {cockpit_device_id = 51, down = 3092, value_down = 1.0, name = _('LHG TADS Sensor Select Switch - FLIR'), category = {_('TEDAC'), _('Custom')}}, {cockpit_device_id = 51, down = 3092, value_down = 0.0, name = _('LHG TADS Sensor Select Switch - TV'), category = {_('TEDAC'), _('Custom')}},
Specter Posted January 7 Posted January 7 On 1/6/2025 at 4:39 AM, Floyd1212 said: There are a couple threads that already discuss this in more detail if you need more help, but here are the commands you want: {cockpit_device_id = 51, down = 3092, value_down = 1.0, name = _('LHG TADS Sensor Select Switch - FLIR'), category = {_('TEDAC'), _('Custom')}}, {cockpit_device_id = 51, down = 3092, value_down = 0.0, name = _('LHG TADS Sensor Select Switch - TV'), category = {_('TEDAC'), _('Custom')}}, That looks impressive, I just have no idea what you would do with those. i7-10700K @ 5Ghz | Asus Z490 Tuf Pro Gaming | RTX 3090 | 64 Gb RAM @3.6Ghz | 1TB Samsung 970 EVO+ SSD | 1TB addlink S70 M.2 SSD | 1TB Samsung 850 EVO | 4TB HDD | Reverb G2 | Thrustmaster Warthog HOTAS | Thrustmaster TPR rudder pedals | Thrustmaster Cougar MFDs
Floyd1212 Posted January 7 Author Posted January 7 1 hour ago, Specter said: That looks impressive, I just have no idea what you would do with those. Tinker at your own risk... https://forum.dcs.world/topic/301340-changing-tads-between-tv-and-flir/
Recommended Posts