Nate Kott Posted October 26, 2022 Posted October 26, 2022 I'm a relatively new F/A 18C pilot and I've been having a lot of trouble with designating targets for use with the AUTO bombing mode. I'm not sure what the issue is but I can't find anything in the manual that suggests what I might be doing wrong. The issue I have is that when I designate a target with the JHMCS (or with the velocity vector) for bombing the targeting bug will move relative to the airframe unless I switch the sensor designate switch to another input. By habit I move it down, but left, right, or down will all work. I've messed with the TDC slew to give a large deadzone and the TDC is not set on the realistic setting (I noticed no difference when I tried it on realistic). I've tried setting up a macro in joystick gremlin to automate resetting the sensor designator immediately but that didn't really work effectively. I've also tried using the enter key on the keyboard rather then the mini-stick on the throttle (Virpil CM3 if it matters by way of Joystick Gremlin) and that didn't make any difference either. I have the same issue in VR as well as with a head tracker. The video below was taken with a head tracker. It seems unlikely this is how it is supposed to work since the movement of the bug makes using the TDC slew incredibly awkward. I should add I used the instant action - target practice because it was quick and easy to show the issue. I've had the same issue in the tutorial missions and other downloaded missions.
Archer.xd Posted October 26, 2022 Posted October 26, 2022 I used this method with TGP one or two weeks ago and didn't have any issue. Commenting here so I wont forget and can test further later today.
Tholozor Posted October 26, 2022 Posted October 26, 2022 Initial suggestion I would have is to verify that no other axes are assigned to the TDC, or try un-assigning the TDC axes and have nothing bound to it to ensure it's not a TDC problem. REAPER 51 | Tholozor VFA-136 (c.2007): https://www.digitalcombatsimulator.com/en/files/3305981/ Arleigh Burke Destroyer Pack (2020): https://www.digitalcombatsimulator.com/en/files/3313752/
Nate Kott Posted October 26, 2022 Author Posted October 26, 2022 Just double checked. There are no axis assigned to the TDC slew other than the mini-stick on the throttle.
Archer.xd Posted October 26, 2022 Posted October 26, 2022 Tested now, I don't have the issue. Moves only if I move my TDC slew
AstonMartinDBS Posted October 26, 2022 Posted October 26, 2022 Already tested without any issues on the current OB. Are you using the Stable version @Nate Kott? Pls share a track instead of a video, if you can reproduce the issue. [Modules] A-10C, A-10C II, AH-64D, F-4E, F-14A/B, F-16C, F/A-18C, FC3, Ka-50, P-51D, UH-1H, CA, SC [Maps] PG, NTTR, Normandy, Sinai, Syria, TC [OS] Windows 11 Pro [PC] MSI Pro Z790-A, i9-13900K, 128 GB DDR5, RTX 4090 24 GB GDDR6X, 2 x SSD 990 PRO 2 TB (M.2), Corsair 5000D Airflow, HX1500i, H150i RGB Elite, Acer X28, TM HOTAS Warthog (Grip@WarBRD Base), MS SW FFB2, Thrustmaster TFRP, TrackIR 5 & TrackClip Pro [Checklists] A-10C, F-16C, F/A-18C, AH-64D, Ka-50, UH-1H
Nate Kott Posted October 26, 2022 Author Posted October 26, 2022 I fly in the Open Beta (on the Steam version if it matters) but I'm pretty sure that isn't the issue. The track for another similar flight is attached that also has the issue. I happened to notice when I was trying to make the track that Joystick Gremlin crashed. And for a minute the designator worked as intended. I can't replicate that except that if I leave no axis assigned to the TDC. If I have no axis assigned to the TDC the designator cue is fixed and works as I would expect. Otherwise, the problem resurfaces. I tried setting a deadzone in the DCS axis tune but that didn't help. I also tried to make the axis input conditional in Joystick Gremlin to be sure that there was no axis input to DCS. That didn't work either only unmapping those axis stops the problem. Having no axis assigned to the Throttle Designator Controller HORIZONTAL and VERTICAL seems to make the problem go away. Am I mapping the wrong thing (screen shot with a circle on axis I had been mapping)? The weird part is the ministick works perfectly fine for the MFD displays I can lock up A/A targets without a problem. JHMC Issue.trk
Solution Nate Kott Posted October 28, 2022 Author Solution Posted October 28, 2022 (edited) After some more testing, I'm certain the issue is the interaction between vJoy and DCS. In case anyone else runs into this issue, I actually got it to go away. They way I did was to attach an old joystick (T16000) and map the x and y axis of that old joystick to the TDC Slew (I've preferred to keep my joysticks directly hidden from DCS and just use remapped vJoy virtual joysticks so DCS doesn't directly see my Virpil Throttle). This both made the TDC Slew work and made it so the target designator didn't move. But it would have been incredibly awkward to use. To my amazement when I remapped the TDC slew to the original vJoy axis it suddenly worked. It continued to work after I shut down and restarted both Joystick Gremlin and DCS and it continued to work. So if you have a similar setup hidHide -> Joystick Gremlin -> vJoy and have this issue try mapping the TDC Designator Controller directly to an x and y axis and see if that makes the problem go away. EDIT: with the recent update the problem happened again. Tried this fix and it didn't work until I put the curve and deadzone back in. I had tried setting the curve and deadzone in joystick gremlin and that doesn't seem to work. But with a deadzone of 10 in DCS itself the TDC slew and targeting bug went back to working. I still suspect it is an issue with vJoy virtual sticks specifically. Edited October 31, 2022 by Nate Kott Fix was different than I thought but it is still fixed. 1
Recommended Posts