CyBerkut

Answering that question is an exercise best left to the forum's search function. :) I don't trust my memory on that, and besides, there are likely to be posts that I haven't seen/read. I do seem to recall a posting that indicated that the problem would be brought to the developers' attention.

It's external. It pushes down from the base of the grip upon the beveled plastic plastic centering ring. For a quick test, just get 2 or 3 garbage bag twist ties threaded in and compress the spring with them. The weak force generated in the stick (when being used in DCS:BS) then does not have to work against that spring to hold the trimmed position. As mentioned before, it's puzzling, as the stick can physically generate more than enough force to overcome that spring and solidly hold the stick in any off-center position.... it just won't do it with DCS:BS and the (current) Saitek drivers.

That largely depends on a combination of what your expectations are, and what you are willing to do. If you want/need something that holds really solid and without making modifications to the stick beyond a few software settings... the issues are definitely not solved. If you can live with a light holding force, and compressing the centering spring (ie. with twist ties or cable ties)... then the issues can be mitigated (or at least mostly so). It's not ideal, that's for sure.

Looks nice and clean! Hopefully you kept the traces spaced far enough apart... :P Trigger, you continue to impress! I'm looking forward to more about that mechanical trim, when you get around to it. Good luck with the pilot's license!!! :pilotfly:

Not to detract from TouchPal (as it is a *wonderful* application!)... but did you realize that you could use the touchscreen monitor to touch (and operate) the switches in the cockpit view? I'm not saying that approach is better. I just get the impression from the way your message was worded that you may not have been aware of that possibility.

A couple of observations here: - We've seen E.D. be responsive on all sorts of issues. - We've seen Logitech become markedly non-responsive on G940 issues shortly after it became available for sale. As in, Logitech Mark disappeared from the forums, etc. Given those behaviors, I think it is much more probable that the needed fix lies with Logitech (ie. their drivers, profiling software, or the hardware's firmware). It would be great if E.D. somehow fixed it, as it would be nice if they could do the same for the Saitek Evo Force. But it probably isn't fair to lay blame upon their doorstep. That's how it looks to me. Others may see it differently.

As far as I know, the old Microsoft Sidewinder ForceFeedback 2 is still the gold standard for DCS:BS. Production stopped on them years ago, but you can still find them via on-line auctions, etc. It is possible to get one in very good shape. (New in the box unfortunately will generally cost an outlandish amount). The Saitek Cyborg Evo Force can be made to work, with the caveat that it doesn't exhibit a strong holding force in the trimmed position. Search the forums and you'll find plenty on that, including recommended settings / mods (ie. disabling the centering spring with twist ties). It's vexing, as the Evo Force can generate plenty of force, it's just that the software is not making that happen for reasons we still do not know.

Some related information available out on the web: http://handle.dtic.mil/100.2/ADA198785 http://handle.dtic.mil/100.2/ADD018494 http://handle.dtic.mil/100.2/ADA153922 http://handle.dtic.mil/100.2/ADA219481 http://www.control.isy.liu.se/~fredrik/reports/05bearingsonly.pdf http://www.sciencedirect.com/science?_ob=ArticleURL&_udi=B6V18-4RJRVH7-2&_user=10&_coverDate=06%2F30%2F2008&_rdoc=1&_fmt=high&_orig=search&_sort=d&_docanchor=&view=c&_searchStrId=1277037444&_rerunOrigin=google&_acct=C000050221&_version=1&_urlVersion=0&_userid=10&md5=44f9a4c34da1a47c476720c5bb295a2d And no, I didn't read all of that. :P But even quick skimming of that stuff reveals that a lot of investigation into the subject has been conducted with an eye toward getting more useful/useable answers.

The motion is seconded! :thumbup:

Hi Lightning, Your ATI 5870 is capable of driving three displays. Presumably, you have 2 DVI Ports, 1 Display Port and 1 HDMI Port. Both DVI ports can be used. In addition, you could obtain an "Active" Display Port to DVI Port adapter. Emphasis on the "Active", as opposed to the cheaper passive adapters that are out there. The Active adapter is needed because it injects a timing signal that the 5870 card is not providing to the Display Port (when both DVI ports are in use also). There should be plenty of info from various sources out on the web. Look into the "Eyefinity" capabilities of your ATI 5870, and you may be able to get what you want via your single card. :)

Perhaps there is no other good reason for *you* to buy it sooner. Oddly enough, there are a slew of other people who are itching to get their hands on all of the available improvements made, ASAP. Getting DCS:BS compatibility later is basically the 'cherry on top'. If you did buy it before the DCS:BS compatibility patch is issued, it would give you time to come up to speed on all of the additions/changes in FC2. It's your wallet and your calendar... operate them as you see fit.

You might check into LEAVU 1.x. I'm not sure what is in there, but Yoda is currently developing LEAVU 2.0 for FC2, and it appears that it will be quite spiffy for MFDs.

Cp, you can always screw it down on to a board of whatever size you need ( A pre-made bookshelf board with a laminate surface worked well for me ) and then C clamp the board to your desk when you want to fly. That's what I did for my Saitek X-52 throttle and stick. I just C clamp it to the keyboad drawer.

It's definitely a bummer that you are having so many problems. Mine has worked well with both Win XP and Windows Vista. 1st off, if the pedals are working well for you, I see no reason to abandon them. As for the X-52, I'm wondering if at least some of the problems you are listing might be related to drivers / software. I have no idea what you have tried so far, or what versions you are running. If you have not yet tried a different version of the drivers & software, I'd start with that before completely giving up on the X-52. Good luck!

Mmmmm... I finally got my TriggerHappy fix. I've been jones'n for months! Welcome back! :D

Very nice! :thumbup:

Yes. You obtain a "Touchscreen Overlay" and install it upon the monitor. Usually by removing the bezel, placing the overlay and routing the cabling, then reinstalling the bezel over it. You may want to check out the TouchBuddy forums for information on overlays, as they probably have at least one thread on it. There are a number of sources for buying overlays. Along with a number of websites for manufacturers, etc., I've seen overlays for sale on eBay. One thing to watch out for is height vs width ratio. If you get a widescreen version for a 4:3 screen, or vice-versa, you will not be happy.

Why couldn't it? It's not hard to imagine that a more powerful engine might need an improved control system to get more useful results. If the steering surfaces and/or control system are now inadequate to make the needed turns with the more powerful engine, it's not an improved performance. NOTE: I'm not saying that is the case in this specific missile system, as I have no idea. I'm just saying that 'missing the target faster' is not really a useful improvement, and that there are more factors to consider in missile performance.

Ahhh, a nice little tidbit in there. :thumbup:

Thanks for the update!

FWIW, on my Vista64 laptop: Opening the Profile Editor and checking the "about" screen reports the SST version as 6.6.2.0. Control Panel properties for the X52 reports Driver Version 6.0.4.1 and Software Version 6.6.0.38

Hmmm... Didn't happen to me on my Vista64 laptop. I'm not at home at the moment, so I can't check version numbers on my SST or drivers. IIRC, the Magic Bus is related to the mouse functions (mini stick and related buttons on the throttle). It might be worth checking out Saitek's forums to see if the problem has been reported by others, etc. (Of course, you may have done that by now...).

Unless I'm misunderstanding you, that capability is built into DCS:BS. Camera + Shkval.

Which "cheap adapter" did you get? If it is available to others (ie. not a 1 shot eBay auction), where did you get it and for how much? (If you don't mind sharing the info). Thanks!

JD, which Operating System are you using, and which version numbers of the SST software and drivers do you have installed?