Reticuli

Yes. And that dynamic trim state you are tweaking with your inputs has certain range limits so you don't end up in some continuous roll or pitching motion when you let go.

Oh, that's all that is in the upper left? Yeah, then that.

There appears to be a defect in Clear Trim (ctrl + T), as it's not just clearing the manual trim state of the internal DCS virtual cyclic when the stick is actually being deflected at that moment, but appears to be either resetting the SAS values in that moment or doing something else that's causing a slight wiggle. So I have the new AutoTrimmer OFF, no manual trim set as I have already cleared it once before, and am using either GlovePIE or just applying a constant stick pressure with the GlovePIE script OFF, yet still this slight immediate alteration of the helo attitude happens specifically with ctrl + T. At first I thought something was messed up in my GlovePIE auto trimming script, but I just looked at the values while pressing crtl + T and they do not change. Something funky is going on with your Clear Trim. This happens in all three DCS Options-Special-Ka-50 trimmer modes, by the way.

Interesting, though I've never seen anyone claim that something like the F-16 stick is not "manual control" just because there's a FBW intermediary going on in between the stick inputs and what the ship control surfaces (or in the case of the LM, the RCS) is doing. As for "rate based attitude", that's rotational rate commanding with input and attitude hold without. I never said the stick directly controlled the thrusters with a physical pully or something. That's kind of a given. Other common AFCS modes, including on FBW helos for landing with gear down, are the commanding of lateral velocities with the stick (when stick inputs are zero, ship attempts to maintain position) and vertical velocity with some other flight control, such as the collective or a lever on it. *** I have figured out some issues with the new AutoTrimmer: 1) It appears separate from the manual trim state and requires the manual trim state to be completely cleared, otherwise you get a limitation of the full available deflection in the opposite direction of the manual trim state. 2) And rather than apply additional control input from the current AutoTrimmer attitude hold state, new stick input completely overrides the AutoTrimmer background state, causing it to bounce down to lesser stick inputs. Weeble wobble effect. Not fun. Makes fine inputs with AutoTrimmer on in options pretty much impossible. Close to being useable, though.

For one thing it's more fun, and it's also like helos that actually have simple spring-based or pressure sticks. No real helo, commercial, military, or experimental, has ever done it the way people are forced to do it in DCS Black Shark, even though there are three different modes to choose from now that you can slightly tailor to your particular situation and mitigate some of the weirdness. The script uses PPJoy as a virtual joystick. So install and configure that first. So DCS is seeing that instead of your Saitek. Then the GlovePIE script is setting the axis values for the PPJoy virtual axes. Your Saitek adjusts the GlovePIE axis values and dynamically applies both the raw stick input through to DCS but also a virtual trim state that you are dynamically moving around and updating through your movements. The extent to how far this virtual stick can be trimmed dynamically like this (the trim limits when you cease input) are set about where any more for that axis direction would cause a continuous roll or pitching. Three modes you double click the trimmer button to cycle through. So in Manual Trim mode you still have the trimmer button available to trim like normal, and Standard and Flight Director modes are tailored just slightly different from each other on their dynamic trim range limits so you don't keep pitching and rolling too much after ceasing a stick input. In Enemy Engaged and Comanche Gold, the actual feedback trimming script stuff in GlovePIE is more simple since their flight models are more simple to begin with and they have a true stable aerodynamic canned "level" they always return to when trim is cleared. Arguably, though, the "dumb" characteristic of the GlovePIE script not knowing the aircraft's attitude is less of an issue on them than Black Shark, where in contrast to the simple sims you now have to constantly fly the aircraft seat-of-the-pants. In Enemy Engaged and Comanche Gold, the scripts are a solution to the goofy auto-leveling when you release the stick. In Black Shark, there is no true "level" it will always return to. I should actually make a video to show you. I'm currently trying to mess with the new AutoTrimmer, but the previously-mentioned issues with it are making things difficult... particularly the way you can sort of hog the trim in one direction and then not be able to apply raw stick inputs in the other fully. It appears the AutoTrimmer almost seems like some type of duplicate stick or trim state over either the raw stick state or the trim state. Edit: Yes, the AutoTrimmer is separate from the manual trim state. In order to prevent the limiting of opposite deflection, you must have either the trim completely cleared or you must be in the Joystick Without Springs and FFB trimmer mode. However, the AutoTrimmer doesn't see your new stick inputs from your current AutoTrimmer virtual stick state within DCS, rather when you apply a new stick input it overrides the prior AutoTrimmer position... so a little input is not added to the current state, but rather is as if AutoTrimmer was completely cleared upon new input and you bounced down towards the lesser position. This actually happens in all the Special manual trimmer modes, but it's just that on the other two modes you sometimes have a background manual trim state that was preventing as much bounce sometimes and fulling me. Anyway, this bounce makes AutoTrimmer unuseable as it is. Should be easy to fix, though.

