remon

I was thinking more in the lines of helicopter rudder losing authority as speed increases. Anyway, we'll see with the Mig 15, if it behaves the same way then we'll know that BSTs FM has problems.

Could be that the FM dll is based on the helicopter FM dll and they have left stuff in there that they shouldn't?

"'expand' is not recognized as an internal or external command, operable program or batch file." EDIT: Nevermind, it seems like you can open these files with 7zip. And thanks for the help.

A bit late on this. What I do is take the atiumd64.dl_ ( there isn't an atiumd64.dll in the rar) and put it on the DCS bin folder as said. If i leave it as a .dl_ it does nothing, if I rename it to atiumd64.dll the game crashes immidiately before the launcher loads. Do I have to do anything else? Also, no SweetFX, no ENB, and I'm running 14.8.

I believe that if they wanted money they'd choose a different profession or subject.

As I said, Downsampling (DSR in essence) isn't something that Nvidia invented. It is the earlier form of anti aliasing, not used widely since MSAA was invented. Nvidia supports it, AMD supports it, and they do so since they started making gpus. All the games I mentioned support it without compatibility problems.

Do you have an AMD card? If so, how do you do the downsample?

It's not support for drivers. Downsampling isn't something new that Nvidia made up just now. The Arma series supports it in their graphic options menu, as you can choose to render in a higher resolution than your screen, Battlefield 4 does too, the Witcher has it as ubersampling, and a few other games. Since people in the DSR thread in the PC Hardware and Related Software forum are reporting that it raises the distance you can spot planes, he's just asking if they can put an option like this in the game.

ED could add this as an in game feature, since DSR is the same thing as supersampling, downsampling or FSAA. Just add an option like in Arma 3 and Battlefield 4 to increase the rendering resolution. Also, any of you here that play Cliffs of Dover, it should resolve the antialiasing problems that game has.

Probably they copied the controls of the Ka-50 and forgot to remove the ones not used?

There are speculations that it's a 21:9 screen. Samsung patented one of them back in March. http://www.feelthree.com/2014/09/crescent-bay-using-new-219-samsung-screen/ and, the Crescent Bay has oval optics. http://imgur.com/a/kwao7#1

DCS doesn't support Crossfire. I believe it supports SLI.

Do you mean there is still heavy tearing when you turn your head around?

I think it's 1300 mph, right?

I can't believe that any modern machine or video game can have problems with AF. Did you mean AA?

The rudder is trimmed (for cruise speed at 2200-2400 rpm, I think they said) on the ground. That's what you probably see. http://forums.eagle.ru/showpost.php?p=2138446&postcount=1 "Currently in DCS the rudder is balanced for cruise at 2200-2400 rpm, though the required rudder input is small for the higher power ratings and corresponding speeds."

What do you mean?

Where did you read that?

I'm guessing that you're talking about ballistics and penetration modelling and hit boxes when you speak about internal model. Is there a quote by any dev that things don't work that way? From what I understand is up to the plane creator to make hit boxes, or cells, and link certain parts with certain effects on the plane. For example, I'd consider the P-51 not losing fuel when the tank gets hit more of a bug than anything else. About the visual aspect of the damage modelling, I'll repost here an older video by VEAO. http://www.twitch.tv/ells228/b/500255397

Go to the In Game Module Manager and see if you can download it from there.

Fixed it. Go to the \Eagle Dynamics\DCS World OpenBeta\Mods\aircrafts\TF-51D\Input\TF-51D\headtracker folder and copy the default.ini file found there. Then go to \Eagle Dynamics\DCS World OpenBeta\Mods\aircrafts\F-86\Input\F-86F\headtracker and paste the copied file, replacing the older default.ini file. Thanks to Skate for the idea.

Are you running the beta? I think only the beta clients update to 1.2.9 for now.

The only module it has problems with is the F-86, all the other planes can use it.

My headtracker (Freetrack) isn't recognised, only by F-86. Anyone having this problem?

It doesn't work like this. Put your eyes really close to your screen, or put your finger very close to your eyes, you won't be able to see anything because your eyes can't focus that close. You still need lenses. The only technology I think that would help with this, other than optics, is bionic eyes, and the most advanced things we have there are glass eyes.