skypickle

I set the encoder delay to 140 ms and that helped a little but still have to turn the encoder many times to go from full zoom out to zoom in. I would like that to be 1 revolution at most. In fact it would be nice if it had an 'acceleraion feature' like mice do. Spin the dial fast-send a lot of keypresses, spin the dial slow-get high resolution. I tried using joystick gremlin to map each encoder direction to a macro. The macro consists of many keypresses for zooming out or zooming in. Unfortunately, this is not much faster and is also stuttery-so you never know how much you will end up with. Currently I have the flaps axis set up as zoom but I would prefer using the encoder for this. Any updates on this issue? This is how to create a virtual axis from buttons in virpil software directly. No need for joystick gremlin https://forum.virpil.com/index.php?/topic/850-setting-delta-encoder-wheel-as-virtual-axis-and-hardcoded-axis-precision/

Finally figured it out. It is still suboptimal. Even though I have programmed a macro to hit the 'zoom out' keypress 10x, it is agonizingly slow and not responsive.

@HC_Official so I installed vJoy and Joystick gremlin. WHOA. Brain slammed. All I want to do is send 10 keypresses for a single click on the encoder. Is there a good video I can watch that you know of? I do not want to remap all my other bindings.

I read somewhere that windows assigns a unique device ID to each controller plugged in. So a controller on one pc may have a different I’d when moved to a different pc making all the key bindings from the old pc non transferable. Are DCS profiles transferable?

anybody figure out how to speed up the encoder dials? I need to turn them A LOT to get a gauge in DCS to reflect the input.

SOLVED: I figured it out. The culprit is terminal human stupidity. I flashed mongoos software onto a constellation stck. After I flashed the correct firmware, now it works. I report this imbecilic human error only to reassure everyone that flashing the incorrect firmware to any virpil device does not termianlly brick your hardware. I appreciate the time everyone took to respond. Eugel gave me a clue when he said the mongoose has no twist.

What do I have to edit to allow a keybind for adjustment of the electronic compass on the dashboard?

I can change the LED colors in the 'head' so I know the connection is good. What is error 25?

So I oredered a new stick (Mongoose) with a base (CM2) back in November. And it just came in last week. And the only thing that works is the x and y axis. No twist. None of the buttons work. Got the latest virpil software and the thing says error 25 in a little red box. Flashed the firmware. no improvement. Restored to default settings. No change. Contacted VIRPIL last week. They emailed me 3 days ago with a request for all my personal info and serial number of the device. Have not heard back from them.

delete

I am having this problem since the latest update. TrackIR is not bindable and does not work in game. Yes the folder "...\Saved Games\DCS.openbeta\Config\Input\A-10C\trackir" is empty. Also all the other trackIR folders for all my other aircraft are empty as well. SOLVED: Reinstalled DCS

Thank you. I did discover that I wasn’t resetting trim before autorotation. Reset helps. @cw4ogdenthank you for those diagrams. I don’t know if it was intentional but the autotrotative force in region C seems to occur with a more angled blade (more collective). Autorotation requires no collective to minimize drag on the blade. Also shouldn’t lift always be perpendicular to the blade? After all the wing shape is not changing. As the blade is angled back with more collective, the lift force generated by the airflow over the wing is related to the wing. The lifting force relative to the wing should remain constant but relative to the aircraft the vector should point more aft- the drawing shows the lift vector moving forward. Inflow as labeled in the diagram is the sum of airflow due to aircraft motion plus rotor motion. If we hold aircraft motion constant, then increasing collective should angle the lift vector backwards?

Last week I was autorotating like a champ. Putting the Huey down in one piece and even on the runway sometimes. But after the last patch I have noticed something weird. I turn down the throttle and lower the collective like I usually do. Then I pitch down and try to keep rotor rpms in the green while keep speed to 80 knots. Except now, once I turn the throttle down, the rotor rpms drop and never come back up. The collective is all the way down and I am pitched 30 to 45 degrees down. Then I started wondering, why does the rotor keep spinning in an autorotation anyway if the collective is all the way down. If I want the rotor to spin up as I fall, shouldnt the rotor blades actually need to angle to the ground a bit?

