![]() ![]() ![]() Sounds like a stupid idea to begin with, that can only add latency, but I read it worked for some Kerbal players in early versions of the game where they had the same problem (not with FFB, but some joysticks in general particularly some saiteks), and it does really seem to work in DCS too. I dont think they are imagining their problem, there probably isnt anything different other than how we handle our sticks.Īnyway, as I wrote in the other thread, for some weird reason I can alleviate the issue by mapping my FFB2 controls onto a virtual vjoy joystick, and using that as input in DCS. Its not a problem for most of us, Im not sure I ever did it accidentally, but some ppl complain about it happening all the time. I had only noticed the occasional delayed and stuttering zoom input. I even read about it, and then posted I didnt have the same issue, as I dont tend to yank my stick around and simply never noticed. In my tests and videos Im making extreme movements to highlight/trigger the issue, but if you are gentle on the stick its not noticeable 99.9% unless you keep staring at the input overlay and are yanking the stick. Im not doubting you when you say you arent seeing the same issue fat creason but clearly others are, as there are a fair number of confirmations in the other thread and keep in mind that the issue is subtle most of the time. If I can ever reproduce this issue I'll make a post about it, I've just never seen it.įWIW I run an i7 6700k, GTX1080, and 16GB of RAM, so by no means a top-tier system. ![]() I'm very sorry I can't help you troubleshoot but it's unlikely that it's the F-14 specifically causing this. It seems like this issue occurs with a very very small percentage of FFB users which is a strong indicator that it's on a per-system basis. How DCS handles inputs for FFB is not something I know much about and we have no control over what we get from DCS in terms of input values or how/when they are updated. The API for FFB is very basic and we just send the stick information through it. We simply get the input state from DCS (it's the same for FFB and non-FFB), only difference with FFB is that we tell the stick where the neutral point is and send it a spring-stiffness value (which is constant, btw) via the API provided to us by ED. If the F-14 specifically caused FFB issues this thread would be blowing up. I have the exact same stick that I use for FFB dev work and mine works on the F-14 without issue, along with likely hundreds of other people who use FFB. HidHide is the better option all around for those who can use it.This issue is likely something related to your system or DCS install itself and not the F-14 specifically. Random non-obvious process having a hold of the gamepadĮven if it works initially, if your gamepad disconnects in the middle of a game chances are that you’ll lose exclusive access upon reconnection, requiring you to close the game to try again.įor the reasons explained above, the Hide DS4 Controllers option is NOT RECOMMENDED, though it remains available to users that need to use it for whatever reason.Nvidia Geforce experience process having a hold of the gamepad.Google chrome/Opera is running (why does it have a connection to the gamepad you ask? A mystery).Common reasons for this request to fail are: The problem with this method is that Windows can deny the exclusive access request when another process already has a open connection to the gamepad. When enabled, DS4Windows will kindly ask Windows for exclusive access to detected devices, meaning the later would only allow DS4Windows to detect the gamepads and preventing the double input issue. This option exists on DS4Windows’ Settings tab.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |