bengo

That's the basics of it. What do you need clarified further ?

No worries mate. This was just too good to let it pass. I'm sure everybody here will do his/her best to help you with your problem.z Maybe this helps. You're standing in a darkroom holding a flashlight. In front of you is a table, and over the table hangs a lamp. Switch the flashlight on and point it straight forward. You will neither see the table or the lamp, eventhough they're quite close to you. Point the flashlight down, you will see the table but not the lamp. Point it up, and you'll only see the lamp. The radar in an aircraft also projects a cone. Anything that is outside that cone is undetected, even if it is quite quite close to you. The cone is moveable, so you can point it whereever you want to look. See if that works for you.

Same here

There's a new feature in FC2 that automatically detects how much of the included PDF-manual you've read. If it sees that you've read the chapter about A-A-radar usage, it will automatically patch up the game for you, and then the radar should work as advertised.:thumbup: There is a cheat for it, if you don't want to read the manual but still have the radar work properly : go to your install-folder, and look for a file called rtfm.exe in the temp-folder. Double-click on it, and it should work. I'm just screwing with you mate. The bug you're experiencing can't be fixed by a patch unfortunately, since you are the bug. Learn how to operate the radar properly by reading the manual, searching these fine forums and asking questions here. If you can't see airborne targets 20 miles in front of you, your either pointing your radar-cone over or under the aircraft, or they are beaming you and therefore your radar can not see them.

Nice tutorial there Ghost, but I see you did not assign the TDC in your setup. The reason I'm asking is I can't seem to find a way to have the ministick on the pro-throttle behave in such a way that it is precise enough to slew the TDC over a moving vehicle and lock it. The momevent is too coarse, whatever I try (deadzone, curves....). So now I do my coarse and quick movement using the ministick, while I use Hat3 on the throttle to fine-tune. Any pointers ?

Use the in-game comms menu to change your payload while you are on the airfield/farp. Don't forget to switch your radio to "CREW" first.

Congratulations. Maybe you could post your solution, so when someone else bumps into the same problem, he can read here what causes the problem and what you did to fix it.

Solved. Problem was caused by the mission being developed on a machine where patch 1.0.2 was not applied on a clean install, but on top of a 1.0.1-install.:doh:

Well, I think I might have solved this problem, but some more testing is needed. I'll keep you posted. Here's the track showing things going wrong. client-20100611-231318.miz.trk

Thanks for the replies guys. I'll try to put up a track as soon as i can. Einstein, did you need to do anything special to make the auto-turn-tgt to work, like trim for example ? Diamond centered usually gives a slow movement forward when you release brakes/parkingbrake. In my case it started off with quite some speed and trimming backwards immediately rose the nose up. Like it's oversensitive to input. Same with collective. Compared to singleplayer I needed to input a lot of collective to see it alter altitude. And when it started to change altitude it did it violenty : it immediatly went to climbs or dives of + 10 m/s ! It did so when someone else was hosting this mission. It did so when I hosted the mission and was the only pilot in the mission. I tried one of the stock missions in singleplayer and did not have the problem. I never had this problem before in multiplayer or singleplayer.

Agreed. But with brakes pressed I should be able to trim the cyclic 1/3 forward to perform a good take-off and not roll forwar, right ?

Heading-channel was engaged. I checked. On the take-off : I had the controls-window up, and the diamond was smack in the middle of the cross, and the rudder was centered as well.

Here's the mission. Another thing I'd like to add : the helicoptre's handling felt completely different as oposed to in single player. For example : when preparing for take-off : while keeping the wheelbrakes pressed, the slightest forward press of the cyclic starts the chopper rolling forward. I immediatly tested to see if my settings weree screwed by loading a singlplayer mission, but everything was allright in there. client-20100611-231318.miz

Last night we flew a multiplayer mission that had some wind in it. We noticed that auto-turn-to-target no longer worked. Later, we removed the weather settings from the mission and auto-turn-to-target worked again. Anyone else seen this behaviour also ?

Please put hi-priority radio communications in the controls menu. Things like "AWACS-Declare", and "AWACS vector to nearest bandit" are crucial and need to be at the pilots' fingertips. In combat situations, I don't have the time to go press 3 functions keys to find out where the enemy fighters are. So please, replace (or add) the radio comms for vector to tanker and homeplate with declare and nearest bandit.

Does anyone know if IRL, the pilots can lean to the side and look past their seat and see one of their stabilizers ? That would increase the SA a lot. Since we don't have 6DOF, that kinda limits it for us. Just want to find out if the sim behaves like the real thing in that field.

Hi, I've just started getting to know the Eagle a bit better, and I've got a question I could not find an answer for on this board or the manual. When trying to keep my eye on a bandit during a dogfight, it seems to me I can't turn my head far enough plus the seat obstructs my view. The F-15's bubble canopy should give the pilot excellent viewing capabilities to keep eyes on threat. So the question is : am I doing something wrong, or is it like that in real life ? Thank you.

