FusRoPotato

I haven't had any issues with the Su-25T other than sometimes not being able to drop single dumb bombs at a time. It drops them all when in SGL/2 mode. I've got a video of the A-10A weapon switching issue

Actually found some footage of sharp rolls with AMRAAMS loaded on the wingtips.

I'm not reporting a wing flex issue, I'm reporting a wing twist issue. There's a difference. It's a separate problem that was not mentioned in that thread. Luckily the fix should be much easier. The direction just needs to be negated for each wing animation. They are simply backwards.

I have a 100% reproducibility rate with this A-10A issue. I'll try to get a video next time I'm home, but I don't have any idea yet how to narrow down the factors on what's causing this. Happens in both single player and multiplayer, and this is a relatively fresh install that I just -repaired yesterday. As for salvo mode, this is the issue. Some of the planes are locked with salvo mode on. Some, like the J-11, I can fire s-25 rockets off individually. With the Su-33 on the other hand, I am forced to fire them all at once. This includes bombs as well. If I load up several racks with dumb bombs, it will release all of them at the same time! lol that's never how they functioned in practice and is impossible to set them up that way. The quantity and timing has to be set and if timing isn't set, they drop one at a time.

New to FC3, coming to some unfortunate realizations about the limitations against A2G in general. Most of the planes have issues where ripple rates and quantities can't be selected, so if I fire off s-25's or dumb bombs, it pickles/rifles all of them off at the same time. Luckily, the A10A doesn't have this problem, buuuut, I am running into another. Seems that if I loadout with more than 3 weapon types, ex: Mavricks, CBU, and rockets, it will only allow me to switch between 2. I can cycle between my rockets and my Mavricks, but can't select my CBU's. I've tried a few other combinations and keep running into the same thing. It appears that I can only switch between the last 2 weapon sets in the order they were loaded. If I expend one of them fully, I can then switch to whatever I couldn't switch to before. What am I doing wrong?

That appears to be a different issue.

I was really impressed with wing flexing physics when I got this module, until I realized that when the F16 rolls, especially with AMRAMMS on the wingtips, they twist the wrong direction! This is according to structural twist resistance designed into the wing against lift direction for lift stability by controlling I-beam widths in specified sections in the first 7 wing spars, moment produced by control surfaces, and CG/Inertia of the payload itself. They all contribute to a twist in a stabilizing direction opposite of what is presented graphically in DCS. When I roll left for example, the right wing twists upwards. It should twist down initially. I know some of you might think that's not obvious, that a wing should lift the right side of the plane up, but that's not how wing twist works. The control surface does that work. The wing was designed to dynamically work against it. It's a minor bug sure but probably easy to fix.

This may not concern all aircraft as I only own the F16, FC3, and have trialed the Mig21, but the bug has applied to all of them so I think this may be considered a general controls bug. When TRACKIR_Z is bound to zoom instead of pilot forward position, for a specific aircraft but not in general, the pilot's forward position can end up being locked into a fully forward or fully back position depending on where the Z position initialized prior to the control being switched over to zoom. The keybinds that normally control this (RCTRL RSHIFT /*) normally have no effect when this happens because there's a 2nd layer of offset stacked on that isn't being cleared. Sometimes the range can be partially restored or shifted, and in very rare cases fully restored with the following procedure: pause track ir double tap num 5 RCTRL RSHIFT /* to move seat back or forward RALT num0 to save unpause Trackir recenter trackir RCTRL RSHIFT /* Unfortunately, I can't find any consistent behavior or dependency that is affecting this range shift correction post initialization. All I know is that above process somehow changes it for some unknown reason by some minor and random amount. It's as if DCS is determining a default resting position with TRACKIR_Z bound to position before zoom is applied instead so that the range of motion is always offset after it changes the binding. If the TRACKIR initializes in the game in a forward position, it gets stuck with this offset until DCS is completely restarted. There are some workarounds: Start DCS with the TRACKIR paused, then recenter it. Spawn in a plane that has zoom bound instead of position, then unpause TRACKIR. This spawns the pilot with full range of forward/backward motion. Bind TRACKIR_Z to zoom in general. This of course causes the equal and opposite reverse effect against zoom for planes where TRACKIR_Z is bound to seat position. This requires step (1) for planes where position is desired instead of zoom. Some suggested solutions: Zero the range when forward/back binding is changed to zoom and vice vs Allow binding of axis to multiple functions at once so that TRACKIR_Z could potentially control both properties.