Maulkin Posted February 12, 2018 Posted February 12, 2018 Before the 2.5 merge I recall the targeting pod had some limited functionality where I could lock a target and lase it. But now I cannot control this thing at all since the move of the OpenBeta to 2.5. Is anyone else experiencing this? (yes I know this is a beta and I do expect things to not work. I just want to make sure I don't have a corrupted module) --Maulkin Windows 10 64-bit - AMD Ryzen 9 5900X @ 3.7 GHz - 32 GB DDR4 3600MHz RAM - EVGA FTW3 RTX 3080 - Asus Crosshair VIII Hero motherboard - Samsung EVO Pro 1 TB SSD - TrackIR 4 Pro - Thrustmaster Warthog - Saitek rudder pedals - Lilliput UM-80/C with TM Cougars
feefifofum Posted February 12, 2018 Posted February 12, 2018 TGP is still behaving fine for me, known missing features notwithstanding. I am able to control zoom, slew the TDC, switch between wide/narrow FOVs and lase targets. THE GEORGIAN WAR - OFFICIAL F-15C DLC
drPhibes Posted February 12, 2018 Posted February 12, 2018 Same here. I Spent most of the day yesterday lasing and dropping GBU-12s, so it definitely works. Try running a repair using the dcs_updater application.
Ruebban Posted February 12, 2018 Posted February 12, 2018 Is it just me that have to change the laser code to be able to get the GBU's to aim up? Otherwise it works okay.
drPhibes Posted February 12, 2018 Posted February 12, 2018 If you start a mission with the pod and GBUs loaded you can use the pre-set 1111 code, but if you add the pod and bombs through the rearm&refuel dialog, you need to change the code to something (otherwise 1111 will just keep flashing, like when you are on the ground).
Raz_Specter Posted February 13, 2018 Posted February 13, 2018 yep TPOD and DMT is working fine for me. Custom built W10 Pro 64Bit, Intel Core i9 9900k, Asus ROG Maximus Code XI Z390, 64GB DDR4 3200 RGB, Samsung 1TB NVme M.2 Drive, Gigabyte AORUS 2080TI, 40" Iiyama Display. Wacom Cintiq Pro 24, HOTAS Virpil T50 Stick / FA-18C TM Stick and Virpil T50 Throttle, MFG Crosswind Graphite Pedals. HP Reverb SPECTER [sIGPIC][/sIGPIC] Lead Terrain Developer / Texture Artist
401TIGGER Posted February 13, 2018 Posted February 13, 2018 Works great for me now as well. TiGGs sends Deadlines..... I love the sound when they go whooshing by..... Windows 10 Pro w WARTHOG HOTAS and Crosswinds MFG Pedals; i7 9700 @ 3.8GHz, Asus, 16 GB RAM; NVidia GTX 2070 GDDR5x VRam11Gb; 500Gb SSD; Oculus Rift S and a partridge in a pear tree :punk:
Zeus67 Posted February 13, 2018 Posted February 13, 2018 If you start a mission with the pod and GBUs loaded you can use the pre-set 1111 code, but if you add the pod and bombs through the rearm&refuel dialog, you need to change the code to something (otherwise 1111 will just keep flashing, like when you are on the ground). Folks, the flashing laser code indicates an internal error condition in which the displayed code and the laser designator code are not the same. That should not happen. To fix this, try changing the laser code. Please indicate me when you get the flashing code condition so I can track this bug and squash it. Thanks in advance. "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." "The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."
drPhibes Posted February 13, 2018 Posted February 13, 2018 The flashing stops after changing the code (when airborne). The fault does not reappear after subsequent rearm and refuel cycles; it only happens the first time the TPOD is added.
401TIGGER Posted February 13, 2018 Posted February 13, 2018 LCODE The flashing stops after changing the code (when airborne). The fault does not reappear after subsequent rearm and refuel cycles; it only happens the first time the TPOD is added. Concur w above. I have Zero issues after changing. TiGGs sends Deadlines..... I love the sound when they go whooshing by..... Windows 10 Pro w WARTHOG HOTAS and Crosswinds MFG Pedals; i7 9700 @ 3.8GHz, Asus, 16 GB RAM; NVidia GTX 2070 GDDR5x VRam11Gb; 500Gb SSD; Oculus Rift S and a partridge in a pear tree :punk:
Recommended Posts