DayGlow

Since the release for the Leap Motion is coming up, has anyone got the dev kit and experimented with it in dcs? I think it would work simple enough with the virtual cockpit. We stil have the pointer on screen to show where we are pointing and need some simple jestures for left and right click as well as mouse wheel up and down.

With the latest version, if I download missions, campaigns, etc where should I put them so that they show up in DCS world properly. I can't find instructions anywhere about where downloaded content is supposed to go.

Are you sure about the time? BS 1 was released in 2007 and A10C was in early 2011. My understanding was that the P-51 started as an internal project to demonstrate the flexibility of the engine and was started some time after the A10 was released.

I think they would sell them as separate aircraft. They are in it to make money. I think you have to drop something like $100+ in the kickstarter to get this perk, so in effect they are buying multiple aircraft.

Many accounts from P-47 pilots that the weight of fire from x8 .50cal hammering a tank would push it off the road and flip it onto its side.

I hope the new engine EDGE will improve the accuracy of the sim physics some. Right now the GAU-8 with its massive 30mm doesn't move the tanks at all. New physics will be needed to accurately model the ability of American pilots to flip WWII tanks with the weight of fire from the .50cal's.

That's exactly my point. I can edit my package, but every allied and opfor package is flawed resulting in huge losses. I enjoy F4/BMS, but this has always been an issue with the campaign since the beginning.

Now that would be awesome. A1? Sign me up.

If Oleg is involved we can look forward to all the trains running on schedule.

There has to be a baseline of realism for the campaign to work. The ATO in BMS still places waypoints near active airfields and well with SAM coverage. As well package timings are way off. There won't be much fun if your A-10 is constantly tasked in an AO full of multilevel intergrated air defenses. This isn't just an issue for playability of the players mission, but skews the whole campaign with horrific loses across the board. I am looking forward to see what ED comes up with, but I am wary based on what I've seen in what is heralded has the defacto DC.

Don't forget the F4 DC was in development with Micropose for 8+ years, they went bankrupt from the dev time and then the community trying to fix it for 12+ years. It's very immersive, but not realistic and very much a meat grinder.

Wingman?

The FC planes have their heritage in Lock On and Flanker products. In the Flanker series you had to switch to cannon to fire it, the joystick trigger fired both cannon and missiles. Lock On introduced western aircraft, but at the time a single keyboard profile controlled all the aircraft. The original Flaming Cliffs added western centric commands such as the pickle button and guns trigger. I believe not until DCS World intergration of FC3 did we get individual command profiles for each aircraft. So this is a really long winded explanation that the cannon toggle is a legacy holdover from the Flanker days.

When I was upgrading my 6970 from my research last year was that CF was no where as mature as sli. I ended up going with the 660ti's because they were at a stupid Boxing Day price and sli was a lot more stable and smoother than CF. I understand AMD is working on beta CF drivers that are to be released later this summer to address these issues.

Might be a crossfire issue. I'm running x2 660ti's and getting smooth performance at 5970x1080.

If you want force sensing the Saitek x-65 works out of the box with no issues. The calibration issues have been fixed with the latest drivers.

Any way to have them kill their lights is the AO? Does this effect AI detection?

Since the new 6DOF cockpits came out I decided to jump into the A-10A for some fun. I have a Saitek X65 with the mini-stick configured as real analog axis's. With axis controlling the TDC for the AGM-65 with the A-10A the vertical axis doesn't work. I checked my HOTAS and it moves the TDC in the SU-27 fine as an axis, as well as in DCS A-10C. The keyboard controls the TDC fine in the A-10A, just the vertical axis doesn't work for an analog device To make sure it wasn't my mini-stick I configured my controls so that the mini-stick controlled the aircraft and my main stick controlled the TDC and got the same results.

I does do SLI. There is an SLI profile that you can find with Nvidia Inspector for DCS Black Shark, but all DCS modules use the same .exe so it is covered. I did a quick test and the SLI visual indicator shows that my second card is working and the workload is pretty split. For the OP, it maybe an issue with quad SLI. from what I've seen on the web it's pretty flakey in many applications. When you are running a single card you're still running an SLI setup. Is there any way to limit the cards to a tri-sli setup?

Well it seems I was making the mission more complicated than it was. I was constantly getting tangled up with the SA-9 and looking for the infantry. Thank you for taking the time for this.

Sweet. Looking forward to this one.

Arma 2 uses PhysX 2.0 and Arma 3 will use PhysX 3.0.

The Zalman mic is really good http://www.amazon.com/gp/aw/d/B00029MTMQ

Just run the auto-updater. It will update all the modules you have.

Beta is still beta. Don't expect a finished product.