Cezar11

I went into the axis curve in BS itself and adjusted it quite a bit... now it's much more predictable with my cougar.

I just added another ati 4850 and enabled xfire... I was able to crank up the detail to the max and my fps is now smooth as glasss... no stuttering at all.. I would recommend it...

No need for a track.... just turn off the weapons system power ( or don't turn it on at all....switch beside the eject seat power ) you'll see that weapons systems are totally unaffected... all aspects of ground moving target mode, a-a aspect mode and auto-turn-on-target mode work as expected. you just don't get the lights on the push buttons... I can add a track if you are really having a hard time understanding what i'm saying... but I think you'll be able to reproduce this behavior with little problems...

I had the same issue..... found out mine was heat... I put a small desk fan blowing into my open case.... not one crash since then... Don't underestimate the effect of too much heat...

I'm not sure if this is a 1.0.1 patch or stock game problem. The Weapons System power switch doesn't seem to do anything expect make the activation lights ineffective on the auto-turn-on-target, ground moving target push button grouping. several people have confirmed this. you can turn off the system power ( or not turn it on at all ) and the functionality of all 4 buttons is retained, you just never know if the button is on or off... This doesn't stop the game, but probably is not the way the thing actually works in real life.... just thought they'd like to know.....

I appreciate the feedback.. but I have no idea what a CYO is... my panel is in english ( I don't know what a catapult switch is either for that matter.. i'm assuming you mean ejection, since it's very close in meaning..)

I have checked my startup against several checklists. I was more wondering from any of the ED or more experienced guys if there are any omitted switches or settings that would cause these issues.. I will try the auto-start sequence.. Edit.. I tried to auto-start... all items worked... so what am I missing? I hear a bunch of clicking.. but can't see what's being switched on. it's very strange to me that the above items still work, but just don't light up when I start up manually... Edit MkII.. Mystery solved.... my stupidity.... point 1.. target points not showing up... Nav Datalink power not turned on. point 2.. turn on target grouping lights not coming on... Weapons system power not turned on.. next to ejection seat power.. I think this is a bug.. because the auto turn on target still works without power....unless the weapons system power switch just powers the push button lights.... which is hard to believe....

Hey all.. really strange thing here.... If I start the chopper manually, target points still work ( auto pilot and SHKVAL still show them as normal. ), but they won't show up in the ABRIS. Also, the auto turn on target section ( the 4 buttons over on the left ) don't light up.. they still work.. but won't light. Now, if the chopper is already running when the mission starts, both of these items work as expected. Am I not turning something on when I start the chopper up? Any ideas?

I had that problem... couldn't figure it out... then I stuck a small desk fan blowing into my opened case..... No more crashes.... must have been heat...

not sure where it is.. i'm at work.. don't have the options.lua in front of me.. but it's almost all the way down at the bottom... where the view and resolution settings are.... there's a line that says "width=xxxx" xxxx is your resolution.... so if your monitor is 1024x768 then it should say width=1024 just change it to width=3120

I had the same issue.... what it turned out to be is that the "phantom" monitor is no longer there... so the center screen does not start at x=1280 ( for a 1280x1024 res ).. but instead at x=0.. then you base your right screen off of that... i.e. abris is x=1280 so to use your lua file.. Description = '2MonitorTest' Viewports = { Center = { x = 0; y = 0; width = 1680; height = 1050; viewDx = 0; viewDy = 0; aspect = 16/10; } } Shkval = { x = 1440; y = 400; width = 720; height = 450; } ABRIS = { x = 2160; y = 0; width = 720; height = 900; } so your full width in the options.lua is now 3120.... ( i.e. 0 + 1680 + 720 + 720 ) and you have to go back and actually edit your options.lua file again.. the patch resets it.....

ever seen this video of an apache taking off a blade with a tree? I don't think you could make it back to base in real life with that kind of vibration.

the pitch, roll and heading hold AP buttons.. I normally have the alt hold on as well.. but you don't have to... I turn it off when approaching for landing or taking off...

I too had trouble with the concept of when to trim, FD on, off, or toggled. I read about holding the trim button when moving the stick, but that just seemed like too much work. I have to say tho, that in the past 3 missions I've forced myself to hold the trim button down and keeping the FD off. 3 AP buttons on, and I've never flown easier, been able to concentrate on baddies, kept a great handle on my yaw/heading and altitude... ever! To all those that are still unsure about what to do.. map a button on your stick to the trim and hold it when you turn, move, stop, speed up.... it's really amazing. you'll never go back to FD in normal flight mode again..( i'll admit.. I turn the FD on when I'm caught with my pants down or I need to press other buttons while moving fast ) I think the common confusion here is the a normal trim recenters the controls wherever they happen to be when you press it. It seems the ka-50 will keep whatever attitude/speed/height the ship happens to be in when you let go of the trim button. ( sort of a cruise control ). My usual flying style is to take off, hover at 10 or so, hold the trim button, yaw to a heading, let go of the trim, press trim again and push forward until I get to my desired speed, then let go of the trim. The ship will stay at that speed/height ( providing alt hold is on ). It even acts as sort of a nap of the earth system ( not nearly as precise as an aircraft NOE system ) The helo will rise and fall as best it can to maintain whatever height you were at when last trimmed. ( you may have to augment with collective as needed..) Then when you want to stop, simply press trim in, bottom collective some, pull back until you are at 10-12 degress and let go trim. The helo will stay at that attitude and come to a stop. I never have to step on the pedals to counter yaw as I slow, heading always stays more or less at the same point. Try it.. you'll like it..

Never fear.. your friendly babelfish is here!! http://babelfish.yahoo.com/translate_url?doit=done&tt=url&intl=1&fr=bf-home&trurl=http%3A%2F%2Fwww.digitalcombatsimulator.com%2Findex.php%3Fend_pos%3D2320%26scr%3Ddefault%26lang%3Dru&lp=ru_en&btnTrUrl=Translate Poof!! English write up :)

I do absolutely love it.... Like many have said.. the comm menu alone is worth the price of admission. Being able to say "vehicle, wing 2, send", then "2 attack datalink" is priceless I've done a few training sessions with it.. but wanted to get into flying :)... i'll train more as I go. I use that profile as well, but am using the S4 switch to turn on/off the flight director I just leave my VAC running..

I run 2 monitors ( cockpit on one monitor, shkval and abris on the other ). works fine. and I run Vista with a single ATI 4850 card... yeah.. it runs in windowed mode.. but you can't tell... it is full-screen ( you can't see any part of the desktop )... the hard part is getting the lua file right....

I don't know what version of BS you have.. but I tried your xml file and it was all wrong... on my version ( US ) the radio key is "\".. you had it as "u", although all of the F keys that followed were right on.. Also, most of the commands you had as 2 different inputs. Such as Lctrl-i, you had broken out as command 1 - Lctrl then command 2 - i, it only works as a single command ( qualifier key Lctrl and i ).... not sure if it's the way the xml file got imported or what.. but it did give me a huge head start and I thank you for your work. I used it last night and wow.. what a difference. I mainly use it for radio comm.. although I did use it to tag and send datalink targets. Makes things so much easier. I also assigned a trim function (t) so I can just say trim ( although i used to phrase 'stick'.. kept getting trim and send confused ).. The gear macro is handy too.. that handle is hard to hit with a mouse when you are just taking off or trying to set up for a landing....

Hey Urze... I really appreciate your effort and time... In no way, did I mean any offense, I guess I really didn't think about many inane requests like mine you must get per day... I apologize. I wasn't thinking of anything anywhere near 31 cm.... just something around 20 cm with a nice radius in the middle where the chair edge would go. The grip would still be exactly above the cougar base, so balance wouldn't be an issue. I would gladly buy of one your extensions, let me ask you.. do the fittings come off? so i could play around with building my own middle part? On another thought, have you ever taken the handle off of the cougar throttle? I was thinking that if I took off the grip part of the handle and made a right angle plate. I could fit the grip of the throttle back vertically instead of horizontally on the throttle pivot point... then mount the throttle box so it acts like more of a collective where your knuckles are pointed out to the side instead of pointed strait ahead. Wondering how much extra wire there is between the handle and the throttle box..... sorry for rambling :)

Urze is the guy at left-side... no ones heard from him in a few weeks.... I did leave a note in thread that he started about him possibly making a curved extension.. but no response. So I just thought i'd check into doing myself...

does anyone know where to get ( or even what to ask for ) to get the Cougar grip connector threaded parts? I'm interested in making my own extension.. ( not that Urze's aren't just brilliant..) but I want mine to have a bend in the middle, more akin to a real helo cyclic so it sits more in my lap. With the base under my seat I know the 5 pin connector between the grip and base isn't that hard to obtain. But I have no idea about the nut that secures the grip to the base.....

Most of the newer motherboards still supply power to USB and network ports even with the computer "off"... the computer can be triggered to come "on" through usb or network commands. If you cut the power to the power supply ( either through a power strip or unplugging it ), you won't have the problem ( assuming it's a problem in the first place )

