dadunn1700 Posted February 24, 2023 Posted February 24, 2023 (edited) Tried hoping into the free flight with the F-16 with DCS 2.8.2.35759 (current Beta version) and the autopilot will not activate. If I flip the switch in the cockpit to "altitude hold" it will not stay fixed and not activate. I'm at 10,000 ft moving at 300 knots and flying level, but still will not activate even after spawning into a clean F-16 already in flight. HOTAS: RealSim FSSB R3 Stick and Base WinWing Orion 2 w/ F-16 Throttle Grip Saitek Pro Flight Rudder Pedals TrackIR 5 Edited February 24, 2023 by dadunn1700
Solution Furiz Posted February 24, 2023 Solution Posted February 24, 2023 (edited) 4 hours ago, dadunn1700 said: Tried hoping into the free flight with the F-16 with DCS 2.8.2.35759 (current Beta version) and the autopilot will not activate. If I flip the switch in the cockpit to "altitude hold" it will not stay fixed and not activate. I'm at 10,000 ft moving at 300 knots and flying level, but still will not activate even after spawning into a clean F-16 already in flight. Hi, Check if your TRIM/AP DISC Switch (Manual Trim Panel on the left side) is set to Norm, if it is set to DISC the Auto Pilot will disconnect since your Trim control is disconnected. also check if you have some of the switches bound to it and they are making it go to DISC. That is the usual suspect. Edited February 24, 2023 by Furiz 1
dadunn1700 Posted February 25, 2023 Author Posted February 25, 2023 20 hours ago, Furiz said: Hi, Check if your TRIM/AP DISC Switch (Manual Trim Panel on the left side) is set to Norm, if it is set to DISC the Auto Pilot will disconnect since your Trim control is disconnected. also check if you have some of the switches bound to it and they are making it go to DISC. That is the usual suspect. Thanks man. I thought I had checked everything but I found out what it was. I had mapped the refueling bay to a switch on my throttle somehow and I was spawning into the aircraft with the refueling bay open or opening immediatly during startup. Thats why the autopilot wouldn't turn on, and hopefully also why i kept getting "trip fuel" warnings. Should have noticed the blue "RDY" warning light for the refuel door. 1
Furiz Posted February 25, 2023 Posted February 25, 2023 (edited) That would be my second guess, glad you found the problem. Thought the fuel issue was a separate issue Edited February 25, 2023 by Furiz
dadunn1700 Posted February 26, 2023 Author Posted February 26, 2023 (edited) 8 hours ago, Furiz said: That would be my second guess, glad you found the problem. Thought the fuel issue was a separate issue One other question before I make a separate post. Do you know of any bugs with the HTS/HAD? Don't remember ever having these issues and figured I'd ask before making a separate post. Spawn in a clean f-16 re-arm with HTS and Harms re-arming complete Startup jet/ takeoff Power up HARMs Power up HTS hardpoint station Nothing detected on HAD despite being launched on from 10 thru to 2 oclock. Edited February 26, 2023 by dadunn1700
Furiz Posted February 26, 2023 Posted February 26, 2023 (edited) 3 hours ago, dadunn1700 said: One other question before I make a separate post. Do you know of any bugs with the HTS/HAD? Don't remember ever having these issues and figured I'd ask before making a separate post. Spawn in a clean f-16 re-arm with HTS and Harms re-arming complete Startup jet/ takeoff Power up HARMs Power up HTS hardpoint station Nothing detected on HAD despite being launched on from 10 thru to 2 oclock. HTS scans for each class of SAM, that scan takes some time so the reason it didn't detect anything is probably short amount of time, you can select which threats it scans for. On the HAD in the upper row there is a THRT button, click it and select which classes of SAM you want it to look for to decrease the amount of time it scans for a specific SAM type. If you select only one type it will scan for it more often. There are ALIC tables for SAM threats in the download section on the website like: https://www.digitalcombatsimulator.com/en/files/3312295/ Edited February 26, 2023 by Furiz
dadunn1700 Posted February 26, 2023 Author Posted February 26, 2023 (edited) 8 hours ago, Furiz said: HTS scans for each class of SAM, that scan takes some time so the reason it didn't detect anything is probably short amount of time, you can select which threats it scans for. On the HAD in the upper row there is a THRT button, click it and select which classes of SAM you want it to look for to decrease the amount of time it scans for a specific SAM type. If you select only one type it will scan for it more often. There are ALIC tables for SAM threats in the download section on the website like: https://www.digitalcombatsimulator.com/en/files/3312295/ I'll give that a shot. I was aware of limiting the threat scanning if you are using the HARM as the sensor on the "WPN" mfd page as there is a clearly seen refresh rate based on the number of threats it's scanning for and the width of the scan, but I was unaware this was necessary for the HAD. Must be a new thing since the last I played. In the past, and in BMS, the HAD simply picked up everything rather quickly with no filtering required. Edited February 26, 2023 by dadunn1700 1
dadunn1700 Posted February 26, 2023 Author Posted February 26, 2023 (edited) 11 hours ago, Furiz said: HTS scans for each class of SAM, that scan takes some time so the reason it didn't detect anything is probably short amount of time, you can select which threats it scans for. On the HAD in the upper row there is a THRT button, click it and select which classes of SAM you want it to look for to decrease the amount of time it scans for a specific SAM type. If you select only one type it will scan for it more often. There are ALIC tables for SAM threats in the download section on the website like: https://www.digitalcombatsimulator.com/en/files/3312295/ Still having the same issue if I re-arm and takeoff. I got the HAD to work if I spawned into an already flying jet with the HAD equipped, but not if I have it armed before cold start. Oddly enough I found out the HAD, in the cold start situation, is picking up signals, but the symbiology isn't appearing on the MFD. If I hover my TDC around I can pick up invisible search radars to lock on to. I'm uploading a track file. HAD not working.trk PS. Think I will report this as a separate issue since I do think this is a bug. Edited February 26, 2023 by dadunn1700
Recommended Posts