I bought my X-keys matrix board from this company in the UK : http://www.steadlands.com/ http://www.steadlands.com/pie/pages/xkeys.htm My x-keys matrix board is sitting in the basement gathering dust, but I'm not gonna sell it because I know the week after I sell mine, something will come up that needs it. :D

Hey RAMjb, just a tip : read up on the "autopilot"-channels. The autopilot in the KA50 is not like an autopilot in a fixed-wing aircraft. There are a lot of posts about this subject on this fine forum. And don't worry : every beginner has a hard time getting his head around the autopilot/trim-system. What I do to change heading : press and hold the trim-button, perform the heading change through co-ordinated use of cyclic and rudders, and when facing the desired heading and controls are centered, only then release the trim-button. Please also read the "Maneuvering the KA-50"-section (page 10-34 and following) from the manual. It all starts with understanding how the thing works and how you as a pilot need to use it to get it to do what you want. Like I said before : the trim-system is definately different from a fixed wing aircraft. Have fun.

Hey, thanks for chipping in Talisman. :thumbup: 1) Indeed, rotary implementation requires encoders and can not be read by X-keys. Solution for X-keys : use two pushbuttons. 2)should work Also check out : http://www.viperpit.org/smf/index.php

Hi Mano, I used to have an X-keys matrix board hooked up to 100+ switches, for Falcon. I've switched to a 19" touchscreen, because that gives me much more flexibility. I can create a layout for every aircraft I fly (Falcon, BlackShark, Flaming Cliffs...) With X-keys, I always had to use my F-16-like panel, where all the switches were located to more or less look like an F-16-pit. In addition to that, a touchscreen combined with the free Touchbuddy-program gives you a lot more then 128 possibilities. With the tab-pages you can group controls or panels on separate pages. The X-keys will work with BS, no problem. The Macroworks-driver will just send the key-press you programmed to that switch to whatever program has the focus at that moment. To the computer and the program it will look like you pressed a keyboardkey. Programming a toggle switch ; yes it is possible to have it just send one keypress. You can program it to send a certain keypress when you close the switch, and another (different) keypress when you open the switch. Rotaries : use a 4 position rotary switch and assign a keypress to each position. (so it will look like there's for separate switches connected to the X-keys) Three-way toggle switch : example left position : flares left middle position : flares both sides right position : flares right The problem here is that BS only knows one command for this function : "]-RAlt", so no matter what side you will push your switch (left or right) the same keypress will be generated. Buy a three position switch NO-NO (normal open - normal open) So when the toggle is in the middle, both contact are open. This means you will need two connections to your x-keys, one for left and one for right. In macroworks you will program the left switch that when it closes it generates the keypress. And then program it again to send the same keypress when the switch opens again. Do the same thing for the right side of the switch. The problem is that there is no way of knowing for BS which side you've pressed, so you may push the switch left while the animation in BS goes right or to the center. Furthermore, I seem to recall some issues with keys being closed accidentely on startup (left in position from previous flight) which caused strange behaviour (lock-ups, long loading times, weird keypresses) I find the touchscreen/touchbuddy-combination much more userfriendly and flexible. No drilling holes and connecting wires, just paste a switch-picture on your screen and add a macro- done. Besides, in my case, X-keys and all the switches and other stuff cost me as much as my touchscreen.

Not got any experience with the FC2.0 in A-A, but from other sims I picked up these pointers : -if available, consult with AWACS often to get steering to enemy. AWACS will tell you the distance from you, the heading from you and their altitude (low = <10000ft, medium >10000 and < 20000; high >20000) -fighter-sized aircraft will only be picked up by radar at distance smaller then 50 miles -tilt your radar up and down to scan the correct altitude where the enemy is signaled to be -when the range to the enemy is less then 10 miles, switch to one of the auto-aquire -modes. This way the radar will lock any target the flies through your scan zone automatically. BTW : the range setting does not influence the range your radar is scanning at, it only scales the display in the cockpit.

So far so good. No crazshes yet with the latest drivers, and a small increase in FPS indeed.:thumbup:

Oops, processing your latest information first. Standby.

Thanks for replying. My problem is that the soundfiles in the English Almaz folder are Russian. When I doubleclick them I hear a Russian voice. So, in the helicoptre Betty is still talking Russian too me. All the other folders were English, except Almaz. Mebbe I screwed up somewhere. Could you perhaps send me a copy of the English Almaz folder ? I see it's about 1,5 MB, so that's not too big. You would help me out big time. Na also, Danke schön und Gutenabend, nachbar. PS I've sent my e-mail address to you through pm