nemises

hrm...not sure sorry mate, but I'd say the quikest way to resolve would be to un/re-install the app... doesn't take long

yep...though TBH, I think the (comparatively) low-tech solutions in the KA50 are what makes it 10X more interesting ... go the steam guages!

If I had a quadrant , I'd assign the throttle axis also....its just cool. I do not know how to tell though if the throttle is at "auto" setting or not though..I assume there is a deadzone or detent on the real throttle levers?

Hi Ed, The Throttle controls the RPM of the engine, and the collective contrls the Pitch of the Rotor blades. Technically both can affect the amount of lift generated by the blades, but only the Collective is actually meant to do this. The Throttle is designed to operate in an "automatic" mode, where it will govern fuel flow to keep the engine RPM fixed between it's lower and upper operational values without any pilot intervention. It is important not to use throttle as a contrl mechanism for lift , as the rotor RPM also runs the generators that supply AC power, as well as charge the batterries for DC power...if rotor RPM drops below a threshold (70%) then AC power can no longer be generated, and many of the electrical systems will stop working. So, long story short, do NOT map the throttle axis, only use the "Pg Up" and "Pg Dn" keys to control the throttles position. Using these keys, the throttle will move to 4 differnt pre-defined positions 1) Idle (this is where it will start on the ground and for engine start) 2) Low (this would be used for on ground testing) 3) Automatic (This is where teh throttle should remain after startup at ALL times unless...) 4) Emergency (This setting increases the RPM to it's higher limit incase one of the engines is in operable...thus the engine that is left will create more tourque at a higher RPM) So, after system startup, you would press "Page Up" twice, the RPM governors will then keep the engine spinning at it's optimal RPM, and you will use Collective (ie. rotor blade pitch) to increase or decrease the amount of lift that the blades have. As for your second question, The Altitude Hold autopliot has two modes: 1) Barometric (This uses the Barometric / sea level altimeter) 2) Radar (This uses the Ground distance radar) Using the Barometric altitude hols will keep you at the same altitude in relation to sea level regardless of hills, valleys, dips etc.. Using Radar will (assuming you are less than 300 Mtrs) keep you at a fixed altitude as relates to the Ground, which means it will automatically climb and descend (by increasing / decreasing colletive!) to keep your relative altitude the same to the ground. The switch to change between Barometric and Radr is on the Right hand panel near the Datalink ID numbers

Theres definately a few other Aussies / Kiwi's that post around here

have not seen this!

ah, thanks for the PT, sorry I didn't search up your post in the first place!

Hi Folks, Had to run up vmware workstation on my gaming rig for some testing the other day, and as part of VMware's segregating virtual networks, it installs a couple of extra (virtual) NIC's.. ..Problem is, this seems to trigger starforce's hardware changes and has made my Black Shark de-activated..? Surely adding two non physical devices should not be enough to trip the "significant hardware change" ... infact, adding two physcial NIC's shouldn't be enough either! Am wondering if there is something specific about the VMWare Virtual Hardware, or if, genuinely adding two NIC's to a system is enough to trigger an activation issue with starforce? Have removed the VMNic's for now to be able to play, but of course, this means I cannot access my virtual networks for the testing I was doing ... I can allways add and remove as required, but wanted to see if anyone else has had the same prob. Cheers, Nem

^^ excellent advice Typhon ... THe KA50 is the only attack heli in the world that is Single Seated, and as a result, the pilot NEEDS to use the tools he has (such as route AP mode) to allow him a chance at having battlefield SA instead of beeing totally focus'd on keeping the bird in the air. I think too many of us fly manual, as it fels a bit like "cheating" to use Route mode, whereas , in reality, it may mean the difference between life and death in a hostile environment.

I actually find it a bit annoying in IL2 (for example) to have the external view move with my trackir...means if I want to see a specific angle, I often need to twist my neck in some weird contortion.. I prefer the keys/mouse as in BS ..just my opinion though, I don't mean to imply that you're guys need isn't just as valid. I'd be surprised if there wasnt a config file that could be tweaked to define what device can move the external views ?