Rotation: Translation: Inside the LM: Here he is flying the demonstrator: And ejecting from it: There were manual controls in the module and it's how Apollo 11 actually executed that touch down. And the primary AFCS mode for both manual moon landing and for Apollo and Gemini orbital docking was rate command, attitude hold for the joystick. I'm not talking about interplanetary navigation or orbital capture. The guidance computers had an issue of timing-out during final descent stages, anyway, so I believe even the later Apollo landings did their touch downs manually and defeated the autopilot, too. The computer's biggest role during the actual landing was controlling the length and intensity of the initial de-orbit burn.

I don't fly Longbow 2, EECH, nor X-Plane with a keyboard. Do people fly the F-16 with a keyboard in DCS? Did the Gemini astronauts maneuver with a keyboard when docking? Did Neil Armstrong land on the moon with a keyboard?

Those are actually there when you hit esc under System, just not adjustable. So unfortunately it looks like much of the graphics stuff can't be tweaked when the mission is running. There's all sort of other stuff that seems we ought to be able to change without much issue, but they don't even have tabs.

There are other tabs besides System and Audio that would be nice to be able to tweak while you're on a mission without having to quit it. Thank you.

I would vote for somewhere in South America, because, you know, their jungles "make Cambodia look like Kansas"... and the stories would make more sense for like modern proxy wars and narco wars and all that. Could even do internal civil war stuff or civil unrest story lines like authorities losing control over certain districts to rebels or organized crime... doesn't even need to be nation against nation or proxy wars. Might be the perfect situation for ED to do some extreme terrain and shanty towns and crazy trees. Please, give me crazy trees. And a volcano. I wanna volcano.

Hah hah hah... no, you command a rate with input and it holds an attitude when inputs end. You skipped a part I think. You're definitely describing the yaw trimmer option in Black Shark in some situations, though :-)

Like when you would get your stick deflection (X52) or pressure (X65F) added to the trim you had just manually clicked with the trimmer prior to returning the stick to zero input state (center or no pressure, respectively), which is why they added the Trimmer Mode Center option. Or the hurdles implementing manual trim for people who had certain force feedback or physically-trimming pole sticks, which is why they added the Joystick Without Springs and FFB option more recently that gets rid of the within-the-sim virtual stick manual trim state entirely so you don't even have to clear or set it... it clears the sim's own cyclic trim and stays untrimmed as soon as you apply input. Certain FFB sticks and pole cyclics literally just stay in their physical positions when you hit their special trimmer button or release their trimmer latch. These three Options-Special-Ka-50 Manual Trimmer options are all useful for various forms of sticks if you want to manually trim, and like I said, the most recent addition (Joystick Without Springs and FFB) actually works better than even the default one for GlovePIE & PPJoy auto trimming if you don't plan on ever doing manual trimming... otherwise I cycle through all my GlovePIE script modes to clear the in-sim trim state you jump in with so the sim only sees the PPJoy virtual stick. The PPJoy virtual stick becomes kind of like a virtual pole cyclic as a software intermediary that my inputs on the Saiteks are dynamically updating. So I've got Manual Trim, Standard Dynamic Trim, and Flight Director Dynamic Trim as modes I cycle through by double tapping the manual trimmer pinkie button on my stick. If I don't plan to use the manual one for the whole flight, I just stick it in the FFB mode in the sim and put it in like Standard Dynamic Trim so I can use Auto Turn To Target. I actually just did some testing finally with AutoTrimmer in the Su-25T, and it's clearly still a work in development even for fixed-wing. So it needs further improvement, anyway, and hopefully ED can make some considerations for helos, too, as work continues on this option setting.

Once they get it working right, you should be able to command a rate with stick inputs and hold an attitude when there are no stick inputs. Some aircraft hold an alpha instead of an attitude, particularly when the gear is down. Right now, AutoTrimmer is sluggish and seems to only slightly reduce trimming workload with fix-wing aircraft. It works slightly worse for helos in some ways and slightly better in other respects. Looks like it needs some improvement.

