Sandman1330 Posted December 20, 2018 Posted December 20, 2018 I'm not sure when this started, as I don't use Auto mode much. I just noticed it today, on the latest Open beta update, as I was doing some buddy lasing online for the new GBUs and needed to designate a point near the target for the auto bombing solution. In short, when trying to designate for auto bombing with the HUD, the target designator jumps all over the place and will not actually designate a location. In the video and track attached, you can see that as I change pitch, the designator moves with the HUD (note the distance to target changing). It's also jittery and all over the place. I also found designating with a waypoint caused the same issue, IF HUD WAS SOI. If HUD wasn't SOI, I could designate with a waypoint just fine and drop using an auto solution. With HUD as SOI, it is completely unusable. Am I the only one seeing this (if so, could it be a potential control issue?) *Note that in making the video, I forgot to save the track. The attached track file is not exactly from the video, but it's the same mission with the same demonstration. Another (minor) bug I came across while troubleshooting this is that, if you select A/G before you choose your fusing options in the Stores page, you still get the DUD cue. Switching to CCIP and then back to Auto seemed to fix this. (second track attached).Auto Bombing Issues.trkAuto Bombing Issues dud.trk Ryzen 7 5800X3D / Asus Crosshair VI Hero X370 / Corsair H110i / Sapphire Nitro+ 6800XT / 32Gb G.Skill TridentZ 3200 / Samsung 980 Pro M.2 / Virpil Warbrd base + VFX and TM grips / Virpil CM3 Throttle / Saitek Pro Combat pedals / Reverb G2
Sandman1330 Posted December 21, 2018 Author Posted December 21, 2018 OK, so nobody else is having this issue I presume? Ryzen 7 5800X3D / Asus Crosshair VI Hero X370 / Corsair H110i / Sapphire Nitro+ 6800XT / 32Gb G.Skill TridentZ 3200 / Samsung 980 Pro M.2 / Virpil Warbrd base + VFX and TM grips / Virpil CM3 Throttle / Saitek Pro Combat pedals / Reverb G2
StandingCow Posted December 21, 2018 Posted December 21, 2018 Mine doesn't jitter around like yours but it doesn't stay put either... so if I put it on whatever target then pull my HUD up so the marker goes off screen it pushes the marker off target as well.... it's weird. 5900X - 32 GB 3600 RAM - 1080TI My Twitch Channel ~Moo
SDsc0rch Posted December 21, 2018 Posted December 21, 2018 HUD cursor super sensitive Sent from my Nexus 5X using Tapatalk i7-4790K | Asus Sabertooth Z97 MkI | 16Gb DDR3 | EVGA GTX 980 | TM Warthog | MFG Crosswind | Panasonic TC-58AX800U [sIGPIC][/sIGPIC]
Sandman1330 Posted December 21, 2018 Author Posted December 21, 2018 Ok, so I’m not alone. Is there anyone for which this works properly? Did it just start for you guys in yesterday’s update? Ryzen 7 5800X3D / Asus Crosshair VI Hero X370 / Corsair H110i / Sapphire Nitro+ 6800XT / 32Gb G.Skill TridentZ 3200 / Samsung 980 Pro M.2 / Virpil Warbrd base + VFX and TM grips / Virpil CM3 Throttle / Saitek Pro Combat pedals / Reverb G2
Sandman1330 Posted December 21, 2018 Author Posted December 21, 2018 Solved my problem. Even though I had no drift from my TDC axis in other modules and with the Hornet radar, it seemed to be messing with the auto cue. I created huge dead zones on the axis and it seems to be working much better now. Ryzen 7 5800X3D / Asus Crosshair VI Hero X370 / Corsair H110i / Sapphire Nitro+ 6800XT / 32Gb G.Skill TridentZ 3200 / Samsung 980 Pro M.2 / Virpil Warbrd base + VFX and TM grips / Virpil CM3 Throttle / Saitek Pro Combat pedals / Reverb G2
Recommended Posts