![]() I updated to the latest beta update of both CUE and Steam, but the problem still persists. ![]() Steam is the culprit but Corsair says it might take a couple months to fix on their end. Did a lot of research and sounds like it's a known issue, Corsair knows about it and is doing it's best to get a fix out but sounded like the Steam people weren't much help. Also caused a lot of weird disconnects with my other USB devices. Took me like 2 weeks before I figured out it was CUE/ Corsair Drivers conflicting with Steam and causing my Xbox One controller to constantly freeze up mid game and become unresponsive, as well as Steam itself freezing up frequently. I searched and searched for a solution, even reinstalled windows 10 thinking my OS was broken/corrupted. Best keyboard, mouse, and headset I've used, hands down BUT I had a problem that plagued me for almost the entire month I had it. In game I map the zoom on the SLIDER1 axis of the "Combined", and the RY for target range, RX for size.Įverything else I map it directly on the "Throttle" and "Joystick" devices, in DCS.Įxcept I don't map anything on the Joystick's S1, H2L, H2R and Throttle's CSL, CSR, MSP and MSU because these will trigger some keypresses that I set up in the script, but this is just an example, if you use the A-10C just delete these lines from the script and map the keys to your liking (as in your originial question).So about a month ago I received my k63 wireless keyboard and dark core mouse and shortly after a wired void pro headset. I just launch the script, the "Combined" appears and the other two stay and work as usual. a filtered slider (through an hysteresis) because my throttle slider is a bit jittery. a virtual axis that is activated through the Coolie switch left and right (for target size) a customized axis (MAP_RELATIVE) to use the ministick for target range a few special commands that call keyboard shortcuts (for snap views, teamspeak, trackIR) Here is a sample script that I'm using it for the P-51D (I just tweaked it so it doesn't depend on other includes), in which I set up: Yes, you can totally do that, using MODE_FILTERED. Joystick = S1+S3+S4 = Nil -> no action Thrustmaster Combined = S1+S3+S4 work by default If(&o = &Joystick & !(o|o|o)) GameOutput(&o, x, o) Int EventHandle(int type, alias o, int x) Thrustmaster Combined = Nil -> no action Note: The X Axis is commented out -> No Mapping -> Throttle removed as game controller -> Joystick remains as game controller With even more magic in the event handler, you can exclude buttons from the original device(!), so they only appear in the Thrustmaster Combined device:Ĭonfigure(&Joystick,MODE_FILTERED) You can also use the "filtered" mode to selectively drag the original Joystick/Throttle/T1600 buttons/axis into the Thrustmaster Combined Device. if(Init(&EventHandle)) return 1 // declare the event handler, return on error -> Cannot configure Joystick from Target With Target you can Exclude a device (or more than one device) entirely: However, there are some switches in Target to change that behavior. Stopping the script destroys the "Thrustmaster Combined" device, and re-instates the original devices. By default, the original devices are removed. When you run a Target Script, the "Thrustmaster Combined" is magically created. Getting the terms straight, there are the original devices - the Thrustmaster Joystick and the Thrustmaster Throttle in the Windows Game Controller Config Panel -> C:\Windows\System32\joy.cpl
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |