Yskonyn

I have been using an X-52 (non pro) for over 3 years now and haven't had any issues with it so far. It a decent product with loads of programming options. I'd buy another one without blinking if this one breaks.

:P Why does this grown-up discussion has to boil down to nastyness with too much information?? :) If we're in that alley already allow me to drop in a thing to consider; CyBerkut, do you have any clue what your forum name means in the dutch language? Every time I come across you on these boards it cracks me up! :D Drop me a PM if you want to know. But be warned, your perception might change forever! ;) For the record; I am not trying to be offensive here, just some harmless fun.

Great post! This deserves a bump! Did anyone find a way to use SideWindow with Vista? BTW Urze, you're PM box is full. ;)

Yeah but I thought the problem was after the FD switched to OFF the autohover was still annunciated on the panel, but the Shark does not autohover anymore?

+1 ;)

You do not need 3Ghz to play it smoothly and to play it on both cores you do not need Vista 64-bit or Windows 7. Please, if you start telling people stuff be sure to give the facts... This guy is reluctant to go at it as it is and now you're telling him stuff that's total bull and might put him off because he thinks performance will suffer. First of all, you can just as easily change the affinity to both cores in Vista 32-bit as you can in 64-bit. And to make it even better there's a little tool you can download off these boards called DCSMAX (thanks Skypat!) which will do it automatically for you when you use that to start up DCS! Just like Feuerfalke said this will increase your framerate quite a bit. Secondly, you do not need at least 3Ghz at all. I am running on a 2.66Ghz Quad Core system and can fly around pretty smoothly. Changing the affinity from 2 to 4 cores doesn't make much difference in performance. Lastly, be sure to keep Water detail away from the HIGH setting as it will only maginally improve detail, but eat massive amounts of performance. Cockpit Mirrors are something I have disabled as well, because I hardly ever use them and they are a performance hog as well. DCS is quite stable and a very well crafted product right from v1.0.0 so if you're really longing for a full detail helo sim for Aces like yourself, come and join the party! :D

Yes I agree, but then the system should extinguish the autohover light, because that would give the false assumption to the pilot that AH is still engaged. If you talk about safety this would definately be a hazard.

Yes but if the Autohover light remains ON, shouldn't we expect the Shark to default back to its Autohover state, regardless of what we did? Is it correct to assume that the augmenting systems work only from the starting position out of a trimmed state? E.g. once you override the auto hover with cyclic/yaw input the system remains engaged although it looses it reference and so its up to the pilot to re-initialize autohover from a trimmed state? Is that how the system is intended to work?

If you think it takes away from realism, consider this: The real KA-50 pilot resides in the cockpit where all pushbuttons, switches and controls are in reach of your fingertips. He can twist his head to look at the required intrument (which we can do with TrackIR as well) and then have his full field of vision to interpret what he sees, then he can reach to the control of the given instrument and interface with it by means of his hands. Here we are; computer KA-50 sim pilots. Our field of view is limited to the monitor we use and can be easily rotated by either TrackIR movement (simulating natural head movement quite well) or keyboard shortcuts or HAT switches on the joystick, maybe even the mouse. But it remains a very limited field of view in relation to what our eyes are able to see if we would be sitting in the real thing. The next limiting factor is resolution; our monitors present a lower resolution of -for example- the labels and instruments in the cockpit when zoomed out a little than what we would be able to see when we're actually in the real thing, further limiting the simmer to interface with the cockpit. These are just two examples of limits we have as sim pilots which real life pilots have much less. So its only natural to look for options to give you the overal overview of all the instruments that you would otherwise have in the real cockpit. IMHO Multi-monitor setup, TrackIR, Touchbuddy and VAC can really add to realism, but a note has to be made that its also quite easy to destroy realism with them as well. But that's really about HOW you use it instead of IF you use it. For example, if you're using VAC to control all the switches and buttons in the cockpit you can indeed argue about the fact that it would be beneficial to realism. If however you use VAC to control the radio commands in the sim and direct your wingmen, then I think it only adds to realism. Point is that with the limited environment we get on our computers we have much trouble getting all the sensory input to our brain in relation to what we would get in the real cockpit and so we look for ways to make up for that.

