ZaltysZ

This will solve not only an axis limit problem, but will rise count of available DX buttons. I personally don't like mapping HOTAS buttons to virtual keyboard, because its is problematic. I either have to create my own keyboard profile for game and assign single keys for HOTAS, or I have to program my stick in a blocking way (so that one multikey keystroke could not interfere with another one) - what really kills effectiveness of HOTAS. It is way better to work with DX buttons only, as they are easily assignable in game and they do not conflict with each other. The only problem - there is 32 button limit per controller. In case of Warthog, there are more than 32 buttons in HOTAS, and almost all of them (except 4) have their own functionality in DCS: A10. This means that if you want to stick to DX buttons, retain functionality of all buttons and program Warthog, you either have to exclude throttle or stick from virtual controller. I.e. I programmed my stick so that I get narrow FOV on depressing the lever and wide FOV on releasing it. I want to have left mouse button mapped to MIC button on throttle, but I can't (unless I choose to use virtual keyboard for part of my HOTAS buttons). Having more than one virtual controller would solve that.

Depends on how damaged the nerves were. If they had severe damage (i.e. numbness was present), operation could not cure her, but it probably stopped illness from progressing further.

The source of carpal nerve syndrome can be any activity in which you keep your wrist bended for prolonged time, especially if that activity is stressful. Incorrect work with keyboard is usual cause, but not the only one. People doing packaging work, or constantly cutting something hard (stiff meat, bones) can easily get this problem too. Same goes for ulnar nerve syndrome, but instead of wrist it is about elbow. Sleeping with your arm bent, holding bent arm on hard arm rests or table can cause ulnar nerve syndrome. Sometimes it is very easy to blame your toys (stick and throttle), especially if you feel tired after using them, however the cause can be something else too, so it is very worth to analyze your activities once you see symptoms. Don't wait to long. If non intrusive methods don't help, go for surgery. Don't forget that once your nerve gets messed up, it won't recover, so waiting too long can be very regretful.

Unless you have eye tracking, and DOF effect depends on where you look with your eyes (and not on where came is centered at), DOF will be very unrealistic if applied while playing.

Sometimes it is possible to get 10-15% increase in FPS. Well, sometimes... :)

Just finished reading half of that Russian thread. Basically FC3 is LockOn planes in DCS: A10 world (as far as possible, i.e. no complex radio comms) and nothing more. Maybe few bugfixes here and there, and that is it, because devs don't have enough resources for something more. FC1 -> FC2 was attractive even after price went up, but unfortunately I think FC2 -> FC3 won't look so reasonable if the price will be the same.

Or just enter target altitude, which was told by JTAC.

I usually modify my flight plan on startup and add one additional waypoint for target. I select it and open its page in CDU before contacting JTAC, so that I can change its coordinates quickly. This approach has advantage in that, I don't have to switch to Mission or Mark modes, whose lack flight plan. Having target, ingress, exgress or other important waypoints at the same time in TAD is very handy sometimes.

No, unless it is made as option. I use that yellow cursor in combination with TrackIR and left mouse button mapped to HOTAS for clicking cockpit switches.

Yet another periodical A2A thread. Henchman14, you should try using forum search function; this topic has been discussed multiple times and in kinda great depth. The summary is as follows: 1) Things won't be altered just because simulation is too "hard". Compromises for sake of gameplay aren't the aim of DCS. 2) Ka-50 does not carry A2A weapons in service. It does not matter if there were experiments or plans for A2A missiles. Only production model matters. 3) Most internet sources include too much advertisement information for masses (dating back from previously popular arm races). 4) It is matter of doctrine that helicopter should not operate without adequate air cover. Ka-50 purpose is CAS/Anti-armor. Other [suitable] aircrafts should be responsible for taking care of enemy air defenses and planes.

It is possible to solve taxi problem by adding table for each airfield diagram. It should contain: 1) Spawn spot ID 2) Latitude/longitude coordinates Then diagram should contain all spawn spots marked in it. Pilot will only have to look at his current position in CDU and check it against the table before taxing.

Maybe you were playing with "Radio assists" or whatever it is called? My Ka-50 have never said anything except "Берегис! Атака" regarding laser.

Bravity code exsits for minimizing radio talk and for this: , NOT to happen. :)

All device included in TARGET profile are disabled once it is running, and you get an aggregated virtual ThrustMaster device, to which you need to bind your controls in games.