I think ED added AutoTrimmer just recently, as there's a thread on it from back in June. https://forums.eagle.ru/showthread.php?t=243490 As for the X65F, I started with Blackshark 1 when it originally came out and the X52. I very quickly started utilizing GlovePIE & PPjoy, as I'd already done it for Enemy Engaged. I picked up the X65F with the idea that it would be more responsive and have less lag for both sensing peak inputs and return-to-center for my scripts, which turned out to be the case. My scripts are used to give a crude auto trimming back before ED even gave us the Trimmer Mode options, which do help somewhat resolve a few of the bigger issues of manual trimming on the Ka-50, though the Joystick Without Springs and FFB option has also benefitted the GlovePIE scripts. Even with the three manual trimmer modes available, though, I still prefer to have trimming automatically update on its own dynamically when using a spring or pressure stick. Feels more natural to me. Pro pole cyclics or FFB would obviously not utilize auto trimming. Nonetheless, ED finally added an AutoTrimmer, so it's just at least a matter of getting the bugs worked out of it. They probably intended it more for fixed-wing aircraft, but those are going to use relatively little trim compared to helos, so the one issue isn't going to occur much. And fixed-wing also isn't going to encounter issues with small intermediate stick deflection resetting or overriding the prior trim state as they're always additive.

The RWR in the upper left of the cockpit is one of those things I really miss when I'm in hud-only mode. A transparent version of the lights on it floating somewhere in hud-only mode would be nice to have. We have the Shkval, Abris already, and Controls Indicator box (optionally), so the RWR would round it out.

Yikes.

The Ka-50 with the current somewhat-wonky AutoTrimmer option or my combo of GlovePIE & PPJoy will give you a quasi-modern experience similar to Janes Longbow, Comanche Gold, Enemy Engaged, or X-Plane (with its auto trimming of pitch loads Plane Maker setting combined with Artificial Stability) if you're using a spring-loaded joystick or a static pressure stick. Unless you use a force feedback stick or buy a pro pole cyclic, none of the others are going to quite feel as natural and intuitive. Since you have chosen the Huey, you might want to consider getting either a FFB setup or a pro pole cyclic.

Totally unrelated and it just so happens to be the right engine not spooling up? Possibly unrelated, but possibly related. Isn't auto start just a script or macro that runs of all the right buttons done in order with the appropriate timing? I can hear them all slowly switching and it takes a few minutes. If it's just a script or macro, start up and re-spawn bugs should occur identically with both manual and auto start.

It's nice to finally see such (at least attempt of) an auto trimmer option in DCS, but it's problematic for the Black Shark currently even though in theory it’s a great idea for people without either force feedback or physically-trimming cyclic pole sticks at home. While my GlovePIE scripts combined with PPJoy are technically "dumb" from a coding sense, as they don't actually know the orientation/attitude of the aircraft at any one time and are separate from DCS, my scripts don't suffer from the specific issues your AutoTrimmer is having and therefore still seem superior when flying seat-of-the-pants and not wanting to bother with awkward manual trimming on a conventional joystick or pressure stick, though your method obviously has benefits and could be even better than my scripts with further work. When AutoTrimmer is on, Joystick Without Springs and FFB and Center under Options-Special-Ka-50-Trimmer Mode both have problems with a deflection or pressure (on the X-65F) between center and the prior trim state bouncing and overriding the prior trim state rather than adding to that trim state or deflecting past it. Center and Default also have an issue where if you have a large trim state (up to max for that axis) and try to deflect in the opposite direction, you are limited in deflection possible by that amount of trim subtracted in the other direction until you either release and it captures a new trim state again or you manually hit the trimmer button... say somewhere nearer (or up to) the center trim position in the red box Controls Indicator. This second issue causes these two Trimmer Mode settings to be oversensitive in the direction of the axis the trim position was/is in and under-sensitive in the opposite direction. So, you can use Default and AutoTrimmer to get rid of that awful bounce effect, but you still have the old trim state fouling up sensitivity in both directions and max immediate available deflection in the opposing direction. You can use Joystick Without Springs and FFB and AutoTrimmer to get normal sensitivity and full deflection available all the time, but then you have to deal with that awful bouncy issue. Regardless of the Trimmer Mode setting you choose, the AutoTrimmer is also quite laggy in "capturing" an attitude. Turning Flight Director on just seems to reduce available rate damping and attitude hold authority with not much improvement on lag or the other issues. Optimally, AutoTrimmer could be less laggy than it currently is and also work the same regardless of which of the three settings under Options-Special for the Ka-50 trimmer you choose. If you have AutoTrimmer selected, it should override the Options-Special-Ka-50-Trimmer Mode setting and work one particular way: A reasonably-responsive rate command & attitude hold, with the same sensitivity in all axis directions at all times, with full deflection immediately available to command, and it also additively commanding rate inputs from the current dynamic trim position rather than ever bouncing to some intermediate stick position that awkwardly overrides the current trim state. Thanks for your time. P.S. On a side note, I also think there's an odd lack of yaw rate damping on the Black Shark and an overreliance on needing to either use the trimmer button to set a manual heading caret (with the Autopilot Desired Heading - Desired Track position switch on the right console set to the middle for neither) or the use of Auto Turn To Target... both of which require Flight Director off. They're still not strong. The SAS rate damping seems even more unusually weak.

