stoop Posted November 2, 2022 Share Posted November 2, 2022 Since today's update I went to F10 and have tried both using T01, T02 ... and TP1, TP2 etc WITHOUT setting a blank marker first, but then none of them come into the kneeboard when I Right Shift-Right Alt - 8 Link to comment Share on other sites More sharing options...
stoop Posted November 2, 2022 Author Share Posted November 2, 2022 Do you need to include the # ahead of the TP designation? Link to comment Share on other sites More sharing options...
AlphaJuliet Posted November 3, 2022 Share Posted November 3, 2022 yup, like #TP1, #TP2... 1 Link to comment Share on other sites More sharing options...
stoop Posted November 3, 2022 Author Share Posted November 3, 2022 Nope still didn't work when I named them such but still couldn't bring them into the aircraft. Link to comment Share on other sites More sharing options...
Recluse Posted November 4, 2022 Share Posted November 4, 2022 A .trk would be helpful. It works fine for me. I have used it extensively since the patch and hotfix. Link to comment Share on other sites More sharing options...
Adrian858 Posted November 20, 2022 Share Posted November 20, 2022 After neglecting the Harrier for a while, I decided to do some re-familiarization today with the recent updates. Had the exact same issue. After putting in map markers labeled #TP1, 2, 3, etc and trying to transfer them using Right Shift - Right Alt - 8, nothing happens. Double checked keybindings, process, and did everything correctly. Corsair Vengeance C-70 (OD), EVGA Z370 FTW, i7-8700k, Noctua NH-D15, RTX 4070ti TUF OC, Corsair Vengeance LPX 64GB DDR4 3200MHz, Samsung SSD 970 Pro NVMe M.2 1TB & 990 Pro NVMe M.2 2TB , WD Black 4TB Perf HDD - 7200 RPM SuperNOVA 750W P2 Modular, ASUS ROG Swift 27" 2560x1440 TM Warthog, TM F/A-18C Grip, Virpil CM3 Base, Virpil Control Panel 1, TM Pendular Rudder Pedals, WinWing Take Off Panel, Cougar MFD's, TekCreations F/A-18C Master Arm, Koolertron Keypad, Meta Quest 3 A-10C/II - AH-64D - AV-8B - F-5E - F-14 - F-15E - F-16C - F/A-18C - P-51D - Bf-109K4 - FC3 - UH-1H - Combined Arms - Super Carrier Nevada - Normandy - Persian Gulf - Sinai - Syria Link to comment Share on other sites More sharing options...
Ramsay Posted November 21, 2022 Share Posted November 21, 2022 50 minutes ago, Adrian858 said: After neglecting the Harrier for a while, I decided to do some re-familiarization today with the recent updates. Had the exact same issue. After putting in map markers labeled #TP1, 2, 3, etc and trying to transfer them using Right Shift - Right Alt - 8, nothing happens. Double checked keybindings, process, and did everything correctly. Although the ATHS map markers (#TP01, #TP02, etc.) transfer to the CAS Recall page with "RS+RA+8", they won't be listed on the kneeboard until assigned Target Points. Not sure if it's WIP or an intended behaviour but it is know by Razbam. Tested DCS Open Beta 2.8.0.33006 1 i9 9900K @4.7GHz, 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 10 Pro x64, 1920X1080 Link to comment Share on other sites More sharing options...
Recluse Posted November 21, 2022 Share Posted November 21, 2022 (edited) If you do it on the GROUND the Target points are Auto Assigned. If you do it in the AIR, you need to assign Target Points with the USE OSB, and select a Target point number on the UFC. It might be those points that aren't assigned yet that are giving the error, but, I don't recall ever seeing that error. Possibly because there is a mix of Assigned and un-assigned points. Not sure. Edited November 21, 2022 by Recluse Link to comment Share on other sites More sharing options...
Recommended Posts