I have two copies of DCS open beta-one on my nvme drive(C: drive) and one on a spinning hard disk(D: drive). (The backup is in case of a disaster so I dont have to download gigabytes over a slow internet connection. When I update my dcs, I only update the one on my C drive and that's the one I use. I havent used the one on the hard drive for a month (and just to update it then) When the new patch came out today (and with all the other patches too) the updater tells me it is copying files from the Hard drive (copying files from the D drive) What's going on?

SOLVED: I put a rubber band around the power brick to hold it tightly in the adapter. It seems the round pegs of russian plugs are too slim for the fat holes of american plug adapters. Now there are no CRC errors and the gametrix software works. Interesting how a flaky power connection allowed the demo to work but not the gametrix control panel. It seems the gametrix software does a CRC check to make sure it's talking to the proper hardware and a slightly off voltage reading affects the readout during this process.

simshaker aviator does not work. the jet seat control panel says disconnected. I tried a usb port on a powered hub as well as one connected directly to the motherboard-same problem. @MasaMandid your power brick solve your problem? The error that MasaMan and I get looks like a software error but he was told to get a new power brick.

I have been using jetseat for a year but wanted to move it to a new pc. I installed the gametrix software and the demo massage app works fine. However, the control panel crashes on launch with 'device cannot be opened error'. The control panel seems fine but when i try to test it, i get the same error dialog as MasaMan. The control panel is v1.3.1.1. Interestingly, when i install the Russian version it is version 1.2.1.1. It also fails with an attempt to connect and then disconnects. I tried running it with admin privileges, same problem. I tried alternative mode (ctrl-shift and click on gametrix logo) and same problem. Event log shows nothing. Device manager shows no errors or yellow triangles. How can I troubleshoot this error? Running the latest win10pro ryzen 5800, 32 g ram.

@Remcothank you . I was looking at the TCS base vs the TCS plus. It seems the TCS base is designed to mate with their sharka grip whereas the TCS plus has the throttle axis is for their UH60 grip which has no throttle axis, but a switch? Anyway, isn't it necessary to the throttle up when pulling the collective up ? It would seem using the uh60 grip requires moving your hand between two different positions to maneuver the collective vs using the controls on the collective.

Is there a way to mount the super taurus to a chair with the monster tech system?

delete

Uncoupled aiming is a feature activated by R shift + T. It allows the TrackIR to direct the gunsight. I would like to bind it to a button on my throttle or joystick but the controls dialog does not allow this. I added Y as another keybinding for uncoupled aiming and it showed up in the file: C:\Users\Stefan\Saved Games\DCS.openbeta\Config\Input\UH-1H\keyboard.lua as ["d3005pnilunilcd46vd0vpnilvunil"] = { ["added"] = { [1] = { ["key"] = "Y", }, }, ["name"] = "Uncoupled Aiming On/Off", }, So I copied that code into the file for my WinWing throttle: C:\Users\Stefan\Saved Games\DCS.openbeta\Config\Input\UH-1H\joystick\WINWING THROTTLE BASE1 + F18 HANDLE {E33C7250-60FB-11ec-8002-444553540000}.diff.lua This is the file that has all the modified keybindings for the throttle. I added ["d3005pnilunilcd46vd0vpnilvunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN13", }, }, ["name"] = "Uncoupled Aiming On/Off", }, but the adjust controls dialog still does not allow me to enter anything for this function on my throttle. So then I looked for the uncoupled Aiming hotkey in the file: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\Uh-1H\Input\UH-1H\joystick\default.lua and found a bunch of commands for the category 'View cockpit'. A similar command for enabling head shift is {down = iCommandViewPitHeadOnOff, name = _('Head shift movement on / off'), category = _('View Cockpit')}, so I added {down = iCommandViewPUncoupledAim, name = _('Uncoupled Aiming On/Off'), category = _('View Cockpit')}, I invented the 'down = iCommandViewPUncoupledAim, ' Now the adjust controls dialog allows me to bind a button from my throttle to the command 'Uncoupled Aiming On/Off' However, it still does not work in game. Also there are two entries for this command in the dialog like so: That they are orange is telling me something is off. Can anyone help me with this?

Has anyone gotten this to work for custom modules like the A4E?

sOLVED: need to move the throttle past afterburner detent for ENTIRE excursion.

You misunderstand. DCS does NOT recognize it AT ALL. If it was an axis reversal problem, I should see some movement reflected in DCS.