In multiplayer, ka-50 right engine not starting using auto start on a server that doesn't have aircraft already started.

This is exactly what I do with the X65F, and then I also use the ministick with registry hack thing when in autoturn for yaw control now with Flight Director off... more precise than my pedals and I get actual real semblance of heading hold stability, unlike the weak as heck SAS axis authority that’s practically useless. I find my right thumb on the stick hat and the pickle button can work the optics just fine for slow stuff, even though it's still not as precise for locking onto an adversary Cobra as I'd like.

Well, they're not shrubs, especially the conifers in DCS, but Alaska, Washington, Oregon, northern California, and Russia have HUGE trees. Tree tallness might be a neat adjustment. And there's more small patchwork I find in real life due to areas of clear cuts vs untouched. Useful. We could additionally combine that with some maps with more varied terrain for rural areas (more canyons, depressed terrain for creeks and rivers, valleys, and lots of small steep hills) and taller objects in the urban sections. I notice a lot of flight simulators have nuance in the terrain in the textures that spoof topology nuance... Enemy Engaged probably being the biggest culprit with their sand dune textures, but then it does have maps with lots of little canyons with rivers in them all over. Another thing to think about is that real roads tend to often have ditches alongside them to prevent flooding, which means trees usually are cleared to a wider path for the road to accommodate them. Some of the roads in DCS seem to have trees right up alongside them and no space for the ditches such that it's hard to get a chopper through above the road NOE. So some roads could benefit from a wider gap of trees beside them that would help helo tactics.

I'd rather have a DCS AH-1Z with SAC side stick modeled and being able to choose between dynamic rate-command/attitude-hold mode like we had in Janes Longbow series, hover mode where you command a temporary lateral velocity with the stick, and other modern flight law modes to choose from on-the-fly that helos that use joysticks and pressure sticks have. I think it would sell well because 1) the Z can hold its own against fixed-wing aircraft and 2) because most people have either normal joysticks or pressure sticks rather than FFB or specialty pole cyclics at home.

Using the X65F with my GlovePIE autotrimming script and now the option of "Joystick Without Springs and FFB" Trimmer Mode in Options->Special->Ka-50, I seem to be able to simply leave Flight Director off, now. It's less squirrely and more like Enemy Engaged... but better physics, obviously. I mean better behaved. The SAS axis channel damping in combination with the attitude hold (but no manual trim within the sim, only in GlovePIE's virtual PPJoystick) seem to do their thing better now and there's no need to cycle through the GlovePIE script modes from Manual, to Standard Dynamic Trim, to Flight Director Dynamic Trim by double-clicking the pinkie button a couple times since there's no actual in-sim manual trim to clear... I believe, correct me if I'm wrong. I just do it once to get to Standard or Flight Director versions depending on how much bank I want to be able to hold. I probably need to tweak my script a little so there's less wobble upon input and to change the quickness of the script response, but doing the auto-trimming loop thing in the script while it's also seeing the raw input seems to currently work well enough right now after finally updating to the beta last night. And when I stop sort of commanding a rate input on the X65F, it seems to do attitude hold pretty acceptably... similar to doing manual trimming with my pinky finger clicking frequently whenever I would find an attitude I wanted to keep. I rarely used Manual Trim mode on the GlovePIE script because I always found it clunky with a normal spring-loaded (X52) or fixed-position pressure (X65F) stick, but the Dynamic Trims were always much more seat-of-your-pants and required constant adjustment than this... you had to constantly fly the helo every second, which I enjoyed but could be a handful... not so much now with option of no-spring & FFB. Then there are various things I can do to utilize heading hold for the rudder channel, like steer towards target, which seems to have quite a bit more channel authority than the damping, though still not as much as I'd like. It's not true "automatic dynamic trim update" rate-command/attitude-hold like ADOCS and Comanche had and later block Apaches are apparently supposed to eventually get if they ever move to side sticks (think Janes Longbow series), but it's definitely usable.

So then doesn't this thread imply that if the body of the helo is below the line of sight (including taking trees and buildings into account) of the radar, then you should not be able to fire on it, and if only the rotors are unmasked peaking above the trees, it perhaps ought to appear in the sim to be a direction-only, no-altitude, and no-range jammer icon on the radar but that HOJ shouldn't be able to hit it? That seems like a pretty simply solution rather than trying to actually model the individual returns of every rotor blade as it's going around in realtime, which is understandable it hasn't been done. An unmasked rotor could light up an active radar in line-of-sight with the ease of an active jammer but couldn't be targeted. I’d be in favor of that. I’d also be in favor of an option to adjust how tall the trees are. Might allow people to set up more balanced servers.