GregP

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.

I should clarify that the test I'm doing should not depend on DCS-BIOS or DCS-ExportScript or anything like that, as I'm simply trying to get the function keys recognized by DCS. I start new profile in Streamdeck, set keys to F1-12, and they work in other programs like Notepad++. But in DCS, they're not being seen.

New Streamdeck XL user here -- I seem to be missing something; no matter which profile I load (I've downloaded several), I can get the buttons to register outside of DCS (e.g. F1, F2, etc.) but when I go into DCS, nothing registers. It's like DCS isn't seeing the output from the Streamdeck at all. I've tried both windowed and fullscreen DCS and neither one works. I've also tried setting a default profile in the Streamdeck app, and setting a profile to go along with DCS.exe -- all to no avail. Am I missing something obvious here?

Well I for one would love to see this released as it appears to make an already incredible mod even better!

JoystickProfiler may be exactly what you're looking for: https://github.com/Holdi601/JoystickProfiler GR did a nice overview video on it recently:

Interesting, I’ll have to try that same test while sitting on the runway before taking off. I had only tried it in the air before.

I noticed last night that if I smoothly move the stick along the roll axis from center to either left or right, the stick in the cockpit (and on the controls indicator) moves right along with it until it reaches about 70% of the full travel and then it slows down like it’s stuck in molasses. No matter how fast I move the stick, when the in-game stick gets to about 70%, it slows down to a constant slow speed until the end of its travel. In the pitch axis, however, I don’t have this problem. And I don’t recall seeing it on any other plane. This is using the default axis tuning options: zero dead zone, X/Y saturation 100, zero curvature. In the controls options menu, the Roll Axis shows the expected 1:1 movement, and same for my joystick’s software (VKBconfig). Has anybody else had this problem? Or have any ideas of how to fix it? Or is this maybe just a feature of the P-47, possibly to prevent overstressing the airframe in roll?

FYI, this post provides a solution to the oversensitive trim commands -- just drop the gain by half. Tested just now and it's much more manageable now.

We should clarify that OP is talking about the thick, blurry HUD text, not the fact that [in that screenshot] he can't see the entire HUD -- that's just a head-position-too-far-back issue. The HUD text issue is a known problem that's been there since the module was first released and there's been multiple threads on this topic. It seems that at any resolution other than 1080p, the HUD (and DDI text) appears thick and blurry. This mod does a pretty good job of fixing it and I've been using it for a long time now.

Maybe put the FLIR into Point Track mode, as that is intended for moving targets?

Sorry for the delay, I just saw this now. I bought from the Microsoft store, and they had free shipping and returns: https://www.microsoft.com/en-us/p/hp-reverb-g2-vr-headset/93qb262d0514 Seems they’re out of stock at the moment though.

I should also note that I really do think that the astigmatism in both of my eyes plays a large role in my continued dissatisfaction with VR. I know from experience that whenever I try to start wearing contacts, it’s extremely frustrating how whenever the lenses get even a little bit out of rotation my vision gets blurry. I think wearing my glasses inside the headset replicates the same problem, in that as soon as they’re a little bit out of alignment with my eyes my image is not sharp anymore; that’s why I said I think that the add-on lenses would’ve helped, but likely would not have completely gotten rid of the problem.