Scotflieger Posted May 22, 2021 Posted May 22, 2021 When attempting to designate a Waypoint with WPDDSG the point moves to a position in front of the aircraft and the LITENING pod slews to this point instead of the waypoint position. In these screenshots the waypoint is off to starboard and move in 17NM in front of aircraft. This has changed in the latest Open Beta release 2.7.126430.
zildac Posted May 22, 2021 Posted May 22, 2021 Same as this issue: 1 14900KS | Maximus Hero Z690 | ASUS 4090 TUF OC | 64GB DDR5 6600 | DCS on 2TB NVMe | WarBRD+Warthog Stick | CM3 | TM TPR's | Varjo Aero
Scotflieger Posted May 23, 2021 Author Posted May 23, 2021 (edited) This track file (deleted/incomplete - see below) shows the problem (link used as track file too large to upload 44MB). Test flown in Multiplayer with LITENING, 2 x MAVF, 4 x JDAM. Target near WP2. Selected weapon JDAM in TGT TOO. On first attack with target to left of track, WPDSG worked as expected and FLIR slewed to WP. On second run, again abeam of target. deselecting TGT and then WPT plus WPDSG places TGT ahead of aircraft along track. Test terminated immediately after this event. Edited May 25, 2021 by Scotflieger
Mikeck Posted May 24, 2021 Posted May 24, 2021 Have the Same issue. Waypoint designate will bit slew the TGP pod and instead “creates” the target point in front of the Aircraft. Apparently the problem resolves if you switch TGP to another MFD and back? No track file but looks like someone above posted
Scotflieger Posted May 25, 2021 Author Posted May 25, 2021 (edited) Above linked file failed to include full details due to 10 minute record delay on Multiplayer server. This track file does cover the problem. File size 60MB. Open beta 2.7.1. Test flown in Multiplayer with LITENING, 4 x JDAM, 1 x HARM and 1 x AGM65F. Target near WP2. After take off selected JDAM in TGT TOO mode. FLIR slewed to correct target which was attacked with JDAM followed by HARM in self-protection mode. Turned to west and deselected WP2. Reselected WP2 steer and WPDSG pressed. Target appeared in front of aircraft with in-range circle. Tried this twice with same fault. Used Sensor Control to select HUD as primary display. Repeated WP2 reselection and designation. Target set correctly to WP2. This is the workaround reported by others. Got shot down and waited 12 mins before terminating mission to ensure correct recording. Edited May 25, 2021 by Scotflieger
MarcT-NL Posted May 25, 2021 Posted May 25, 2021 I'm not sure if this is related, but I noticed that when you carry GPS-guided bombs, and they are populated with coordinates, then that has become your target-point. Don't know if that is "correct as is". But try to deselect the JDAMS and then try again.
Scotflieger Posted May 25, 2021 Author Posted May 25, 2021 34 minutes ago, MarcT-NL said: I'm not sure if this is related, but I noticed that when you carry GPS-guided bombs, and they are populated with coordinates, then that has become your target-point. Don't know if that is "correct as is". But try to deselect the JDAMS and then try again. The problem appears whether or not the weapon selected. It is the selection of the navigation waypoint and its designation as the target where things have changed in 2.7.1.
VIXEN413 Posted May 25, 2021 Posted May 25, 2021 can reproduce too 1 Rig: MB Gigabite z390UD, CPU Intel I7 8700k, RAM 32G DDR4 3200 Gskill ripjaws, GPU MSI RTX2080SuperOC, HDD Crucial mx500 1tb M2 sata, PSU Corsair 850W, watercooling Corsair h100, Controlers TM f/a 18 stick on Virpil warbrd base, TM cougar f16 stick on cougar base, Cougar F16 throttle on TUSBA, ch pedals, TM cougar MFD 27" monitor with trk IR 5 and HP Reverb HMD. Modules F18, F16, F86, Mig15, FW 190D9, Nellis range map, Aggr campaign, Middle East map
Silverfox275 Posted May 26, 2021 Posted May 26, 2021 (edited) I'm having the exact same issues. It seems to happen after my first bombing run. On the initial mission the TGP will slew to the targeted waypoint as it should. After returning to the airfield for rearm and refuel, the TGP doesn't seem to want to work correctly. Whenever i try to designate it to the next waypoint by pressing the WPDSG button it will designate a location a few miles out in front of my aircraft. I can break the lock and re-designate targets with the Helmet system and all seems to work until I want to re-designate the actual WP itself as the target area. So far I've had this happen in the Nevada map and the Syria map Edited May 26, 2021 by TNgamer1973
GazAce Posted May 26, 2021 Posted May 26, 2021 Exactly the same issues here with both ATFLIR & LITENING. Thanks for posting GazAce's "Skynet Rig" :: :: 13th Gen Intel Core i9-13900K :: Asus ROG Strix Z790-A Mobo :: Nvidia GeForce RTX 4090 MSI Gaming Slim GPU 24GB :: NZXT Kraken Elite 280 RGB AIO White Cooler :: G Skill Trident Z Royals DDR4 4x16GB = 64GB :: WD Black SN 850X NVMe SSD 2TB M.2 (C Drive) :: Samsung 860 Pro 2TB SATA (D Drive) & a couple of other Drives adding another 1.5 TB :: Corsair Crystal 680X White Case :: Asus XG349C 34" Curve G-Sync 180Hz 3440x1440 Monitor :: MSI 1000 Watt PSU PCIE5 :: Virpil Constellation Alpha-R Stick with VPC WarBRD Base :: Virpil MongoosT-50CM3 Throttle :: 3 x CubeSim ext mini screens with TM Cougar MFD Bezels :: Asus ROG Pugio 503 Gaming Mouse & Razer BlackWidow mech kb :: TrackIR 5 Pro & Cap Clip :: Win 11 64 Bit
Gierasimov Posted May 26, 2021 Posted May 26, 2021 Track file must be short and in single player to play back more less correctly. I tried to reproduce but had no luck so far. Will try again. Intel Ultra 9 285K :: ROG STRIX Z890-A GAMING WIFI :: Kingston Fury 64GB :: MSI RTX 4080 Gaming X Trio :: VKB Gunfighter MK.III MCG Ultimate :: VPC MongoosT-50 CM3 :: non-VR :: single player :: open beta
ED Team BIGNEWY Posted May 26, 2021 ED Team Posted May 26, 2021 please include a short track replay showing the issue. 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
Gierasimov Posted May 26, 2021 Posted May 26, 2021 1 hour ago, BIGNEWY said: please include a short track replay showing the issue. Hi @BIGNEWY - this track cannot be as short as always, due to the fact that this issue is reproducible only after rearming. So, on my first test attempt I flown the mission - (air start) and I was able to designate and have targeting pod looking at correct spot (Waypoint 2), then landed at friendly airbase, rearmed, changed the pod, in the air I turned on the TGP and Waypoint 2 designation is not correctly passed to the pod. In the attached track: 1.Air start on final to Incirlik - I am able to auto slew my pod to waypoint 2 (via HSI pushbutton) 2. Land and rearm & refuel 3. Take off and wait for the pod to come online. 4. Use HSI WPDSG to designate waypoint 2 - no luck, pod looks ahead - however I noticed also, 5. Designate spot in the ground with the pod - then undesignate, then use HSI to designate waypoint WPDSG and the pod slews to the spot which it previously had designated. 6. Undesignate, have the pod to follow velocity vector, use HSI to designate waypoint 2 - pod looks ahead. I tried to keep the track as short as possible, but had to land for rearm otherwise not able to replicate. atflir weapon dsg.trk Intel Ultra 9 285K :: ROG STRIX Z890-A GAMING WIFI :: Kingston Fury 64GB :: MSI RTX 4080 Gaming X Trio :: VKB Gunfighter MK.III MCG Ultimate :: VPC MongoosT-50 CM3 :: non-VR :: single player :: open beta
ED Team BIGNEWY Posted May 26, 2021 ED Team Posted May 26, 2021 Thanks this has been reported 1 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
Recommended Posts