iceman223

Watch the YouTube video I posted. I set the RWR volume knob set to 25%. At 20s, there's a quiet search tone being played correctly. At 23s, the track tone gets played, but it's at full volume. It's not until I bump the volume knob at 28s that the game realizes it should've been playing the track tone at 25% volume all along. That's the bug. It plays the track tone at 100% volume regardless of where you have your RWR volume knob set, until you touch it. And in a mission with a bunch of threats, this happens over and over. It keeps playing RWR tones at 100% and you have to keep touching the volume knob, to get it to update and play the volumes at the correct level.

Quick Explanation: I made a quick mission to demonstrate. I spawn in, there's an SA-6 searching, I turn down my RWR volume to ~25% with the AUD knob on the front CMSC panel, the search tone is correctly played at a lower volume, but when the SA-6 starts to track me, the track tone is played at full volume. I have to touch the AUD volume knob either by clicking and dragging or scrolling over it, to set a new volume, to get the track tone to be played at the properly set level. I then set the knob back to 100% to show that the track tone was indeed being played at 100% volume, despite the knob being set to ~25%. This also happens when the knob is in its default position (~50%), it's just more apparent if you like to turn the RWR down even more. And I think this might be happening with the new threat tone as well, since it also played quite loudly, even though you spawn in with the RWR volume set to 50%. Here's a video. And here are my audio options. a10c2 rwr volume bug.trk

I have two separate questions and I don't know if they're bugs or not. First, as far as I can tell, you can't command full stabilator deflection, either forward or aft, with a centered trim position. I figured if I was dogfighting the jet and wanted to have full control over the stabs, then it was best to be at a centered trim position. But when I tested it in the ground (because SAS makes it harder to test in the air), the stabs don't max out unless I also trim. If you want to command full stab up, you need full aft stick plus ~15% aft trim and for full stab down, you need full forward stick plus ~10% forward trim, even though in the cockpit, the stick shows you maxing out the controls with a centered trim position. It gets weirder yet, because when I'm pulling full back and I reach the aft trim position required to command full stab up and then I look inside the cockpit to the horizontal stabilizer position needles and trim a little more, the needles move another couple degrees. So to recap, because I feel like I'm not explaining this succinctly, I have my trim centered and my joystick full aft. I see the ingame stick full aft, so adding aft trim does not move the ingame stick anymore, but it does move the stabs. I then keep trimming aft until the stabs stop moving (happens at about 15% aft trim) and I'm now commanding full stab up, but then I look at the control surface indicator gauge in the cockpit and put in a little more aft trim and the needles move, even though the stabs don't. And the same things are true pushing forward. The second thing is that the stabs move up when the combat/maneuver flaps/slats deploy. This might be how the real jet was, but it seems backwards to me. I feel like they should move down to compensate for the nose rise from the additional lift generated from the flaps being extended. Because right now what happens is, if you get a little slow in a dogfight and the maneuver flaps come out, then the stabs move up. So it's as if you're pulling an extra 20% back on your stick, even though you haven't moved the stick at all. You're still exactly at the same stick position you've always had in that turn. It's akin to your trim suddently changing and I find it really awkward, because it happens multiple times in a dogfight (any time your maneuver flaps come out or go in, the stabs are going to move up or down respectively). I couldn't understand why it was so hard to maintain corner speed in this jet, because finding myself a little too slow, turned into finding myself way too slow more often than not. And it's because when the maneuver flaps pop out, the jet commands more stab up, which tries to turn so much tighter that it just dumps all of its speed and it's all without you commanding it. So I find I have to catch it and and quickly cut my pull in half when the flaps come out and the stab moves up and then once I'm back on speed and the flaps go back in and the stab moves back down, I have to resume my previous hand position to prevent getting too fast. It feels clumsy. I don't know if these two stab behaviors are bugs or not, but I can make a video demonstrating them more clearly if my explanations aren't good enough. Thanks

Cibit, how weak does the return to center force get with a 125mm extension on the Warbrd base?

Is it just the grip? or T50 grip and base. If it includes the base, I'm interested. Edit: I don't know if my PM went through, so I'll just write it here too. Would you be willing to split the package? I'd buy the stick (as long as it was T50 grip and T50 base) and it looks like cichlidfan wants the throttle. If not, then I'm still interested. I'd still buy the bundle.

Version: DCS World 1.2.4.12913 Plane: A-10C The yaw SAS is not coordinating turns properly. To test, I trimmed the A-10 for a 1.1G turn. I took a screenshot capturing the HUD and turn coordinator with yaw SAS on and off. I then repeated this for a 2.1G turn. 1.1G yaw SAS on http://i.imgur.com/e6nWP2Z.jpg 1.1G yaw SAS off http://i.imgur.com/Dj1xmfR.jpg 2.1G yaw SAS on http://i.imgur.com/xPplojo.jpg 2.1G yaw SAS off http://i.imgur.com/hL1wZx9.jpg If you open these images up in different tabs of your web browser and flip between them, you'll see that when yaw SAS is off, the turns are more coordinated. The ball is more centered and the flight path marker is closer to the center of the HUD. Also, with yaw SAS on, the plane wanted to unbank itself, rolling out of the turn. So either yaw SAS is inputting rudder in the wrong direction, or the rudder input is switched and happening when it shouldn't (when yaw sas is off). When yaw SAS was off, the plane was quite stable, requiring no input to maintain its bank.