nemises

yep, once it starts spinngin, it take s a hell of a lot of pedal to stop it again

yeah...it doesnt haveto be zero speed really...anything under 20kph is usually ok..but the closer to TRIMMED for 0, the less the AP has to do = the less deviation you'll get... good luck!

Hi Gaz, Here are exact instructions as to how to forward the ports needed on that router: http://www.portforward.com/english/routers/port_forwarding/Netgear/DG834/Lock_On_Modern_Air_Combat.htm Once he has opened the ports correctly and has hosted a mission you should either 1) see his server show up in the Multiplayer browser (you might need to wait a few minutes..keep hitting "new search" or... 2) click "directly connect", and then put in his EXTERNAL ip address.. he can find out what his EXTERNAL IP is by going to : http://www.whatismyip.com/ Good luck!.. If you guys are still having trouble, jump on the 104th Phoenix Teamspeak server, and we'll try to help out... I should be on (much) later, but most folks there will also be able to help out. (find the teamspeak details at http://www.104thphoenix.com , sorry to all for site spam, but it's legit!)

It is possible, because of wind and trim, that you might float a little off axis... What you can do to assist the autopilot is teh following: 1) MANUALLY trim for a hover, do not do it from 12kph, do it from 0kph (or as near as you can get it 2) Activate the auto hover 3) wait a second , press the trimmer 4) wait another second press the trimmer again 5) again press the trimmer (nope, not kidding) ... This will re-set the desired hover posoition to follow along with you while the AP is trying to dampen out any movement...in this way the AP will have max contrl over pitch and roll while it is trying to hover. You should also manage your VVI with collective and hit the Collective brake (g?) to set the desired hover altitude once settled as well...this will stop the altitude hold channel from trying to regain whatever height you were at before reaching a stable hover.

Accidentally full trimming your rudders... ...trust me, it hapens a lot!...(well, lo...to me anyway)... Make sure you have your ctrl-enter screen up to be able to tell where you have trimmed rudders too

Hey Sobe, Yeah, you are right, the PVI and Abris are two allmost completely seperate systems (think of the Abris as like a GPS sat nav in your car, whilst the PVI is more like a map book and compass). When a mission creator builds a mission, and sets up waypoints for the player controlled KA50, the game automatically creates the waypoints in both the PVI and Abris systems, however the numbering can be different....Waypoints can be "named" as anything, and this will display in the Abris, however, they will allways be presented in the same way in the PVI The PVI is contrlled from the keypad on teh right hand side...if you select "nav" and then click on a number (from 1 to 6) , if there is a waypoint setup as that number, it will change the yellow heading bug in the HSI guage (left of the TV display), and also the Heading carrot ^ in your HUD...the HSI is your primary navigation device, and the PVI sets the heading bug on it....the Route autopilot mode uses the PVI/HSI to navigate NOT the Abris. To select your takeoff point, select "airfld" then "1"...and (if different) to select your landing field press "airfld" and then "2" on the PVI keypad ... once again, this will change the heading bug in the HSI / HUD and give you a range in the top left of the guage...do not forget the HSI / PVI is your PRIMARY navigation device, NOT the Abris The Abris is contrlled on it's own screen ... click on "nav" and then click "susp" to iterate between different waypoints...the main function of this is to get a secondary bearing , ETA etc... or as a backup navigation device if the PVI is damaged. The ABRIS cannot drive the KA50's autopilot, nor can it update the HUD / HSI. It may be usefull (for eg) to have the Abris giving Bearing and distance info to a navigation waypoint, but have the PVI / HSI pointing at a target point or return airfield ... potencially useful info for when you need to let other people (ie in multiplayer) where you are without changing the Autopilot destination to find out! The only place that the two systems (ABRIS and PVI800) interact as far as I know , is in the setting and display of datalink target points, which uses a 3rd system (the datalink) as a middle man. Whew, hope that makes some sort of sense...if not, keep asking

also, try the "press and hold" method where you press and hold the trimmer at the start of any manuever, and keep it held during the maneuver (say a 15 degree right bank), KEEP it held untill wings level again, then release and recenter stick/rudder.

*edit* the new method is to help those of us with centering force joysticks (ie springs!).....in watching your track, I can definately see the ocillations you are experienceing, and it sure seems to be from double transformation once releasing trim....this should not occur with a FFB joystick....if it is NOT a Force Feedback joystick, then you are doing it wrong ;) you need to recenter the stick / pedals within a micro second of releasing trim OR use the new trim method which will allow you to recenter with no time limit....you might be tripping up on actual real world habits and you are just not used to re-centering a springy joystick* /* irrelivant dribble below If you get pitch ocillations with the new trim method, then something is wrong...the new trim system specifically stops ANY input from the controllers untill they are physically centered, and this (in anyone elses setup) would mean that when control is returned, NO input is beeing sent from the joystick/rudders untill you move them off center, hence no accidental pitch/roll and no ocillations. So, I expect 1 of several possible things 1) you are not flying with the a/p stabalisers on 2) you are using the old trim method only (we "all" get ocillations with this!) 3) you are not using version 1.01a (ie. no new trim method) 4) there is something very wring with your joystick...you must check it in windows control panel, and look for input spikes in the pitch / roll axis! 5) you have more than one axis assigned to pitch / roll */