Looks Awesome mate, keep it up!. To pivot around in F2 view, either move the mouse! / zoom with wheel, or use the Keypad number keys (2,4,8,6 , * and / to zoom in and out)

oh ya, thats what I meant, the film, not the ingame

at 35 seconds, the film is sped up about 2 X IMHO

no FFB is not needed.. (though it sure would be nice..sigh) Make sure you press "ctral-enter" to bring up the controls guide...this will show you where the controls are trimmed to...make sure you havent trimmed in some rudder. Alternatively, it could be wind cocking. Alternate to the alternative, you could have your heading hold set to another heading, and the AP could be trying to resolve that.

yes, they are high velocity solid objects, and they will deflect off acute angle objects and objects with more mass. The HE rounds explode on contact.

the gun will still track to wherever you aim the shkval (within the guns limits) assuming you also still have the ranging laser in standby.

mumble is a great voip solution, unbelievably low latency! I play Project Reality (a great BF2 mod), and a lot of servers use Mumble...it can position itself in 3d space!...so the voice actually originates from the players location, and fades out over distance.... not sure if only PR supports this, though I expect thats the case We use BF2 built in voice comms for radio cahtter, and mumble for "local" voice chatter.. You can even hear the enemy talking if you are close enough, and let me tell you the 3d positioning is UNCANNY ... you don't realise how much SA it adds beeing able to hear where the voice is coming from positionally.. And as I said, the latency is really amazing...transmits the microsecond you press the PTT button, not the 100ms or so delay TS puts in. /fanboy

yeah, for sure! There are two completely seperate installers... One for X52 drivers (which will find and install all teh "magic" bus devices), and one for the SST software. Just don't install SST ... should have no problems... Windows will automagically see all buttons and Axis (including teh microstick as a mouse ... you can use it as a mouse in windows if you like). The SST software is (unfortunately) a bit on the buggy side, and used to causeme all sorts of issues too...latest stuff seems pretty good tho (need it for Lomac and IL2) .. but yeah, as I've said above, I mapped everything in BS itself (apart from my TS PTT key), adn no issues at all.

yeah, I need to move my trim button, as its currently on a thumb button (x52 button A) ... this is fine for normal flight ops, but kinda sucks when I need to launch a Missle/rocket with the same thumb (thumb fire button) .... pinkie switch would be ideal, but I've allready brain-trained so many useful functions using it as a shift button.. :(:(

so, take a deep breath, and hop down off the horse for a second. There has been literally dozens of threads , and probably over a hundred posts on this exact topic over the last 12 months..and the result? Black Shark performance is NOT improved by setting muticore affinity in XP However, it can have a considerable increase in performance on Vista and Win7 go test it yourself if you like.

yeah, dunno , I definately find the press-and-hold much easier, though I believe the "fight AP and then trim" method is he technically correct way ?

ok..thats cool

I must admit, I use trim reset when I land as a shortcut to trimming properly for the ground... ..but I feel ever so naughty when I do!

Hi Mate, That is an accurate appraisel of how it works. The trimmer button doubles as a "new heading" Input button , when released, for the Heading hold AP channel and also sets the goal pitch/speed when in route mode. While the button is pressed, all input from AP is disabled. The Collective brake has a similar function inputting goal altitude for the Altitude hold channel.

Hmm... I use X52 , Win32 XP and SST no probs I actually map 99% of stuff direct in BS..only SST I use is to put a TS PTT button on my rudder pedal toe brake, lol.. I use the X52 mouse in BS all the time...it just thinks it's a mouse...nothing to do with SST (though you will need the X52 drivers installed, which will also install "saitek magic mouse" , and "saitek magic keyboard" devices). Bit confused as to why BS would not recognise all X52 axis...it does on mine? Sounds like maybe you need to ge th latest X52 drivers...then check in contrl panel, controllers to see if all axis and buttons are seen in windows....if windows (direct input) can see them, then BS can see them too...