Was wondering.... what's the mechanical connection between the upper and lower swashplates of a helo? since the lower one doesn't move and the upper is rotating at the speed of the rotors, and given the force that's needed to change the blade chord angle in the airstream, you'd need a pretty sophisticated, durable, and low friction type of connection. My first thought was a very high strength ball-bearing joining, but wasn't sure that would be durable enough. Any mechanics want to provide details?

Was wondering if any real helo jockeys out there could answer this... in a real helo... does the collective stay put at any point on it's travel or does it always want to bottom out? I know there are collective brakes on some, but was wondering if the brakes are more of a "won't let it move" kind of brake or if their sole purpose was to keep it where you want because without the brake on, it would bottom out on its own? I would think that since you have to take your hands off the collective during flight to flip switches and other stuff, you wouldn't want it moving on it's own..

Hey Urze.. I have a cougar and while I love the idea of an extension for the handle.. I was wondering if you could make something a little more in keeping with a traditional helicopter cyclic....maybe not quite this bendy.. http://en.wikipedia.org/wiki/Cyclic_pitch but you get the idea... I'm wanting to put my cougar under my seat ( or close to under ) but have the cyclic more "in my lap".... Thoughts? BTW.. if it's not feasible for you to make one... can you tell me where you got the locking nut and screw assembly for the base of the grip and I can give it a shot on making one myself....