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!