Feuerfalke

I'd say 33°, measuring from the pivot point. But lets not argue about it. The Warthog has range of roughly 23-25°. With the extension, the travel distance on top of the stick changes, of course, but the angle stays the same. And of course you can still add the BU0836 and an extension to the Fighterstick, too. (Actually, I found the Fighterstick pretty easy to extend) One more word on the article posted: Yes, indeed, mathematical and from an engineering point of view, this makes the 16 bit win over any other input device, even the famous 12-bit-BU0836. So the statements made are most surely correct. However, IMHO this equation misses a really vital point: While the Joystick maybe polled at a rate of 1000 Hz and a 'lag' of 1ms, you probably run the game on a framerate of 60-100 fps on a monitor with 60 Hz. If you run the game a flatscreen TV its probably less. That means even the flumsy Fighterstick with it's lousy 8bit hardware and windows 125 Hz standard polling rate is checked TWICE before you can even see the result being rendered. Not even considering input lag from your monitor... So these loitering CPU-cycles for the next input as stated in the article? You do that at least 10 times as long to actually render a single frame. Well, in the end it's just up to personal preference. I just want to point out, that though the Warthog feels a lot better, it doesn't mean it is in general a better stick. That is rather a question of immerson than that of largely better hardware. Let's face it: There is no such thing as a perfect HOTAS on the market. So if somebody points out something is obsolete, it's most likely because they want to sell you something even more expensive to replace it.

Yeah, I know. But honestly? I prefer 256 rez-points I can actuate extremely precise over the Warthogs top-notch hall sensors with mechanics you need to polish and grease up to actually make use of it. And really, even if you get a warthog with expensive spring-mods and extensions, the stick still moves only 2/3 the way CH Fighterstick does in each direction. So your 16 bit are still stacked over almost half the length the 256 bit of the Ch Fighterstick are stretched. So putting all together and having the luck to have both testet in parallel, my opinion still stands.

You should at least consider the CH Fighterstick. It outlived 2 Warthog HOTAS and is still rocksolid. In fact, my original Fighterstick was replaced after 15 years of service only because I didn't find a good solution for it's gameport-plug... It's got tons of buttons and even a built-in z-axis you can use for throttle. Yes, I hear the critics: "But it's made of plastic" Yes it is, but lets be honest: The Warthog feels better because all surfaces your handle are made of metal, but the vital parts are all plastic, too. The CH Fighterstick also got 2 gimbals, so each axis has its own centering (which comes in pretty handy especially for WW2-planes) and the springs for that can easily be replaced or adjusted to your needs (again extremely useful for WW2-dogfights). The programming surface is.... simple (to find a better word than Windows 95-style :music_whistling:), but extremly powerful.

Some people shrink, when you take look at them through a magnifying glass.

Pilots don't pay 300 $ for their stick. And they use it in a much different manner. IMHO if paint wears off from simple usage, that's not a sign of quality nor realism.

Had this problem, too, unless I found a good post in the bug-section. Apparently with the previous patch the soundsystem switched to surround-output if a surround-system was detected, disregarding what speakers where connected or what the systems settings were. So in effect, if you are use a stereo-device on a system with surround-renderer, you only hear the front-speakers. Thats why engines on the A10 and most other jets seems extremely silent in the cockpit (engines behind you) and comparably loud from the outside (aircraft in front of you). The bug is simply most obvious in the A10, but after the fix I found the difference in the other jets as well. Reconnecting audio-device was one hint. In my case, I had to disable HDMI-Soundsystems as well.

Thanks mate! That did the trick! Good workaround. Hopefully the bug is fixed, soon.

IIRC it was mentioned back in the days of BlackShark, that the 2 seater-cockpit posed the most unresolved issues. Not only multiplayer with shared controls an as smooth as possible network-sync, but also the AI having to interact with the pilot in case of singleplayer flights. If that put a hold on the process, part of it seems to be accomplished by the L39. I sure hope we will see more helos in the future. Apache, Kiowa, Hind, Hokum :cheer3nc:

Now, that's even worse :-( There is no chance to keep your target focused in a dogfight.

I don't think it will be like: look at the button and it's centered. That works fine as long as you have your buttons onscreen. If not, you have to increase your factor eye movement to your field of view. So you may check six by looking at the far left edge of your screen. But then you can only fix your target with your peripheral sight, because as soon as you look at it, your field of view changes as well. Even in this video the tester had to move all important information into the center of his screen. Looking forward to some hands-on-reviews for flightsims.

Wenn schon: :D

That is just the installer. ;)

Delivery Insurance. Pretty common, indeed.

You specs don't state any soundcard at all. Which one are you using? As long as you are using the onboard soundcard, neither cables nor speakes will make a large difference. That's the pitty fate of sound. Everybody know how to read FramesPerSecond and nobody would play DCS or any AAA-Title with onboard-graphics. But with sound, most players use onboard-chip even with surround-sound and claim there is no difference in quality... :music_whistling:

Probably the same problem as described in this thread. :( http://forums.eagle.ru/showthread.php?t=152231

Tried to update driver and narrow down the cause. To no effect. Works perfect in 1.2 with all settings and drivers. No joy in 1.5 and 2.0 - literally...

1.5.2.48162 same result. Input from all 3 X-Keys-devices are not recognized. 1 in software, 2 in hardware-mode. I can even set keys to being pressed as long as I hold the key. DCS doesn't recognize the input. :( They work perfectly in other games.

Bug still present.

Same problem here. X-Keys-Keyboards are no longer recognized. Even if I artificially slow them down. Keyboard input of the same commands still works. CH gear still works, too, but sometimes DCS doesn't respond as it did. :(

Sure wish I had your monetary resources at hand. :glare:

Kommt auch ein wenig auf den Setup oder (Cockpit) an. Der Schubhebel vom Warthog ist sehr nahe am Original und eigentlich nur bequem zu nutzen, wenn er irgendwo Richtung Sitzhöhe steht. Außerdem sei an dieser Stelle nochmal gesagt, dass auch der vielgelobte Warthog nicht ohne Probleme daherkommt. Aus Metall sind eben auch für 300 Euro nur die Teile, die man sieht und berührt. Die eigentliche Mechanik ist bei Throttle und Stick aus Plastik und damit genau so anfällig gegen überstehende Grate und Verschleiß, wie die Konkurrenz. Auch der Ministick am Throttle ist ein Witz. Als Seitenruder-Ersatz wie beim CH-Throttle wird man den nicht nutzen können. Zur Info: Das sind keine Vorurteile. Ich besitze sowohl ein CH-Setup (Fighterstick + Pro Throttle), als auch einen Warthog. Ganz ehrlich: Nach anfänglicher Euphorie steht mein Warthog eigentlich nur noch im Regal.

In the CH ControlManager you can assign a single axis on a single controller to up to 16 virtual devices. This assignment can be toggled via CMScripting. So pushing one button would switch the throttle to control only the left or right engine. When deactivated it controls both again. I'm pretty sure I've seen something like that a while ago on CH Hangar. Didn't test it, though. I've implemented a keyboard-solution, though. Much simpler and more handy in an emergency situation. Question remains, how DCS handles controller switching. I've had DCS stop recognizing my HOTAS, when switching profiles.

The FPS are related to the viewscreen only. If you fire a Vikhr and keep the Vikhr-Screen on, the FPS drop the further the missile goes. If you switch the screen off / reset targeting while inflight, the FPS instantly are back to normal. Keeping fingers crossed for a quick fix.

I must say, I wish I had your confidence. Just because some piece of software will be released later doesn't mean its bugfree. There aren't even all vital features implemented, yet...

Fighter Pilot on a CPC. That was back in 1983...