Dave62ndFF Posted August 16, 2021 Posted August 16, 2021 Is it just me or are there some issues with the TPOD in the latest release? Problems I'm seeing at the moment include: Snowplow mode: The HUD reticle indicating where the TPOD is pointing is gone. VVSLV: Start point for the slew appears to be somewhere above the VV, again no HUD reticle. SSS not responding properly, e.g. SSS down short not cycling between AR, PT, & MT. Left short does seems to change FOV okay. Problems getting the laser selection & arming OSB buttons to work. With enough button mashing & switching in & out of the TPOD I have been able to get some weapons on target but I'm finding interfacing with the TPOD quite problematic at the moment.
Nealius Posted August 16, 2021 Posted August 16, 2021 4 hours ago, Dave62ndFF said: SSS down short not cycling between AR, PT, & MT Should be SSS aft short.
Dave62ndFF Posted August 16, 2021 Author Posted August 16, 2021 1 hour ago, Nealius said: Should be SSS aft short. Sorry I wasn't clear on that one, I did mean aft short as distinct from from down/depressing the SSS.
Recluse Posted August 16, 2021 Posted August 16, 2021 You sure you are in TPOD HOTAS mode (SSS Depress 2x) rather than INS or TV when the TPOD is up?
Dave62ndFF Posted August 16, 2021 Author Posted August 16, 2021 (edited) As a precaution I have run DCS repair and I'm still having problems. I have the TDC slew mapped to an axis on my controllers. I have attached some screenshots to illustrate some of the problems I am seeing. Harrier_Snowplow shows the absence of the HUD reticle after I have slewed the TPOD to a position near some targets. There was no HUD reticle visible while I did this. In the screenshot Harrier_OSB I have used the TDC depress/down button since the prior screenshot, zoomed in, & slewed the TDC onto a target. I tried to use SSS to cycle between AR-PT-MT without success. As such I was trying to mouse click on the associated OSB, which can be seen pressed in the screenshot, and it was not cycling. I also note in the Harrier_OSB screenshot that the coordinates in the upper right of the display are showing as zeroes. Could this be a clue to the problem? I have also attached a screenshot of the special settings I have applied for the Harrier. Could it be something to do with the INS or GYRO settings that is causing all the zeroes in the TPOD coordinates? Edited August 16, 2021 by Dave62ndFF
Dave62ndFF Posted August 18, 2021 Author Posted August 18, 2021 I have determined that the TPOD problem is somehow linked to the mission file I was using. I have a version of the mission, with an airstart, saved under an earlier version of the open beta. I loaded this up and the TPOD seemed to be working okay, the HUD reticle was back for snowplow & the TPOD was showing coordinates etc. I then went back to the version of the mission I was having trouble with, a ground start version that had a few changes and was saved under the latest open beta, and the problems returned. No HUD reticle for snowplow etc. I had loaded a TPOD, GBU-12s, and APKWS prior to takeoff. I have attached a copy of the problematic mission file. Harrier _training_1.miz
Ramsay Posted August 18, 2021 Posted August 18, 2021 (edited) 9 hours ago, Dave62ndFF said: I have attached a copy of the problematic mission file. Unfortunately the TPOD functions correctly for me (using the keyboard for TDC slew, depress, etc.). Can you attach a track file, as it'll include your options, etc. Tested using DCS Open Beta 2.7.5.10869 Edited August 18, 2021 by Ramsay i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440
Dave62ndFF Posted August 19, 2021 Author Posted August 19, 2021 15 hours ago, Ramsay said: Unfortunately the TPOD functions correctly for me (using the keyboard for TDC slew, depress, etc.). Can you attach a track file, as it'll include your options, etc. Tested using DCS Open Beta 2.7.5.10869 Thanks for giving it a go. I've made a track file, first flying toward the targets and trying to lock them up with snowplow, then switching to velocity vector slave. Unfortunately when I play it back the TPOD is out of sync with the targets. It does however show the TPOD being slewed without a HUD reticle and the coordinates being only zeroes after TDC is depressed. Harrier_TPOD_problems.trk
Dave62ndFF Posted August 19, 2021 Author Posted August 19, 2021 Fortunately this does seem to be a limited problem. Since posting the track I have tried another older mission and the TPOD worked okay. I also created another mission in Nevada, under the latest open beta build, and it seems to work okay too. But whatever went wrong with the mission file I have posted here seems to be reproduceable time after time for me.
Ramsay Posted August 19, 2021 Posted August 19, 2021 (edited) 6 hours ago, Dave62ndFF said: Fortunately this does seem to be a limited problem. I see the same problem, it seems the TPOD isn't initialised properly when using SSS "double tap" to go from DMT TV to the TPOD page (after TPOD rearming and not used/loaded previously) i.e. it doesn't generate lat/long coordinates. Closing the TPOD page OPER --> STBY and opening it again, seems to fix the problem. Tested DCS Open Beta 2.7.5.10869 Edited August 19, 2021 by Ramsay Testing suggests it only occurs after TPOD rearm i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440
Dave62ndFF Posted August 20, 2021 Author Posted August 20, 2021 18 hours ago, Ramsay said: I see the same problem, it seems the TPOD isn't initialised properly when using SSS "double tap" to go from DMT TV to the TPOD page (after TPOD rearming and not used/loaded previously) i.e. it doesn't generate lat/long coordinates. Closing the TPOD page OPER --> STBY and opening it again, seems to fix the problem. Tested DCS Open Beta 2.7.5.10869 Nice work Ramsay! It all makes sense now. I was leaning toward the mission somehow getting corrupted when I saved some changes under a different version of the open beta. The older mission I tried, where things worked okay, had the TPOD already fitted and used an airstart. The new mission I created had the TPOD already loaded via the mission editor. In the troublesome mission I was rearming with the TPOD at the beginning of the mission. It also makes sense why I sometimes managed to get weapons away after "button mashing". One of the things I would have tried was putting the TPOD into STBY and bringing it back up again. I just hadn't made the connection that it was the sequence that got things working again. Are you on the beta team/connected with the devs? If not I guess one of us should bring this to their attention using the correct forum.
Ramsay Posted August 20, 2021 Posted August 20, 2021 (edited) 4 hours ago, Dave62ndFF said: Are you on the beta team/connected with the devs No, I like helping people and it gives me little puzzles to investigate/solve while keeping current with the Harrier. Please feel free to make a bug report linking back to this thread. Edited August 20, 2021 by Ramsay i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440
Hornet81 Posted August 27, 2021 Posted August 27, 2021 @Ramsay @Dave62ndFF I've been running some tests but I am not able to reproduce it. Do you still have that issue?
Ramsay Posted August 27, 2021 Posted August 27, 2021 (edited) 2 hours ago, Hornet81 said: Do you still have that issue? Yes, I tested in the current DCS version. Main point to recreate the issue is to have a AV-8B that hasn't had the TPOD loaded or turned on. It's specific to when Sensor Select "double tap" is used to display the TPOD page and it hasn't been opened previously i.e via MPCD Menu > TGP > STBY > OPER This is a fresh mission Quote • Runway start Kobuleti (unarmed) (This is important, bug doesn't show if TPOD was preloaded in the ME) • Load up with TPOD [and optionally - GBU-38, etc.] (do NOT open TPOD's MPCD screen) • At WP2, turn to target • Select WP3 (TGT area) • Active Pause (LShift+LWin+Pause) EHSD designate WP3 • SSS aft to call up DMT LST --> DMT TV (should slave to WP) • SSS double tap to switch to TPOD MPCD page (zeroed coordinates and missing TPOD HUD Hex) • Slew TPOD with TDC to confirm issue (TPOD coord's stay at zero, HUD TPOD hex is missing, TPOD is still creating/moving designation diamond in HUD) • TPOD OPER --> STBY (initialises TPOD ? ) • TPOD STBY --> OPER • TPOD MPCD page has coordinates, HUD has TPOD hex. If at any time previous, I had called up the TPOD page on the MPCD, the TPOD would have been initialised and would have worked normally. AV-8B TPOD Initialisation Bug rpt Dave62ndFF (with Fast Forward to bug), 2_7_5_10869.trk Edited August 27, 2021 by Ramsay i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440
Dave62ndFF Posted August 27, 2021 Author Posted August 27, 2021 5 hours ago, Hornet81 said: @Ramsay @Dave62ndFF I've been running some tests but I am not able to reproduce it. Do you still have that issue? I am reliably able to reproduce this issue using the Harrier_training_1.miz file attached earlier in this thread. To do this I rearm at the beginning of the mission adding a TPOD and some GBU-12s or similar to use with the TPOD. If I then try to activate the TPOD, using SSS double depress when approaching a target, I experience the issues of no HUD reticle when slewing in snowplow, zeroed coordinates after TDC depress etc. Using the workaround Ramsay found, switching the TPOD to standby then bringing it back up again, gets the TPOD working normally.
Recommended Posts