JupiterJoe Posted July 4, 2024 Posted July 4, 2024 (edited) Bug: Auto-throttle disengaged warning light not illuminating. Can I reproduce it 100%: Yes If not 100%, how often out of 10: 9 How to reproduce/ description: Step1: Engage ACLS and activate auto-throttle. Step2: Manually over-ride auto-throttle. DCS Version: 2.9.5.55918 M/T System Specs: Processor Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz 3.70 GHz Installed RAM 64.0 GB Device ID 36C95E96-CEE8-4C82-AF93-9730F33AFFDB Product ID 00330-80000-00000-AA169 System type 64-bit operating system, x64-based processor Windows 11 Pro NVDIA GEFORCE RTX 3070 Peripherals: Joystick: Thrustmaster T-Flight Stick X Throttle: Virpil Controls T-50 CM3 Headtracker: Third-party Track IR Mission File: Instant Action: F-14A Carrier Quals - Marianas. Track: Please ignore first pass. The second pass demonstrates taking manual control of the throttle and the auto-throttle disengaged light not illuminating. It should also be noted that FFB ceases to work properly if you switch aircraft. A full restart is required. auto throttle test no ffb.trk Edited July 18, 2024 by JupiterJoe 1 Intel Core i7-8700K CPU @ 3.70GHz - 64GB RAM - Nvidia GeForce RTX 3070 - Microsoft Sidewinder Force-feedback 2 - Virpil Mongoose CM-3 Throttle
Q3ark Posted July 4, 2024 Posted July 4, 2024 AFAIK the light will only illuminate if the system disengages the auto throttle. If it’s done by the pilot either with the switch or by taking over the throttle it doesn’t come on. It’s to warn of an uncommanded disengagement. 1
JupiterJoe Posted July 4, 2024 Author Posted July 4, 2024 (edited) 10 hours ago, Q3ark said: AFAIK the light will only illuminate if the system disengages the auto throttle. If it’s done by the pilot either with the switch or by taking over the throttle it doesn’t come on. It’s to warn of an uncommanded disengagement. Yes, but this video seems to show it working as intended. In this example, as Cap traps and goes to full a/b he's manually over-riding the AT and the light comes on. You obviously wouldn't just need that warning light when you've landed, but on approach, to give the pilot a chance to react, especially at night, or in fog, when you'd need to know in a hurry if you've accidentally knocked the throttle out of AT. At the moment I can't get the warning to illuminate by any means. Hence I suspect a bug. Edited July 5, 2024 by JupiterJoe Intel Core i7-8700K CPU @ 3.70GHz - 64GB RAM - Nvidia GeForce RTX 3070 - Microsoft Sidewinder Force-feedback 2 - Virpil Mongoose CM-3 Throttle
draconus Posted July 5, 2024 Posted July 5, 2024 (edited) 11 hours ago, Q3ark said: AFAIK the light will only illuminate if the system disengages the auto throttle. If it’s done by the pilot either with the switch or by taking over the throttle it doesn’t come on. That's not what NATOPS say. 10 hours ago, JupiterJoe said: video seems to show it working as intended It shows only one of the interlocks working - disengaging the AT with Weight On Wheels and then showing the warning correctly. I have yet to test this one in current DCS version. Edited July 5, 2024 by draconus 1 Win10 i7-10700KF 32GB RTX4070S Quest 3 T16000M VPC CDT-VMAX TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria
Q3ark Posted July 5, 2024 Posted July 5, 2024 2 hours ago, draconus said: That's not what NATOPS say. Fair enough, I’ve never read the NATOPS, I’m one of those men that don’t read instructions 2
draconus Posted July 9, 2024 Posted July 9, 2024 (edited) On 7/5/2024 at 9:28 AM, draconus said: I have yet to test this one in current DCS version. I failed to reproduce. I trapped F-14B with Auto Throttle and ACLS on and upon touchdown there was no AUTO THROT warning light triggered. Btw: the GR video is from 2019. Edited July 9, 2024 by draconus Win10 i7-10700KF 32GB RTX4070S Quest 3 T16000M VPC CDT-VMAX TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria
JupiterJoe Posted July 10, 2024 Author Posted July 10, 2024 22 hours ago, draconus said: I failed to reproduce. I trapped F-14B with Auto Throttle and ACLS on and upon touchdown there was no AUTO THROT warning light triggered. Btw: the GR video is from 2019. What do you mean you failed to reproduce? You failed to reproduce the bug, or what happens in the video? It's supposed to illuminate under the circumstances depicted in the video, isn't it? Therefore the bug stands. Intel Core i7-8700K CPU @ 3.70GHz - 64GB RAM - Nvidia GeForce RTX 3070 - Microsoft Sidewinder Force-feedback 2 - Virpil Mongoose CM-3 Throttle
draconus Posted July 10, 2024 Posted July 10, 2024 22 minutes ago, JupiterJoe said: What do you mean you failed to reproduce? You failed to reproduce the bug, or what happens in the video? It's supposed to illuminate under the circumstances depicted in the video, isn't it? Therefore the bug stands. Yes, the bug stands - it's still wrong in current DCS. I replied to my post where I promised to test the conditions from the video. 1 Win10 i7-10700KF 32GB RTX4070S Quest 3 T16000M VPC CDT-VMAX TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria
Recommended Posts