-Nighthawk-

This has happened twice now, on the start of a mission I'm already to go on the runway, contacted the tower to take off and I'm just ready to go. Next thing I know I heard this huge noise and my helicopter starts shaking like crazy so I immediately turn off all engines to stabilize myself. I look up in the sky and it turns out the Wingman #2 has crashed into me not knowing I was actually on the runway. My rotor blades have been completely destroyed and half of my helicopter has been damaged. What's up with the AI and not actually knowing I was there in the first place? Seems kind of annoying when I was to take my time and not rush things within the game ;)

Yep Windows 7 takes advantage of multi-core CPU's much like Vista did over XP, should be good. Thanks for the info

Larabee with only have a chance of being successful if game developers take advantage of it, after release this will be a while. No point getting one on launch as a cheaper ATI / Nvidia will do the job much better.

Remove the Z axis from the axis commands in DCS, then apply it through profiler. That way there are no conflicts between the Saitek software and the DCS software

Thanks heaps, it removed it. I was also experiencing a random crash to desktop sometimes when the aircraft crashed, this should hopefully solve that problem. cheers

Use Saitek profiler to create a profile for the joystick. Under the "Throttle" section change the mode to "Directional Axis", you will then see to extra boxes appear being "Throttle+" and "Throttle-" In "Throttle+" add the key command "Num+" and under "Throttle-" add the key command "Num-". Save and launch your profile, now it will work fine.

Ok Ill try that thanks, I just find it stupid to have a DCS Profile thing built in yet you can't even switch modes as that requires the "Profiler" software...

Yep sometimes had it in LOMAC now I'm starting to experience it in DCS, hopefully the new patch finally removes it...

Hey, I'm currently having a problem with the X-52 profile on DCS: Black Shark. I have made my own one but every time I go into the game I get that "Saitek RULEEZ, DCS: Black Shark" profile in it, I think DCS has it's own Saitek profile however I cannot locate it to remove it. From the forums I downloaded a batch file that restarts the MFD so that I can use my own profile on it, this method is extremely frustrating however as I have to minimize the game each time, load the batch file and reload my profile. How can I remove this conflict so it works each time? thanks

I highly doubted it at first, then going to the link: "In spain April fools day is 28 of december"

DCS: Black Shark isn't big enough of a game for ATI / Nvidia to optimize drivers for, only major games like COD4, Far Cry 2 etc. get this. Not to mention there isn't really a need for it, I can run it maxed out 1680x1050 with full AA on my HD4850 / AMD 5600+ (3.0GHz) at 40FPS+. All though SLI / Crossfire is done via the drivers, a game can still be optimized to make best use of multiple cards through the engine.

Nice, I got some airshow tickets, an X-52 PRO Flight Control System and the usual etc.

The manual would be too long if they explained every single function in detail, just read the manual thoroughly then do all the training missions and that should set you up, if you are unsure of a certain function etc. just ask the forums :)

There is clear instructions after you purchase the game in large writing. You must download both setup.exe and data.cab, once they are downloaded make sure they are in the same folder then run setup.exe. Easy as pie.

It's a great game, these days I'm hard to impress with the quality of something, there is always something else to benchmark against. When I got DCS the other day I've never been so impressed with a simulator, it took my about 3 hours just to learn the startup procedure (encountering some problems with the cut-off valve etc. ;) ) instead of just pressing "I" or something similar in another game there was about 40 commands to click. So far I've learnt the basic flight systems, the navigation systems (from LOMAC) and now I've moved onto Combat which I'm about half way through. It will take months to learn but that's the whole fun of it :)

You're first suggestion was doing it "before" starting up the engines, which didn't seem to work for me. The cut-off valves had to be enabled when the engine was over 15% RPM

Yep I'm aware it's the percentage, just prefer using thousands to count it instead of percentage as I'm use to LOMAC ;)

Yep as soon as the RPM indicator hits between 1500 and 2000 RPM then quickly turn on the cut-off valve for the left engine, that will get it up to about 7000 RPM which you then turn the right engine on and also enable the cut-off valve at 2000rpm, once both are up to 7500-8000rpm then press page up twice to enable full throttle. That's how it works for me, might want to try it :)

After re-watching Matt's producer note #1 I got it working :) Turns out I was waiting too long to enable the cut off valves, seeing how he did it, it was about 3 seconds after the engine had be started up. Thanks for everyones help

Hey, I'm just loading the mission "Death Valley" (as I am unsure of any other missions where you start on the ground with nothing loaded up ;) ) I've gone through the check list many times and all are fine up to the left engines getting enough RPM to enable the cut off valves. Vortex: yes the cut off valves are not enabled as that is the next step once my engine RPM is up

Hey, rotor break is released and I've also tried increasing the throttle to allow for fuel increase, however none of these seem to work. The right engine seems to work (just guessing by the noise) its just not the left. Anything else?

Hey, I've tried the cut-off valve a few seconds after the engine has started, however it does not make a difference in getting the engine RPM higher. Anything else I should look out for? The rotor break is down (meaning its off) so I don't think that's whats stopping it, and the ANU is also on working fine. Thats the step I've got up to. thanks

Hey, I've just started learning the KA-50 with the help of the manual for startup procedures however I am stuck on a certain part. After the left engine is started it says to wait for the engine to reach around 18% RPM, however the RPM gauge is not moving. I have re-tried all the steps so the rest of the startup procedure is fine however it is just the rotors that don't seem to be moving much which I think is the RPM, they startup for about 30 seconds then stop. Any help would be greatly appreciated, thanks

Every single DCS release will be highly detailed hence why the first one was only the KA-50, it takes that much time and effort just to create a single aircraft, so yes

Just one at a time, perhaps ED will allow for purchase of additional cd keys for cheaper? If you are installing it on a separate computer you need to deactivate the current copy then reactivate it on the new computer