Nate Kott

I've been having the same issue when I tried the new train strafe missions. I checked it with the warbirds I fly regularly and I couldn't damage the train with the p51, p47, or the Spitfire for the Normandy instant action mission. The Channel map version didn't work either (though I only tested the p47). However the Caucases version worked just fine. When I checked the debrief DCS did not register any rounds on target. I'm pretty sure at least a few rounds were on target. Train Strafe Normandy p47.trk Train Strafe Normandy p51.trk Train Strafe Normandy spitfire.trk Train Strafe Caucasas p47.trk Train Strafe Channel p47.trk

Update: tried this with EDGE 2.9. It's better than it was before, but I only consider it barely playable on my system. Mission I tried was mission 6 and the frames frequently dropped into the single digits. I was able to complete the mission but the frames were bad enough that accurate strafing or bombing wasn't really possible.

I was dubious, but the force feedback issue was absolutely correct for me. I guess that got set by default when I switched from the Steam version to standalone. When I unchecked it elevator trim started working again immediately.

I have this issue as well. Best I can recall it started somewhat recently. Weirdly it affects all of the allied warbirds I've tried but insofar as I can tell only pitch trim. Aileron and rudder trim both work as expected. I've tried the Spit, 51 and 47 and they all seem to have the same issue. I use VKB stick through joystick gremlin. I have also tried directly using keypresses, remapping joystick presses to the joystick buttons, and remapping a joystick axis to the trim wheel. In all cases, you can watch the pitch trim wheel spin (or the indicator in spit) and there is no effect on the actual flight trim of the plane. Mission was free flight on Normandy instant action. Elevator Issue.trk

I just wanted to drop a note and say that this mission is incredibly helpful for practicing. Much better for practice than the training mission in the FA-18 module.

Same as the others. With AI on screen the game stutters quite badly but the missions seem to load in and run. I did run into some bad AI on the first command post bombing mission. Ordered them to attack primary target and they just went of gallivanting across the French countryside. But otherwise the only issue is the stuttering which is quite bad. AMD Ryzen 9 5950X 16-Core 3.40 GHz and an RTX 3080. Also in VR (Valve Index).

For the drifting target issue: I had a similar issue that went away when I set a deadzone of 10 on the ministick bind for the TDC.

I'll try that. Yeah I'm not sure really what is causing the DCS order to get screwy it well could be a windows change triggering it.

I've always used Joystick Gremlin and vJoy to map controls in flight sims but it seems every time there is a DCS update then DCS gets all the bindings mixed up. DCS shuffles the vJoy devices and invariably assigns the binds to the wrong one. The binds are all there just set to the wrong vJoy device. Since I've been trying out modern planes lately this is a royal pain. I have a mix of devices if it matters, VKB stick; Virpil throttle; and crosswind pedals. I still prefer using Joystick Gremlin since I'm used to it and know how it works. Has anybody had a similar issue? Has anybody had success saving the binds and reloading them after an update? I don't want to go through re-mapping everything to lose them again I'd be concerned that DCS would still attribute them to the wrong vJoy device. Tbh I haven't tried that yet because I just started flying modern aircraft recently and warbirds are not really a big deal to rebind. Or do I need to switch to relying primarily on the DCS internal keybinding assignments?

Digitalvole, I'm seeing the same thing. Seems like every other time I spawn in SteamVR crashes. It seems to be specific to DCS I don't have this with the other VR titles I played (including IL2). Might have to put down DCS until they sort out VR. It's kind of rage inducing to get through putting in your waypoints on a server and then have DCS cause SteamVR to crash.

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.

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

Just double checked. There are no axis assigned to the TDC slew other than the mini-stick on the throttle.

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.