Q: I have loaded right TARGET profile and my controls are messed up in game. A: Make sure that you load TARGET profile when nothing is using your HOTAS. If you don't do that (i.e. if you load profile when some game or other software like TS3 is running and is bound to some buttons or axis), TARGET will fail in hiding controllers included in virtual device and game will get confused. Q: I have created my profile via GUI, but I needed advanced functionality, so I edited the script. It worked, but now it doesn't. A: If you open the profile (not the script) in GUI, TARGET regenerates the script every time the profile is saved or launched, and your custom additions "by hand" do not survive. Q: I am using only part of the buttons for Game-X (where X is not DCS :) ), so my profile is thin, however some buttons, whose I haven't assigned, sometimes have effect in game. A: Controller reports every button as DirectX button. By creating a profile, you can assign different DX button numbers or key presses to each button; when you do that, unassigned buttons may get DX numbers shuffled, shifted or doubled. To be safe, assign special "null" action to unused buttons.

If you have 2 FFB devices connected at the same time, only one will get FFB effects. I remember this from someone who tried to make FFB pedals. If you have FFB wheel, unplug it. Next, I assume you have problems with DCS based product (Ka-50, FC2, A10). Simply go to control screen, choose all from category list and clear every assignment from G940 column. Every device has separate column, so if you have many of them connected you might need to scroll control grid to side. After you have cleared the assignments, choose a category from list and begin assigning controls by your liking. You just need to click a cell, then click ADD button and press or move your controller - button/axis will be autodetected. Nothing hard.

It is common for USB to supply power when PC is off. However, devices, whose do not need it, should enter a low power state on computer shutdown. Obviously WT does not do that or it thinks that "lights on" belongs to low power state. Thrustmaster should be pushed to fix that, although their are already working on it in some way. I just hope, that their upcoming back lightning control function won't require a script to be running. :)

Serial #: 03151 Location: Lithuania (bought from Amazon UK)

I do not own CH stick, but I suppose it has separate springs for every axis. This makes diagional movement require more force than moving only in one axis. The stiffer the springs, the more apparent it is, so you may not like the result. You can try adding rubber boot. The additionally required force will be even to all directions, however the more you deflect the stick, the more force you will need. It is kinda cheap to do. You just need to choose correct cv joint boot (car part), "trim" it and fit between the base and stick. http://images.outdoorpros.com/images/prod/6/Dorman-03601-rw-49035-61784.jpg

Where are you from? If DHL Paket International is used for shipping, Amazon shows nonsense for tracking information. Try entering tracking number here: http://nolp.dhl.de/nextt-online-public/report_popup.jsp .

Try adding additional axis #8 and mapping "sacrificed" axis to it. #8 won't be seen by games, but adding it will likely allow to assign one ministick axis to #0-#6. These registry keys map axis reported by driver to DirectInput axis. Arbitary combination is not always possible (i.e. you can't just skip axis and order is usually important). --- If someone wants to get IDs of axis, they can try opening Saitek profile with notepad. IDs are in it. For example: [axis=0x00010036 name='Precision Slide'] In registry it should be used as: 01 81 00 00 01 00 36 00 --- I have attached registry file for "classic" X52. Ruder twist axis is "sacrificed" for ministick in it. x52_ministick.zip

Teej, maybe you have to much things going in POST? I.e. memory check, initialization of not used hardware like additional SATA controller, or large boot order list in which your HDD is not at first position? 35s till seeing Windows boot screen seems extreme for desktop PC.

From TM docs I assume that you need to run firmware updater twice (once for stick and once for throttle). Dastardly, have you done that when you updated firmware?

Welcome to the proper flight simming. Expect about 1 month to pass before you completely get used to pedals. Time and practice is needed for legs to learn how to be less clumsy and work in coordinated way. After that, you won't even look back.

It is a question not about what human eye sees, but at what frame rate human brains sees the sequence as smooth. This strongly depends on scene. Low detail scene can look smooth even at 15FPS (especially with motion blur like in movies), but sharp, detailed and rapidly changing scene can look like it is stuttering even at 60 FPS. Technically it is rectilinear projection (view is not curved, but stretched at edges), not a fish eye projection. 180 FOV with rectilinear projection is far from playable, but for sake of "sense of speed" experiment it will do the job. Something like 150 FOV would be more playable.