skypickle

any idea where i can find the pictures?

I have noticed that DCs sometimes restricts whether certain controls can be assigned to specific controllers. You can identify these forbidden assignments in the controls setting dialog because they have a darker blue hue. How can a controller be 'enabled' for binding a function? For example, in cockpit visual recon mode where you also need mouse left clicks and right clicks? I guess the most generic solution would be to allow mouse clicks to be bound to any button.?

is there a way to have different weather in different regions of a map? I'd like to have a cyclone that a flight has to navigate around (if the pilots are situationally aware).

Why is this better than changing the normal to 'toggle on'?

@HemiGuy Thank you for posting this. I was looking at your assignments for the T switches. Did you change these in the virpil software from normal to switch or toggle? For example, in normal mode, the T switches only send a button press in the up position. So how do you get landing gear to go up?

The Virpil cm3 throttle has a multitude of hats. Most of them have unique tactile design to allow you to know which way they are oriented. They have a ‘castle’ or ‘rook’ style top and the 4 cardinal directions in which the finger has to move the hat are obvious. Except one. There is a 4 way hat centered on the rotary encoder on the medial side of the throttle. This hat has a conical shape. Although there are facets on the hat, I often find myself pushing it the wrong way. Part of the problem is that as the throttle is moved through its excursion, the orientation of the hand on the throttle changes so you have to push the finger (usually the thumb) in a slightly different direction to achieve the same direction on the hat. It would be so much easier if the hat had the shape of a cross. Then I would know exactly which way to push the hat simply by feeling for the appropriate arm of the cross. I don’t have a 3d printer nor any experience with 3d cad. Has anyone made a snap on improvement?

@TED please point me to your 6900XT adventure

Is there a simple 'how-to' on this for setting HMCS settings?

In the A10C_][ it is possible to change which symbology is provided by the HMCS and whether it is occluded by the HUD. In which lua file is this information stored? I would like to save a setup so I dont have to spend time at the beginning of each mission click a bunch of virtual buttons.

Attached please find my virpil config. Since I am using a newer firmware, it looks a little different. My maximum step value is 255 but I was using 16. I also had buttons 2 and 3 in the opposite locations to yours. Now reconfigured it works, although not as smoothly as using the flaps lever- I get discrete jumps but useful. I dont know why it was spazzing out before-as if it was registeringthe physical buttons instead of the logical ones.

I have been able to escape vrs in dcs by rolling the cyclic to the left, with a lot less altitude loss than dumping the collective. Even with very little forward velocity. I think this has been described by Vuichard.

@imacken The encoder is about the ONLY button that cannot be an axis. because of the way it works, ( sending two physical button clicks with each click - the order of which determines which logical button is sent to windows) any attempt to create a virtual axis from an encoder creates a ‘schizophrenic’ behavior. You can see this in joy tester when you turn the encoder after assigning it to a virtual axis.it’s tracing is sawtooth. You even alluded to that in your post above. Yeah, zoom needs to be a real axis. Even using the encoder with the longest delay setting, 140 ms, helps but it is still weak and stuttery. I think the firmware needs to be rewritten to allow encoder dials to act like real axes.

@CrashAlotsetting the encoder to delay to 140ms makes the encoder 'more aggressive...essentialy each click of the encoder results in the keypress being held down longer. Of course it would be nice if the encoder could be an axis. And an axis with 'acceleration' like mice....spin it fast-move a lot, spin it slow-get high resolution.

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?