CyBerkut

I use Vista 64 bit. The reason you want the latest beta of the SST software is because of how it handles differentiation between left and right common used shift keys (ie. CTRL, Shift, ALT and Windows keys). DCS Black Shark uses both left and right versions of those keys separately. The latest SST beta will accomodate that fully, whereas the earlier versions do not fully implement that. By using the latest SST beta, you should be able to leave DCS:BS key mappings as their default settings. If you use an earlier SST, you will need to change some of the DC:BS key mappings... which in turn means that you are more likely to have to make additional adjustments to any SST profiles (for DCS:BS) that you download from someone else.

Ogiedogg, there have been many of us who managed to overlook the axis pull down selection initially. It must be some sort of human factors / design thing. Glad to hear you have that whipped. If you have the latest beta version of the SST software and drivers working, I'd suggest using the BS controls panel for setting up the axis designations, and then using the SST software for the keyboard commands. You can save yourself a lot of typing (of the command key sequences) by downloading someone else's profile, and then editing it to your preferences. Keep in mind that current SST software uses .pro files for the profile, whereas the original versions used .dat files. They are not interchangeable. Note: If you don't find an X-52 profile, you can download someone's X-52 Pro profile, and then convert it by selecting the X-52 controller instead, and then tweaking it. Enjoy!

My guess is, "Low Observability Restoration", as in special work that needs to be done to bring it back to low observability.

To get back on topic, in response to the OP's question... I'm fine with all the additional gizmos. The previous respondents have covered the subject pretty well already, and they make good points. For me, I'm not particularly hard core about realism. I can be happy getting immersed into something that doesn't necessarily match up with how things are arranged in the real aircraft. A closer match is better, but all of us are making concessions to some degree or another. It's a matter of resources vs. priority. Whatever people are having fun with in conjunction with E.D.'s software, it's good for our sim'ing community.

No offense taken. I was told by someone a few years ago. I adopted the handle long before that though, as a concatenation of Cyber and Berkut (seemed like a natural). I had the subspecies of golden eagle, Aquila chrysaetos daphanea in mind, not the plane(s). Mongols have hunted wolves with them, and they regularly take fox with them. I seem to recall they have been used to hunt tiger, but don't take that as written in stone. I guess it is fortunate that I capitalized the "B" and not the "k". :)

It seems odd in light of what you are saying (and in light of Innobec's web site not listing Vista as being supported) but http://www.winexpertpro.com/innobec_sidewindow_1_2_0_0_12563.htm has Vista included on its list of supported Operating Systems. Here: http://apps.innobec.com/apps/sidewindow/ Innobec says they don't support Vista, but have plans to make a Win 7 version which would also work on Vista... so it may be a matter of waiting for that.

It's difficult to predict whether the buttkicker will help you with *that* movement, or hinder you... The triple head 2 go seems like overkill frankly, as 1 head should be enough (and less confusing, too). And try to lay off the TouchBuddy while you're in there! :smartass:

Yes. Yes. Yes. :)

It's stuff like that in the past that led me to changing my Windows Update settings to notify me instead of automatically installing. I generally go ahead on security related items like Windows Defender and Internet Explorer updates. Updates to things that are already working, such as my ethernet, I usually leave uninstalled (The ol' "If it ain't broke, don't fix it" approach). I've had MS drivers for Saitek controllers "break" the SST software before, so I defer to Saitek's drivers unless I have a compelling reason not to.

http://forums.eagle.ru/showpost.php?p=630153&postcount=3

I don't think it is the rendering of a huge resolution that is the likely issue... The reason I think that is because people use an 8800 to render a humongous resolution for a Matrox Triple Head 2 Go, with satisfactory results. With that arrangement, the 8800 is rendering a large resolution, but it is not having to communicate over a bottleneck with a slower secondary video card.

Sounds great! What are you getting for frames per second, and jitter now?

I'm not sure what it is you think I should be letting go of. The post you are replying to was a fairly simple, straightforward statement of what I would be willing to spend money on. Prior to this reply, I've posted exactly two times on the subject. http://forums.eagle.ru/showthread.php?p=656525&highlight=English#post656525 http://forums.eagle.ru/showthread.php?p=666710&highlight=English#post666710 I intentionally refrained from chiming in on the more recent thread/debate since I didn't see anything good coming out it. E.D. announced their decision on what they had made available, and I respect that. Having been a business owner in the past, I am accutely aware that in such cases it is impossible to please everyone. There were a number of factors contributing to their decision, and it was understandable. No need for me to pipe up with a complaint... I would just continue using the printed copy of the .PDF manual I already have when the motivation hit me to put up with doing the visual/mental gymnastics. Then this thread/poll came up with a legitimate question. OK, a new opportunity arrived to possibly get something that I would value enough to spend over $60 on. I said my piece, and like before, I would have just left it at that. There has been a great deal of rancor over in that other recent thread. Some of the posts in there appear to be a lot more about preaching at others about how the simulation should be used, rather than what is in the best interest of E.D. and its customers. I understand some people wanting to use the sim with cyrillic labels. Making it out to be a superior methodology or somehow more correct/valid than other people playing with english labels is a bit ludicrous and shortsighted. What is good for them is good for them. That's fine. But getting preachy about it toward others does not serve to bring more customers into the fold. If the purist simmers think that espousing such positions is good for the community, then it is more likely to stay a smaller community. *That* does not serve to encourage E.D. or other software companies to invest the resources into creating simulator software for us. I also understand those folks wanting cyrillic labels in the manual pics. Well, now they have them in a printed manual (B&W). They also have them in color in the original .PDF. They have been served. Will the rotor blades permanently fall off everyone's masts if E.D. publishes a manual that has pics with english labels? Oh, the horror! I made my earlier statement in this thread because that it what *I* would be willing to pay extra dollars for. I will now point out that (contrary to some claims in that debate thread) the poll running in another thread about what labels the english speaking north americans are running indicates 66% english as I write this post. I am not going to sit here and claim that represents equivalent sales of manuals with english labels. I have no way to know that, and frankly, it is E.D.'s concern to figure that out (if they are interested). I'm simply saying a bunch of other folks should probably stick to making their own case, and refrain from projecting for everyone else. *My* case is that english labels would add value for me, such that in a nice printed manual (ring bound or spiral bound, they each have their advantages) I would be willing to spend $80, or possibly even more. In *my* case, having to deal with cyrillic character conversions is extra work that I don't find enjoyable. It detracts from my enjoyment which translates to less time spent studying/using the simulator. It also happens to make it harder to recruit other acquaintences of mine to join our community. E.D. will do what they think is best. If it adds enough value for me, I'll buy it. If it doesn't, I'll remain O.K. with that, and continue using what I already have. Regards,

