Slayer

I just saw a cool overview of the A10C on Future Weapons. They have the video of it up on their websie under season 3. The flight sim Mac gets to fly is amazing....is this the one that ED is working on???? http://military.discovery.com/videos/futureweapons-season-three/ You can't watch the whole episode but the clip is pretty cool.

This was a really old issue I thought was fixed in 1.01 dis you update yet? Anyways I had the same problem, you don't need to do all that other stuff. Just go into your C:\Eagle Dynamics\Ka-50\bin\stable and delete or rename the lua_direct_output.dll file. Here is the original thread if you want a detailed description http://forums.eagle.ru/showthread.php?t=34311

As I said sometimes the auto turn on target flakes out and the helicopter just wants to randomly start rotating and wont turn on target... no matter how many times you trim it. Trim reset fixes it for me when this happens. Never had rotors strike once because of it...

I use it all the time since I don't have a force feedback stick. It is best to use this when you land and rearm-start from scratch as he previous poster suggested. I also use it when the I'm hovering and the auto turn on target quits working and the helicopter just starts to randomly turn of its own accord...reset then quickly trim again and all is good.

Lighten up on the stick a bit and try to work the controls smoothly this will go a long way. If you ever fly in the mountains at high altitude you will quickly see how heavy handed flying impacts the helicopter. Any easy trick to keep engine power up is to turn off the dust/ice protection if you don't need them...They rob engine power. You can also bump up the engine throttles to emergency power and this seems to help a bit if your heavily loaded and manouvering hard. Some purists get mad about this one but who cares...it's modeled and pretty much any mission you fly will be over before the engines start to degrade..

Maybe you take damage before you get the chopper powered up and started and the game isn't showing it on the ekran because it wasn't powered up yet? Just a guess...

I thought I read that they were going to do something with Lockon...it wasn't clear if it was a patch or an expansion...

Are you running in full screen or window mode? My game does something similar and even after a fresh install I must manually go into the config file and set it to full screen because I can't see the game unless it's full screen....

Another tip with these profiles is that they don't seem to work unless you "add" the .exe In otherwords even though the profile is there you must still point it to the actual program file, most of the games I have installed are not auto detected by the default profiles. [ATTACH]30117[/ATTACH]

Another user posted this fix that worked good for me to correct the AA +AF problem. Open Nvidia control pannel: go to the option for Adjust image settings with preview and toggle it between Let the App decide and Use advance settings, make sure you hit apply. then your AA and AF will work again...do this even if you already have the use advance dettings checked. Until you do no setting for AA or AF in the DCS profile will work not even in global(for me anyways)

Good find. Seems to have fixed it for me also.

Good find +1 works great for me....others should head your advice instead of going back to older drivers.... I can confirm that this also fixes it under Vista X64 for me also. I had the "Use advanced 3D image settings already selected previously but when I checked "Let the application decide" then back to "Use advanced 3D image settings" it worked and would start using the AA and AF settings from my DCS profile. I'm also using the EVGA sli enhanced profiles too. With the premade profiles it seems it doesn't work until you "add" the game and point it to the .exe......even if its in the list already.

EVGA put out an SLI enhancement patch that specifically mentions DCS:BS I've installed that. You can change the profile in your Nvidia control panel. Thats has always worked for me.

Glad to fianlly see a full FFB HOTAS setup hit the market. Just what we need for Black Shark. Thanks for the heads up.

There already is some basic implemented functionality but all it does is send a message to your MFD. If you look in C:\Eagle Dynamics\Ka-50\bin\stable you will see a file called lua-direct_output.dll. Saitek is the only game controler I know of that uses DirectOutput(It's what sends stuff to the MFD) so maybee you could find out what they implemented in their DLL and make a C program to call on the functions of it. I have a feeling that it was just a pet project for ED and never really got implemented properly. If you make your own code you will probably have to remove or rename the ED file. As previous posters have stated you would have to get your data from LUA

With ATI you need to disable the Catalyst AI....it causes headaches for many people. Lots of posts on that topic.

I'm using this driver on Vista 64 bit but the profile doesnt show at all, it's not in the list for me. These profiles are always flaky for me. Many times it doesnt detect games I have installed. especially if I didn't install to the default path. I've tried restoring defaults and looking in the list with the "only show installed games" unchecked. BTW with a GTX 295 you do not get the option to show SLI visual indicators unlesss you install a 2nd card :/ probably an oversight on Nvidias part.....

Anyone running dual boot run any kind of benchmark on Win7 yet? I read a long winded article about how DirectX 11 was supposed to boost beformance because they were optomizing all the code for multicore/multithread...

Yep nem is right. Was gonna say the same thing but he beat me to it.

There is an axis dropdown at the very top of the list. Also make sure you are setting up the controls for the mode in which you are playing (ie game mode / realistic)

Well with the download you got to play it months before anyone who will just see it and buy it on a retail shelf. Think of it as a preorder.

So are you using the 8800 and 285 as SLI or seperate displays?

The jittering is caused by worn out or oxidized analogue potentiometers. This happens either through lack of use if its been sitting a long time or if it just becomes worn out through being used a lot. Analogue pots work with little "wiper" arms across a variable resistor. The farther it slides the higher the resistance value. I believe on the X52's everything but the main joystick X and Y axies are analogue. The main joystick pots are non contact hall sensors that don't wear out. They used the old style analogue pots on everything else that gets less use to cheapen up the product so it doesn't cost over $200.00... A quick fix from years ago before they came out with digital joystics was to spray some WD40 into the pot.

I made a custom profile and used "smooth" acceleration for all the axis, Also you might want to remap all the default keys (I use Shift+F8,Shift+F9 etc) because the default keys conflict with game keys.

If you are shot down you can't get over 50% success....