yep, great work mate, I've been shot down 3 times sofar on hte SP, lol...will haveto try the MP + treat it a bit more serious! (Also great tip about the "hold" fudge , really great idea)

the initial Payload is setup in the mission... If you want to try different weapons out, go ahead and open up the Mission editor, add in a KA50 with pilot skill "Player", then click on the Payload icon (lower right hand side of screen), and you'll see all the differnt pre-set weapon payloads you can set...pick one you like (or make a new one by right clicking on a hardpoint slot), then click the Blue "play" icon on the left hand side :) The 104th Phoenix (http://www.104thphoenix.com) have quite a few black shark players, feel free to jump on the Teamspeak server any time (found at site above), and ask away :)

I don't believe there is any mode that allows the mouse curser to be (relatively) stationary to the cockpit when moving the head.. The 3 modes are: Axis moves head, no cursor Axis moves Cursor, no head movement Axis moves both head and cursor (default)

Hi Gaz, Whoever is going to host the game will need to make sure to Port Forward TCP and UDP 10308 on your router. By setting this up, you are telling your router to allow incoming traffic on those ports (blackshark traffic) , and also to forward that traffic to the specific internal IP address of your PC. If you're not sure what this means, or what to do, come back and post the type of router you / your friend has, and we can be a bit more specific about how to do it :) ..alternatively, have a bit of a google about port forwarding / NAT.. good luck!

very true, however, you're only ever pressing it if the altitude hold mode is also on, which for me is only maybe 40% of the time?.. I see your point though ... as it's essentially automatic in the real thing etc... Don't know about scripting for button presses based on axis variance though

..or assign a button to it on your hotas....

make sure MAster arm is on...the zebra colored switch under the TV...obvious I know, but I bet you thats all it is ;) ..I know this because I did the same thing the other night "...wtf is wrong with the goddamn targeting comp?!"

pull.. ..I still want urze's collective mod

Its proper use in the sim is to set the goal altitude for the alititude hold channel. If you are in altitude hold mode, and wish to increase or decrease altitude, you should press and hold the collective brake, then ascend/descend, then release it (think of it a bit like the trimmer for altitude)..thats it's only real function in the sim...IRL of course, it is also a physical barrier to moving the collective, and would allways be held in (ie. disengaged) when moving the collective...

yes, I enjoy non combat roles / missions

new system so far...I was happy with old system, but want to give new system a go for a while to see. There are slight drawbacks to the new system (as Aero mentioned, sometimes you get control loss because of not properly returning the controllers to center), but I think, overall it helps me fly a much better profile....no bucking bronco moments anymore..

I don't think it would be "hard" , but it could be time consuming.. certainly to do a basic job (ie just add another client with matching waypoints), then not too hard or long, but to clone and redefine all of the triggers and events for either player, maybe a bit harder.. There is another post on this board where someone in the community is looking into an external program that will interface between Teamspeak and BS (via lua exports) and contrl channel connectivity based on radio freq's, which is pretty cool. For ED to encorperate voice comms in the engine would be quite a big amount of work for them, especially considering 3rd part solutions allready exist in part ... It would be nice to brdge the gap though, and at least have it automatically join you to the appropriate TS server on BS server connection...

so just consider that DCS is the product, and Blackshark is just the first addon module to it...A10 will be the second module to it ...both modules use DCS...the underlying stuff (Mission editor, multiplayer engine, rendering engine, AI, flight dynamics engine, GUI) are all DCS, irrespective of what mudule.. ...at least, that s the theory

yep, or you can allways jump onto one of the training servers and ask on teamspeak / vent

The throttle goes aup and down to 4 (?) differnet positions... Idle, Low, Auto and Emergency. Emergency would only be used if 1 of your 2 engines cut out. The most likley cause of the RPM low warning is if you pul too hard on the collective with a full load and with no forward movement. Even though helicopters can go straight up and down, it is not efficient to do it.... you should try to roll forward during your takeoff and gradually raise the collective. This way your lift is optimised. If you just yank on the collective with a full weapons and fuel load, you can definately slow the rotor speed down to "warning" levels.

Check your version of directx is the latest , and your video card drivers are up to date. Also try try turning down some graphics options to help troubleshoot. Most likely culprit is your video card (hopefully drivers and not anything physical)

I think he's trying to ask if the frequency is a value that can be exported ... if it is, and his program can use teh exported value to chege TS channels, then, cool!