GregP

Iain Christie just did another in his iron bombing series: He basically uses the bottom of the reticle as a general aiming point and it seems to work pretty well.

I hope Mikhail doesn’t mind me posting this here, but I’m selling mine here and so could save people in the US some waiting time if they’re interested. I had no complaints with the collective at all, really loved it but just decided to use a different one.

Sold!

Very interesting, I stand corrected then. This is where, again, clarification direct from ED would be incredibly helpful. I seem to recall that the trimmer options in one of the other modules was changed at some point such that instead of there being the default option of 0.5 seconds to return to center, and the center trimmer method where you have infinite time to return to center, one of them was dropped to make it simpler for users. Maybe I’m wrong on that but I thought I recalled that happening. Either way, if you’re saying the default option works for you and you have 0.5 seconds to return to center, that’s good to know and I’ll give that a try tonight.

Excellent video, thanks! Looking forward to more.

What kind of stick are you using, and what trimmer option have you set in the Special tab?

OK no, I just verified that choosing 'default' makes things worse, as this option is clearly intended for FFB sticks where it is not assumed that the stick will return to center after being trimmed. From some more testing and looking at the controls indicator, it can clearly be seen the Central Position option is most suited to sticks with springs, but by its nature it's not possible to do multiple small trims rather than one big one, since stick input is ignored until returned to center. Additionally, whenever the trimmer button is released and stick returned to center, immediately upon returning to center a slight 'bump' is seen in the direction the stick was trimmed. This must be the bug that VitMax cited and that everyone has noticed as the additional undesired movement of the cyclic after they've trimmed. Doesn't seem to be any way around either of these problems until the bug is fixed.

Yes, VitMax thank you for such a helpful post explaining both the way it is supposed to work and the bug. Your explanation I think answers most of the questions that we all have been having about the trim system up to this point. Until the bug is fixed, this also suggests that the bug’s effect can be minimized by doing frequent trimming and thus not allowing big differences in cyclic position to accrue between trimming. That would argue for doing lots of press and releases as we move the stick instead of the press move release or move press release methods that presumably most of us have been doing up to now. However, for those of us with spring sticks, having to constantly move the stick back to center after every press and release would get annoying very quickly, so I wonder if therefore we should try the default FFB option in the special options menu?

Thanks for the update!

Just wanted to say thanks for this little mission - nice and simple.

I never imagined DCS and poetry overlapping but this is brilliant!

Example: 'Readjust free turbine RPM' can cover the 'AP Yaw On' tooltip even with seat and controls hidden. Mi-24P Tooltips Overlap.trk

Both use LCtrl+LShift+c.

Can you explain this part more? I can't quite understand what you mean here.

This is where some documentation about what the settings mean and how they are supposed to work, would probably quickly answer most of our questions.

Clearly there seems to be a lot of confusion among users on the different trimmer modes in the special options menu screen, as well as the actual method of trimming, i.e. whether to hold the trimmer button down and then move the stick and release the button, or move the stick and then click the trimmer button. Also since most of us are using normal center spring joysticks, but some are using FFB and some are using sticks with no springs and no FFB, we don’t seem to be getting anywhere by comparing our experiences. Could someone from ED step in and explain which of the trimmer modes is intended to be used with each kind of stick, and the proper method of trimming?

I still haven’t gotten around to learning the Harrier yet, but when I do I look forward to trying out your missions—they look great, thanks for the work you’ve put into these.

For anyone else trying to solve this problem for the F-14 in the future, just wanted to note that setting the Canopy Shaking filter to 5 solved it for me.

Yes, great info here guys, please keep it coming. I'm in the research phase of doing a similar conversion, having bought both an MSFFB2 and a CH Fighterstick that I intend to mate with the FFB base. But obviously a Virpil grip would be much better, so I look forward to hearing how yours progresses. On a side note, you mentioned having not tackled the low pot resolution issue -- not sure if you've seen this related thread, but it appears that if you run the MSFFB2 thru something like a Bodnar board, you can at least remove some of the deadzone around the center of the stick's movement.

Price drop.

SOLD Bought new in April for $650 and only used for a few hours. Perfect condition, no problems at all. Selling for $400 shipped within the US. Plug-and-play, doesn't require any extra drivers. http://oe-xam-simulators.blogspot.com/2019/08/bell-206-collective.html?m=1

Apologies for resurrecting an old thread, but I’m considering modding an MSFFB2 and am currently researching all the different options. Could anyone who has paired a Bodnar board with this stick comment on the following? Am I understanding it correctly that the primary benefit would be as a way to remove the stick input deadzone? As it appears that in a practical sense on its own it probably doesn’t do much to increase the precision or accuracy of the stick. And also, if I were to attach a different grip to the stick, might there be any benefit to trying to attach its wires to the Bodnar board rather than use the stick’s own board? I could see this being a necessity if the stick has a gameport connection, but if it was USB, would there be any advantages?

Got it sorted thanks to frostycab in the other thread -- I had DCS set to run in Admin mode, which was apparently preventing external apps from feeding keypresses into DCS. Turned off Admin mode and SD now works as it should.

Wow, I hadn't previously bothered to see if there was a mismatch between how I was running DCS and SD -- turned out I had set DCS to run in Admin mode at some point, and apparently this was conflicting with external apps' ability to feed keypresses into DCS. Turned off Admin mode and viola, SD is now working! Thank you!

Could use some help here from anyone else who's using a Stream Deck in DCS. I got a SD XL a few weeks ago and have downloaded several profiles found here and other places; I've also grabbed ctyler's plugin, and DCS-ExportScripts, etc. The problem I'm having is, I think unrelated to any of those scripts. All I'm trying to do is setup a basic profile by assigning the Function keys to the SD in order to control comms in-game. From looking at other people's profiles, it appears to me that I'm setting up the F-keys just like everyone as, i.e. using the System Hotkey option in SD. The keys will register in other apps such as Notepad++ or Chrome, but when I go into DCS, it's like the SD is entirely invislble to it -- DCS isn't seeing any of the keypresses. If for example I then press F1 on my keyboard, it works in-game as normal; but pressing the SD button that I've set to F1 does nothing. This happens whether I use other peoples' profiles or my own -- nothing gets recognized in DCS. I've been struggling with this for several days now. I've tried running SD in Admin mode, trying DCS in fullscreen and windowed, etc to no avail. It's been a while since I've tested a SD command that relies on any kind of export script, so to be honest I can't recall right now whether I've ever gotten those kinds of commands to work. But right now my focus is these simple keypresses, and I'm having no luck. I've tried more than just the F-keys -- briefing screen, controls indicator, auto start etc. Nothing gets recognized by DCS.