yes it is. I've seen it at Dynabyte. ;) But if you look at the webstore it actually says 'out of stock'. If you want the DVD version I'd contact them to see whats the status.

Well the bright side is that you can spend all your time on the Shark now! :P (Sorry man, did you get sacked due to the economical malaise or have you just finished school and are a fresh chicken on the market?)

I had an ATi X1950 Pro in my old computer and I got the atixxx.dll errors as well with a few games. Command and Conquer 3 was the most notoriously title crashing constantly after about an hour with those errors. At first I thought disabling Catalyst AI had solved the problem, but it didn't. The only way I kept the system from crashing was to reduce details in the game options. It would run fine that way, eventhough I exceeded recommended system specs for the game. I never really figured out what the problem was, but it seems related to stress on the card in combination with (possible) driver issues. Hence this looks quite familiar to your problem. I hope you can figure out what causes the problem.

There's Touchbuddy for touchscreens which is confirmed to work with BS, so if you can find a similar product to work on an iPhone, you're game.

http://www.gameclubcentral.com/index.php?name=ForumsPro&file=viewtopic&t=4278 Try this link.

Rep inbound! very nice share, thanks! I am stunned to see the stable control on the yaw axis. I tend to jiggle a lot in the sim and find it difficult to stay solidly pointed at a given object, for example.

Black Shark has just been released and is going to be released in the US very shortly. Do you mind ED focussing on delivering BS properly before moving on to the Hog? ;) The plans are there and a little search gives you all info that's available. Just wait patiently for what's coming. If all goes as planned we will get the A-10 which will be compatible with Black Shark.

Just make sure you don't look at the HUD to get to that 130 kts is the morale of the story about now. At least not on a windy day. :P

Yeah but if you make it a habit to abide by the HUD speed to pull of tricks you're bound to die on a bad day during a mission. :)

So much for reading my flight manual, I guess. ;) So the Shkval is the instrument to watch while doing maneuvers then as is the analog IAS indicator in the cockpit. Is there a way to alter the speed indication on the HUD, like, for example, you can do in the F-16?

True! :) But not quite the point here.

Right you are Ethereal. There's no CAS selector knob in the KA-50, but a bit of calculating can easily transform IAS into CAS. You do have IAS, don't you, or does the KA-50 correct for wind and show groundspeed in the hud? That would be weird because the only 'performance indicator' you have, while flying, is IAS or CAS. As for certification EAS is mostly used: http://en.wikipedia.org/wiki/Calibrated_airspeed As you told us you're a wikipedia nut I thought you might like this. ;)

But you would imagine that if FD disengagement results in Auto Hover disengagement as well, that the light would extinguish on the overhead panel. Maybe that's the bug then? Logically; if the light is still on like Skypat says, then you would assume the accompanying system is still engaged as well.

No problem! ;) I was just teasing you as well. I have absolutely 0 knowledge of helo's and their aerodynamic characteristics so you could fool me into anything regarding that matter. ;) I am a 'fixed winger'. In one of the overview training missions you're being told that the stub wings provide weapon hardpoints as well as additional lift. I am rather curious how much positive lift these small wings provide to add to overall maneuverability. I can imagine there's lots of turbulence interference coming from the downwash of the rotors on top of the wings harming the airflow over them from the forward speed of the helo in level flight.

Most of us have already done so for quite a while since the download became available. :) I wonder how many are divorced, sacked or have lost custody over the child by now. . . :P And apparently there's a new wave inbound!

That's why there's something called Indicated Airspeed. ;) If you convert that to Calibrated Airspeed (corrected for intrument error and position error) that speed should always be the same to pull off maneuvers because of the correction.