Punisher74 Posted January 16, 2022 Posted January 16, 2022 For the last few months I’ve noticed that the waypoint designate button doesn’t work. It will lock onto the waypoint then instantly unlock. Causing the tax not to be able to lock onto the waypoint or target. The reticle just even when TDC depress is held long or short. I haven’t tested with an auto start, but I’ve waited for the alignment at manual startup as required. It even happens when I manually added waypoints before startup and alignment or preloaded waypoints from mission editor. Thanks, Lt. Commander Jason "Punisher" M Hardware: i7 10700K 5 GHz Quad Core, Water-cooled , 32GBs 2400 DDR4 RAM, MSI Intel Z470A GAMING MB, MSI RTX 3080 GPU W/10GBs GDDR6X, 512GB NVME.2 SSD, 1TB NVME.2 SSD, 2TB External SSD, 2 512Gb SSD's & 1 350 Gb HARDDRIVE, WinWing Orion 2 Stick Base and Throttle Base, Quest 2, Windows 11 (64bit)
fagulha Posted January 16, 2022 Posted January 16, 2022 No issues on my side. Did a test mission (with WP created in ME), selected WP designate button on MFD, used ATFLIR to lock etc, and it worked as should (not tried in MP). About carrier ops: "The younger pilots are still quite capable of holding their heads forward against the forces. The older ones have been doing this too long and know better; sore necks make for poor sleep.' PC: 14th I7 14700KF 5.6ghz | 64GB RAM DDR5 5200 CL40 XMP | Gigabyte RTX 4080 Super Aero OC 16 GB RAM GDDR6X | Thermalright Notte 360 RGB | PSU Thermaltake Though Power GF A3 Snow 1050W ATX 3.0 PCIE 5.0 / 1 WD SN770 1TB M.2 NVME + 1 SSD M.2 2TB + 2x SSD SATA 500GB + 1 Samsung 990 PRO 4TB M.2 NVME (DCS only) | Valve Index| Andre´s JeatSeat.
Cathnan Posted January 16, 2022 Posted January 16, 2022 Only played SP today but haven't had an issue. Worked for me as advertised. Since this will inevitably be asked by a mod sooner rather than later anyway, do you have a trackfile?
Punisher74 Posted January 16, 2022 Author Posted January 16, 2022 Video Evidence 1 minute ago, Cathnan said: Only played SP today but haven't had an issue. Worked for me as advertised. Since this will inevitably be asked by a mod sooner rather than later anyway, do you have a trackfile? I just recorded a video. Thanks, Lt. Commander Jason "Punisher" M Hardware: i7 10700K 5 GHz Quad Core, Water-cooled , 32GBs 2400 DDR4 RAM, MSI Intel Z470A GAMING MB, MSI RTX 3080 GPU W/10GBs GDDR6X, 512GB NVME.2 SSD, 1TB NVME.2 SSD, 2TB External SSD, 2 512Gb SSD's & 1 350 Gb HARDDRIVE, WinWing Orion 2 Stick Base and Throttle Base, Quest 2, Windows 11 (64bit)
Foka Posted January 16, 2022 Posted January 16, 2022 Works with no issues for me. Verify you key bindings, especially NWS/Undesignate, maybe you have it binded somewhere, you have pressed all the time.
Punisher74 Posted January 16, 2022 Author Posted January 16, 2022 8 minutes ago, Foka said: Works with no issues for me. Verify you key bindings, especially NWS/Undesignate, maybe you have it binded somewhere, you have pressed all the time. I just created a mission quickly and it worked fine when the weapons are preloaded. Testing when weapons are not preloaded now. Also it's not the key bindings. Thanks, Lt. Commander Jason "Punisher" M Hardware: i7 10700K 5 GHz Quad Core, Water-cooled , 32GBs 2400 DDR4 RAM, MSI Intel Z470A GAMING MB, MSI RTX 3080 GPU W/10GBs GDDR6X, 512GB NVME.2 SSD, 1TB NVME.2 SSD, 2TB External SSD, 2 512Gb SSD's & 1 350 Gb HARDDRIVE, WinWing Orion 2 Stick Base and Throttle Base, Quest 2, Windows 11 (64bit)
Swift. Posted January 16, 2022 Posted January 16, 2022 I've seen a similar intermittent bug going on with undesignation. I think in this case 'works fine for me' might not cut it to make this problem go away. This does fall under the unfortunate category of 'bugs that are almost impossible to reproduce' though 476th Discord | 476th Website | Swift Youtube Ryzen 5800x, RTX 4070ti, 64GB, Quest 2
Mikaa Posted January 16, 2022 Posted January 16, 2022 1 hour ago, Swiftwin9s said: I've seen a similar intermittent bug going on with undesignation. I think in this case 'works fine for me' might not cut it to make this problem go away. This does fall under the unfortunate category of 'bugs that are almost impossible to reproduce' though I’ve potentially encountered issues with UN-designating from a TGT point, but wasn’t sure exactly on the logic so I haven’t made any reports. Something does feel a bit buggy, but seems hard to pin down whether user error, or something broken.
Shimmergloom667 Posted January 16, 2022 Posted January 16, 2022 3 hours ago, raptorsim said: Video Evidence I just recorded a video. You really have to upload the track for that or ED wont be able to help here i7 - 9700K | 32 GB DDR4 3200 | RTX 2080 | VKB Gunfighter Mk II /w MCG Pro | Virpil T-50CM2 Throttle | TrackIR 5 | VKB Mk. IV AJS-37 | A/V-8B | A-10C | F-14A/B | F-16C | F-18C | F-86F | FC3 | JF-17 | Ka-50 | L-39 | Mi-8 | MiG-15bis | MiG-19 | MiG-21bis | M2000-C | P-51D | Spitfire LF Mk. IX | UH-1H
ED Team BIGNEWY Posted January 17, 2022 ED Team Posted January 17, 2022 Hi, I am unable to reproduce all looks good to me. Please if possible include a short as possible track replay showing the problem. thanks Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
Foka Posted January 17, 2022 Posted January 17, 2022 The undesignate function works a bit wierd. In my exprience you need to undesignate with sensor you used to designate as SOI. For example - designate target with TGP, change SOI to SA page - you can't undesignate. Move SOI to TGP and it works fine.
Cathnan Posted January 17, 2022 Posted January 17, 2022 1 hour ago, Foka said: The undesignate function works a bit wierd. In my exprience you need to undesignate with sensor you used to designate as SOI. For example - designate target with TGP, change SOI to SA page - you can't undesignate. Move SOI to TGP and it works fine. Just remembered, that it works very similare to this for me. When I designate a target with Waypoint designate, the TPOD slews there and everything works just fine. Usually I then switch to point track or simply designate from the tpod again, no problem. But if I make the SA page soi I can't undesignate. Have to switch to the TPOD to undesignate, then the rest works fine. Didn't report it because I wasn't sure if it's a bug and it was easy enough to go around. Don't think it's supposed to be like this tho. Everytime I encounter this it looks exactly like in the video.
Recommended Posts