BakaNi

These are great! Thanks. I'm sure I speak for everyone when I say: MORE! ;)

If you need to disassemble the stick, you're doing it wrong. Just find a piece of string or two cables ties and compress the spring.

I can almost get the stick to function correctly if I disable the spring and adjust the forcefeed back settings in the saitek control panel. It still has a tiny bit of unrequested movement at the extremities, but otherwise it trims correctly =)

No need to build a patch system, that's over the top, a simple binary diff would save a lot of wasted bandwidth and time.

Any chance of a patch between .93c and this new .94? Seems like a waste of bandwidth to re-download the entire thing. That said, YAY, new version. I've used this tool to debug all my lousy flying habits.

Sounds like rotor rpm is dropping below the minimum speed needed to turn the ac generators. You're either overloaded or trying to push the chopper too hard. Is the engine limit warning light, lit? EDIT: I'm assuming you've got the throttles in the correct position (AUTO - page up twice if on cold start)

Just as a counter point, I've had zero problems with Empire: Total War demo and Black Shark, they don't fight in any way shape or form.

There is no official sli support from nvidia, however some people have reported increases in fps with custom profiles. If the 8800gts cannot provide the speed you require, I recommend you buy a faster single card solution, rather than adding a second 8800gts. Please note that Black Shark is hugely cpu limited, so even my 8800gtx ultra sli is held back by my 3.6ghz processor. More cpu grunt is the key to better Black Shark performance. (unless you're running a stupidly highly resolution screen, e.g. 2560x1600 plus)

You're right, after fiddling with the ForceTest, it's clear the stick has more than enough force to hold it in place with the centre spring functional. I always assumed that the stick was supposed to 'slip' from it's trim position, as the stick in game also 'slipped', it seems the ingame stick is mirroring real life as opposed to vice versa ;) I'm not sure what's causing the trim to function incorrectly, but even with the centre spring disabled, the stick doesn't hold it's place correctly.

The evo force works fine IF you disable the centre spring, personally I've just used some string to coil the spring up and voila, working forcefeed back.

Well done OP, fantastic parody, I'm laughing my ass off over here. I almost believed you were for real, until the dynamiting fishing comment ;)

You can disable vsync with dx10 apps, the statement by nvidia is wrong/outdated. It might be some semantic point, such as you cannot disable vsync globally but instead we just disable it on a per program basis.

Pretty sure BlackShark doesn't use DX10, it's all DX9.

Disable the spring and the EVO works well :) I've removed the spring and the plastic baseplate, works very nicely now.

It's true. -- *facepalm* I've found out why my joysticks aren't behaving themselves and are moving to the centre when trimmed elsewhere. It's the huge and very obvious mechanical spring that's overpowering the hold of the feedback bit. Two solutions, one is to remove the pull of the spring, which I've done with a bit of string, and second is perhaps to increase the power of the force feed back? The motors are pretty strong, I know they're more than capable of overpower the central spring, is there a way of increase the strength of the forcefeed back trim? (The option in the axis menu is already set at 100, I could do with say, 150/200) EDIT: I've found a config file which allows me to set trim force at whatever value I see fit, unfortunately this just results in the same inital trim inaccuracy and a very stiff unresponsive stick, removal of the spring it is!

So just to clarify on the trim. Non-FFB: Point in direction, press trim, hands off stick and let it bounce back to the centre. This works fine. FFB: Point in direction, press trim, stick stays where you trimmed it? With no pressure on the joystick? My ffb trims the chopper, but the stick will have constant pressure on it and will bounce back to centre on release, which causes bad flying mojo. I'm not sure what to expect with FFB enabled, anyone care to enlighten me?

Sounds like some starforce drivers have been corrupted, update them here http://www.star-force.com/support/drivers/ Although, this isn't a dcs bug. DCS doesn't use the dvd checking starforce and those files are not installed. Some other program has installed and possibly broken those files.

SLi is turned on and off in the nVidia drivers, but this is more of a 'master arm' setting. Whether or not sli is used ingame is down to a combination of a global force sli afr/sfr etc setting and per-game profiles. By default all apps should be globally forced to run in SLi:Single mode, which means that sli will not be used, hense it being strange that the launcher.exe should crash when sli is 'armed'. I'm not sure which OS you're using, but in the nvidia control panel, under 'manage 3d settings' is 'SLI performance mode' set as anything other than 'Single-GPU'? If you have a sli mode in that setting, then the graphics drivers might be trying to apply that type of sli to every application it has no knowledge of, hense causing launcher.exe to crash0r.

I think one guy managed to get his microsoft stick working, by swapping the ffb axis. However, none of my ffd sticks work correctly :( They neither stay in place when trimmed, or trim the chopper. http://forums.eagle.ru/showthread.php?t=35039&highlight=frustrated&page=3 - That is the thread I first noticed that mentions problems with forcefeed back and trim.

Sli really shouldn't be crashing your system. Which version of the Nvidia drivers are you using and are you forcing on global sli in the drivers? Sli isn't very useful for DCS, I've only managed negative performance with sli enabled, maybe you'll have better luck.

Trimming doesn't work with force feedback, you'll need to disable it in the Producer.cfg file. Here's hoping ED will fix it in a patch.

You can start the Ka-80 without ground power and purely off batteries, I do it every time as I can't be chored to mess around with ground staff. If you watch the track, you'll see that whilst the landings are pretty poor the chopper is down, braked, shut off and not moving. There is a slide to one side, of a few centimeters every few seconds

I did that, the chopper still slid sideways for no reason. I've included a track, notice how the chopper slides to the right on both the aircraft carrier and the OHP (to it's doom). Slide on Landing.trk

Excellent, someone posted a screenshot of the exact effect I was seeing. Even with 16x AF and forced high quality textures, 'fuzzyness' still creeps into some of the instruments when fully zoomed out :( Although in fairness, it is pretty minor.

Thank you for this mission, it turns out that I can actually land the Ka-80 after all! Unfortunately whenever I land on a ship, the chopper slides very slowly to the right, for no reason what so ever. I landed on the OHP and watched as my helo slid off the side and into the sea :( Any reason why this happens?