Originally posted by Skuzzy
Adding a third party control program to a stick adds another layer the interrupts must traverse. Another potential source of failure. A delay. Another layer of routing data. More CPU time and so on.
It is always best to avoid using third party control managers if you can.
Doesn't the CH Control Manager only load the commands in the stick via eproms or some such then shut down so it doesn't add that extra layer you refered to?
IIRC, that is what the documentation says.
Would this 'extra layer', if it exists, be much of a problem on computers that far exceed the AH minimum requirements?
The reason I'm bugging you about this is that ever since I've started flying back in AW4W I've always tried to keep my computer in top gaming shape.
But the thought of reprograming my CH gear and loosing some of the functionality of the CH Manager has that the AH mapping doesn't support, scripts are one example, is a scenario I'd like to avoid.