BBQ

Example README.txt This could be a lot better -- but as I didn't develop simFFB, and am writing this from memory. It's a start, anyway. simFFB README by BBQ (user, not author) **Description** simFFB.exe is a small program used to control how forcefeedback is implemented on your controller. **Installation** Simply place the simFFB.exe file in a directory of your choice (does not have to be in the game's directory). **Uninstallation** Simply delete the simFFB.exe file. **Usage** After launching simFFB.exe a graphical user interface will appear. There are a number of settings and menus: Pulldown Device Selector: use this pull-down menu to select your forcefeedback capable device. Number box next to Device Selector: after choosing your device, use this pulldown to select with button on your device will serve as the "trim" button. NOTE: Be sure to also map this button to the trim function within the simulation. Spring Force: set amount of spring desired Damper Force: set amount of dampening desired Friction Force: set amount of friction desired Trim Method Menu: Initialize: select this item once you are happy with the settings -- this is the final step Instantaneous: select this method for instant trim (upon release of the trim button) Progressive: select this option for progressive trim (needs further explanation) Both: some simulations/aircraft can utilize both methods, in which case you would want to select this option. ****NOTE: In some simulations, e.g., v126 of DCS: World, you must first load the simulation world (i.e., load a mission) -- and then once you are in the cockpit, ALT-TAB back out to Windows and launch simFFB.exe and select "Initialize"; then you can ALT-TAB back to DCS:World and you're all set. Failing to follow these steps may result in no forcefeedback in your controller.

RE: glovepie Awesome -- thanks

The word that seems to be missing from this thread: oscillations So when I'm constantly making micro adjustments to the cyclic, it would soon get hard to manage as without dampening, nothing would be prevent my input corrections and over-corrections from adding up (e.g., I pull back, but went too far, so push forward, when actually I should have waited a second or two for helo to respond to initial back pull, instead, end result was that I was pushing forward when helo was also pitched forward, etc., ad infinitum, until someone in a village below you calls the local radio station and reports some "porpoise-like" object flying through the sky. It's much easier when the inputs are dampened and the oscillations cancel each other out, or are lessened in some way. Not sure how it actually works mechanically or electrically or pneumatically, or hydraulically, however it may be in the Ka-50. From an article about tight-rope walkers: He designed a means of safely anchoring both ends of the cable both at Niagara Falls and the Grand Canyon where no suitable infrastructure existed. Perhaps most notable, he designed an innovative means to stabilize the cable and dampen oscillations. Highwires in a circus tent or at an amusement park are only 30-50 feet above the ground, and are stabilized with a system of guy wires attached from the main wire to the ground below. This is clearly impractical at the heights of Nik Wallenda’s stunts. “Michael designed a solution wherein the cable is stabilized with a system of pendulums made of weights suspended by smaller cables attached to the main cable. The engineering problem was to determine the number, spacing, length and weight of these pendulums needed to counter the effects of wind and the vertical oscillations created by Nik’s steady cadence as he crossed the wire.”

Awesome analogy -- well done :)

Was wondering what the increased traffic in this thread meant -- then remembered the sale that's going on! I encourage everyone to try the Ka-50 -- really anyone remotely interested in a helo flight sim would be foolish not to pick this one up!

I was specifically NOT given permission to release the Russian version. Perhaps the producer's will update the Russian version and release that on their own.

That sucks! Wish I could help you -- if there's someplace else where you could access them, let me know, I might be able to upload them again (no promises).

You, and everyone else who gives it a try are in for a great bit of campaigning! I would agree with the others that stated it's the greatest campaign to grace a flight sim. Hand's down. Enjoy. I sure did :P

The campaign has been updated. Click here to navigate to the relevant thread.

**UPDATE** 19AUG2017 Please use the link below to download this FREE campaign. Updated to be compatible with current DCS World Open Beta 1.5.7 NOTE: In Mission #2 there are two separate flights in this mission -- the first led by one leader, the second led by another. Near the end of the first flight, when you are nearly back to the base, you'll be instructed to quickly land and refuel and then hover at the end of the runway to wait for the second leader to appear. You've only 10 minutes to do this. In reality, it's more like 15 :) With permission from the producer's of the Vergeev Group Campaign, I'm proud to announce the availability of the English version of the campaign, fully updated to be compatible with the current (1.5.7) version of DCS: World. I spent at least 100 hours testing all of the missions and working out the bugs that prevented normal users from enjoying the campaign. This is my way of giving back to our wonderful community. If you're not familiar with the Vergeev Group campaign, check out this short video I created: Download Update **All credit and copyrights remain the same as the original, i.e, Roman Leroni of the Vergeev Group and DCS.**

Not sure I understand issue -- but if you're expecting some coordinates from where you have your Shkval pointed, be sure to set the left switch (below the PVI there are two switches) to the Shkval setting (I think it is the "up" as opposed to "down" setting).

Is using simFFB a temporary workaround for this issue? Not the missing shake feature -- but the input delay and general FFB features.

Oh man, no wonder I never seem to get consistent settings. I thought you just had to launch DCS first -- and then started simFFB -- and then "launch" a mission. You've clearly stated though, that I need to launch simFFB after the mission has loaded, and not before, correct? That is, you don't start simFFB until you're actually in the game world? It seems clear that you are saying this -- but I just wanted to confirm since you've hinted at English not being your native language -- My proof-reading offer is still good of course (for a Readme)!

Looks like it might be related to this new FFB problem introduced with 1.2.6.

I'm having the exact same problem in the Blackshark -- wonder if that file exists in the Ka-50 folder. Will check when I get home. Got home -- unfortunately there is no such option (sticktimelag) in the corresponding Ka-50 file :(

I'm pretty confident it's happening in the Ka-50 as well -- it would explain a problem I've been having lately with the trimmer. Going to test it when I get home.

Of course every time I specifically set out to record this phenomena, I can't reproduce it -- but thought I would ask community at large if anyone else has noticed this behavior: When coming to a hover, I'm obviously pitched up to slow down until I more or less stop forward movement. At this point I've got the trimmer punched in and held, so that I can compensate for wind, etc. -- so end result is I'm hovering manually with zero vector, and then I release the trimmer, then engage hover-mode. That's my modus operandi. Lately though, it seems like 50% of the time (usually when I'm in a hairy situation of course) when I release the trimmer, the nose drops a few degrees and I end up moving forward. This is before I engage the hover-mode. I then pull the nose back up again and attempt another trim. Sometimes it takes up to 10 attempts until finally it will hold the nose where it's supposed to. I started to notice this after the 1.2.5 update, which included "Better support for force feedback", and wonder if it has anything to do with that -- as indeed, I use a Sidewinder 2 with FFB enabled. I've tried to also use simFFB.exe to control FFB, but I get the same "nose-heavy" result most of the time. Anyone else notice this lately?

I guess your point is why would pilot want to turn light off and not retract it? One reason might be for morris-code type signaling -- say, for a downed pilot, or wingman when secure comms aren't available for whatever reason. It wouldn't work if you had to retract light after every single "blip".

Maybe I haven't recovered from the weekend yet - but isn't this exactly what you were expecting? (middle position light is OFF but NOT retracted)? I.e., you have to put switch in down position in order to retract it.

Aside from the first, the rest of the images are from various missions in the Vergeev Group campaign ...

Unfortunately no -- if anyone sees Leroni around the forums, please let him know about this thread! I've already sent him an email --

Thanks for info -

I checked the /Mods/Aircrafts/Mi8.../Docs folder and could only find a russian flight manual (DCS manual) -- is the English version not finished yet?

I saw the other thread, and thought we could use one thread for everyone to post their first flights in --