I'd spring for a printed color manual IF it had english text labels in the cockpit pictures instead of cyrillic text labels. For that, I could go $80, or maybe even higher.

Hehehe... happy to help out! I took the less blunt approach in part because I felt it was prudent to allow for the possibility that I might be wrong. I know, I know... it hardly seems possible, but it does happen occassionally. :lol:

Just my guess here, but I'd suspect the 6200, or rather, a bottleneck being created by the 8800 having to communicate with the much slower 6200. As someone suggested, if you have another computer that could handle the TouchBuddy over a lan connection, you may get more satisfactory results.

Put your rudder pedal and X52/X52 Pro setup in the same SST profile. Selecting it should load both controller configs, I believe.

The Saitek software / drivers may have installed something that is conflicting with your mouse. (ie. The X52 and X52 Pro have a mini stick on the throttle that is actually a mouse by default). Before you go into your Windows control panel and start ripping things out though, check your Black Shark controls settings (don't forget the often overlooked Axis tab !!!) to see if you have a conflict in there, since that is an easy place to fix it. As you may have already seen in other threads, the Saitek Cyborg Evo Force can be demonstrated to have plenty of force capability... but it is also known to be less "forcefull" in Black Shark. Whether this is a bug, or the result of the 20% authority that the autopilot on the controls being modeled accurately is debatable. Along with the settings you mentioned (which leads me to believe that you have read other threads in these forums on this) some of us have gained improvement by physically disabling the centering spring. Garbage bag twist ties are a quick/cheap way to accomplish that, to see if it helps (when done in conjunction with the settings). If you get the force feedback trim to work, then you don't really need the stick to center any ways. Good luck with it!

I can't say that I blame you. (Hell, I always go with commercially produced power supplies for anything I put together!) It still may be though that your discarded power supply project would actually deliver the desired voltage under load. But I wouldn't test it by hooking it up to the mill, that's for sure!

Some possibilities that come to mind: - Teamspeak. Sometimes it is useful to see who is transmitting (ie. open mikes, or ppl you haven't learned to recognize by voice yet) - Temperature monitoring. If you're on a machine with potential heat issues (ie. a laptop) - Multiple screen users. Some of them have funky configurations and using windows may make things fit/work. - Configuring / modifying controller setups. - Reading manuals/tutorials/references. - Following along with a video tutorial. - Severe porn addiction. (Not to be taken as a recommendation... :smartass: ) - Maybe even somebody developing a TouchBuddy application (for BlackShark, not the porn...) - Checking the affinity and core utilization to see if DCSMax (or the other affinity tools) are having the desired affect, etc.

Trigger, have you put any load on that power supply yet? (I'm curious what the voltage went to).

Yes. It's frustrating how often these computers do exactly what we tell them to! ;) Very glad to hear that you have it whipped! :thumbup:

Right now I'm at work, and some of the pictures aren't coming through as visible (happens pretty regularly). Of the ones that I can see, the voltmeter labels are a bit too blurry to read well, (so I can't tell if you have it selected to VDC or VAC, for instance). Since it appears to be easy for you to try different configurations, try the following: With the standard configuration, measure both Volts AC (VAC) and Volts DC (VDC). With the capacitors removed, measure both VAC and VDC. ----------------------------- With the capacitors removed, you should see a lower VDC value. When capacitors are installed across the output of a properly functioning full wave bridge rectifier, the capacitors will charge up, "clamping" the DC voltage to a higher level than you would see with the capacitors removed (See the right side of Oakes drawing in post #562). The degree to which the capacitors will be able to keep the voltage clamped higher will vary with the load placed upon the circuit. Right now, you appear to be measuring the circuit with no significant load upon it. If you measure it with a significant enough load upon it (use something unimportant to try it out) you will see a lower VDC at TB7. The reason this happens is because the significant load allows the capacitors to discharge (and the recharge, etc., etc.), so the circuit's output voltage can drop down (more "ripple" means a lower average voltage in this case).

No, it doesn't solve that mystery, to be sure. It is cause to re-perform the measurements though (which is what I think Trigger indicated he was going to do). Trigger, is anything else hooked up on to those terminals of TB7? If so does that component have any other power sources that could be putting voltage on to the TB7 terminals (either by design, or by some unexpected component failure)? Also, can you confirm that you took the measurements leg to leg (as described earlier)? And just because it is easy to do, have you checked the fuse?

Thanks, PoleCat.