Opening up Controls in DCS open beta latest shows this: Opening up box labeled "collective " allows the analog thumbstick to be assigned to it(either motion of the thumbbstick - vertical or horizontal) but NOT the WinWing throttle motion. The Winwing joystick base has no problem getting assigned to cyclic pitch and roll. Also, Opening up box labeled "throttle" allows the analog thumbstick to be assigned to it(either motion of the thumbbstick - vertical or horizontal) but NOT the WinWing throttle motion. For some reason, the Winwing throttle motion is not recognized in the Huey. It IS recognized just fine in the A10C and the F18. Inside C:\Users\Stefan\Saved Games\DCS.openbeta\Config\Input\FA-18C_hornet\joystick as well as inside C:\Users\Stefan\Saved Games\DCS.openbeta\Config\Input\A-10C II\joystick is a file named WINWING THROTTLE BASE1 + F18 HANDLE {E33C7250-60FB-11ec-8002-444553540000}.diff.lua I copied that file to Inside C:\Users\me\Saved Games\DCS.openbeta\Config\Input\UH-1H\joystick and restarted DCS. The Winwing throttle is still ignored and cannot be assigned to the collective. The 'Flight Control Collective cell' has 'JOY_Z' in it but nothing happens when the WinWing throttle is moved both ways. Deleting 'JOY_Z' and opening the cell also does not allow WinWing throttle motion to be assigned Other buttons on the throttle can be assigned just fine. For example the 'pinky switch' forward and back can be assigned tozoom in and out. The top 4 way push can be assigned to different views.The buttons just next to the ministick can even be made into modifier buttons and they all work. Inside C:\Users\me\Saved Games\DCS.openbeta\Config\Input\UH-1H\joystick are these files: I succesfully used my old TWCS throttle in the past as a collective for the HUEY and have two different working configs. I opened up TWCS Throttle {0C6ADB20-45EC-11eb-8002-444553540000}.diff.lua and is this: local diff = { ["axisDiffs"] = { ["a2001cdnil"] = { ["name"] = "Flight Control Cyclic Pitch", ["removed"] = { [1] = { ["key"] = "JOY_Y", }, }, }, ["a2002cdnil"] = { ["name"] = "Flight Control Cyclic Roll", ["removed"] = { [1] = { ["key"] = "JOY_X", }, }, }, ["a2003cdnil"] = { ["name"] = "Flight Control Rudder", ["removed"] = { [1] = { ["key"] = "JOY_RZ", }, }, }, ["a2012cdnil"] = { ["added"] = { [1] = { ["key"] = "JOY_SLIDER1", }, }, ["name"] = "Zoom View", }, ["a2087cdnil"] = { ["changed"] = { [1] = { ["filter"] = { ["curvature"] = { [1] = -0.06, }, ["deadzone"] = 0, ["invert"] = false, ["saturationX"] = 1, ["saturationY"] = 0.98, ["slider"] = true, }, ["key"] = "JOY_Z", }, }, ["name"] = "Flight Control Collective", }, }, ["keyDiffs"] = { ["d10pnilunilcdnilvdnilvpnilvunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN9", ["reformers"] = { [1] = "JOY_BTN2", }, }, }, ["name"] = "F7 Ground unit view", }, ["d135pnilunilcdnilvdnilvpnilvunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN10", ["reformers"] = { [1] = "JOY_BTN3", }, }, }, ["name"] = "F6 Weapon to target view", }, ["d13pnilunilcdnilvdnilvpnilvunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN_POV1_U", ["reformers"] = { [1] = "JOY_BTN2", }, }, }, ["name"] = "F9 Ship view", }, ["d151pnilunilcdnilvdnilvpnilvunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN10", ["reformers"] = { [1] = "JOY_BTN2", }, }, }, ["name"] = "F8 Target view", }, ["d15pnilunilcdnilvdnilvpnilvunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN_POV1_U", ["reformers"] = { [1] = "JOY_BTN3", }, }, }, ["name"] = "F10 Theater map view", }, ["d179pnilunilcdnilvdnilvpnilvunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN11", ["reformers"] = { [1] = "JOY_BTN3", }, }, }, ["name"] = "Communication menu", }, ["d3004pnilu3004cd41vd1vpnilvu0"] = { ["name"] = "Pilot Trimmer", ["removed"] = { [1] = { ["key"] = "JOY_BTN3", }, }, }, ["d3007pnilunilcd49vd1vpnilvunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN_POV1_R", }, }, ["name"] = "Pilot Sight Switch", }, ["d3009pnilu3009cd21vd1vpnilvu0"] = { ["name"] = "Pilot's radio trigger RADIO", ["removed"] = { [1] = { ["key"] = "JOY_BTN1", }, }, }, ["d326pnilunilcdnilvdnilvpnilvunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN8", ["reformers"] = { [1] = "JOY_BTN3", }, }, }, ["name"] = "F1 HUD only view switch", }, ["d341pnilunilcdnilvdnilvpnilvunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN9", ["reformers"] = { [1] = "JOY_BTN3", }, }, }, ["name"] = "F5 Ground hostile view", }, ["d359pnilunilcdnilvdnilvpnilvunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN_POV1_L", ["reformers"] = { [1] = "JOY_BTN3", }, }, }, ["name"] = "F4 Look back view", }, ["d7pnilunilcdnilvdnilvpnilvunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN_POV1_R", ["reformers"] = { [1] = "JOY_BTN3", }, }, }, ["name"] = "F1 Cockpit view", }, ["d84pnilu84cdnilvd1vpnilvu0"] = { ["name"] = "Pilot weapon release/Machinegun fire", ["removed"] = { [1] = { ["key"] = "JOY_BTN2", }, }, }, ["d8pnilunilcdnilvdnilvpnilvunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN_POV1_D", ["reformers"] = { [1] = "JOY_BTN3", }, }, }, ["name"] = "F2 Aircraft view", }, ["dnilp210u214cdnilvdnilvpnilvunil"] = { ["name"] = "View Up Right slow", ["removed"] = { [1] = { ["key"] = "JOY_BTN_POV1_UR", }, }, }, ["dnilp211u214cdnilvdnilvpnilvunil"] = { ["name"] = "View Down Right slow", ["removed"] = { [1] = { ["key"] = "JOY_BTN_POV1_DR", }, }, }, ["dnilp212u214cdnilvdnilvpnilvunil"] = { ["name"] = "View Down Left slow", ["removed"] = { [1] = { ["key"] = "JOY_BTN_POV1_DL", }, }, }, ["dnilp213u214cdnilvdnilvpnilvunil"] = { ["name"] = "View Up Left slow", ["removed"] = { [1] = { ["key"] = "JOY_BTN_POV1_UL", }, }, }, ["dnilp3002unilcd49vdnilvp-0.5vunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN_POV1_D", }, }, ["name"] = "Pilot Sight Intensity Decrease", }, ["dnilp3002unilcd49vdnilvp0.5vunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN_POV1_U", }, }, ["name"] = "Pilot Sight Intensity Increase", }, ["dnilp32u214cdnilvdnilvpnilvunil"] = { ["name"] = "View Left slow", ["removed"] = { [1] = { ["key"] = "JOY_BTN_POV1_L", }, }, }, ["dnilp33u214cdnilvdnilvpnilvunil"] = { ["name"] = "View Right slow", ["removed"] = { [1] = { ["key"] = "JOY_BTN_POV1_R", }, }, }, ["dnilp34u214cdnilvdnilvpnilvunil"] = { ["name"] = "View Up slow", ["removed"] = { [1] = { ["key"] = "JOY_BTN_POV1_U", }, }, }, ["dnilp35u214cdnilvdnilvpnilvunil"] = { ["name"] = "View Down slow", ["removed"] = { [1] = { ["key"] = "JOY_BTN_POV1_D", }, }, }, ["dnilp36unilcdnilvdnilvpnilvunil"] = { ["name"] = "Center View", ["removed"] = { [1] = { ["key"] = "JOY_BTN5", }, }, }, }, } return diff I duplicated that file and renamed it to WINWING THROTTLE BASE1 + F18 HANDLE {E33C7250-60FB-11ec-8002-444553540000}.diff.lua I still cannot assign the WinWing throttle to the collective function. However I can assign ANY other axis of ANY other controller to be the collective. What do I have to do to get my Winwing throttle to behave for a collective in the HUEY?