Vakarian

Yeah, those values look fine, by the looks of it those are device identifiers. Just spitballing, could you reinstall the drivers of the sound card? The issue could be on the relation DCS <-> Sound card drivers

IIRC BigNewy commented somewhere that this is on their tracker and should be fixed eventually as they are aware of the problem

Already reported

For starters, remove your personal info from those screenshots. Just don't do that, ever. Only share as little as it's required. Next, it's "common" for vendors to request you to destroy the item before you get a replacement. That's their way of ensuring you aren't faking it and just scamming your way to another product for free. As for removing the Paypal request, I'm not sure. Never been in that situation

Nothing they tell you is incorrect. You also might work on your behavior and manners is I may notice... They use specific type of grease which on one side smooths out the movement and helps reduce the jitter, but on the other may induce some stickiness as a side effect if left at a certain place. That is by design, you may or may not like it but there's nothing for them to fix as the product is working the way they designed it. What you could do is open up the throttle and replace the grease with the different type, but be careful which you choose as not all greases are made the same.,

You sure about that? I've completely reinstalled windows few days ago and redone all of the cockpit which includes updating firmware to the VPC peripherals. Flashing new firmware clears all config and once I've done that I still had the button functionality meaning it's not something I've added on my own. One thing to note is, that button (Button 1 in VPC software) will register only when you need to unlock the full travel back to the off position as that's the only point where it depresses enough. If you are anywhere else in the travel range, it won't reach the button. Bottom line is, that is a logical button by default. If it's not on your end I'd double check the firmware. --- EDIT: As far as Kiowa goes, it works out of the box with absolutely no fiddling in software both on VPC or DCS end. Just ensure that the special options for the throttle for Kiowa is set to fuil range (don't know the exact wording by memory) Make sure to check this post out. I haven't checked Huey lately but unless something's changed in DCS since then, this tutorial is the way to set it up for the Huey

It's not in the dropdown as that specific DTC profile (or any in this case) isn't added to the mission file. You can still import your own profile with the "Import" button and select whichever DTC file you wish from your PC and use it in MP sessions.

IIRC you can set a static unit instead of a live one, and that one has a checkbox "dead" which should serve the purpose I completely misread the question, Razor below has answered it correctly

@NineLine@BIGNEWY So, as we saw on the expo, the MiG-29 will have a functional visor. Does that mean we can hope for a working visor in other ED modules coming at the same time or very shortly afterwards? Maybe it's nothing for someone, but at least to the people in this thread it means the world. The clip of a working visor for the Fulcrum

To be honest, recently I've started to envy those people. What would I give so that the biggest issue in my life is a moved date for a video game product release...

Maybe, but there are still people who are unaware. Now when there's more vendors emerging in a FFB market that is something worth reminding so people can make a better informed judgement. That ain't cheap

Well, Moza's FFB are dead in the water as they stole the software and then couldn't make it work meaning that their FFB bases are neutered in the capability out of the box.

Wondering what they stole this time...

Have you actually tested this in the MP environment? AFAIK for the MP that doesn't matter, hasn't ever mattered. What you set as mission maker goes in the MP session, and only in SP can user override your settings