PlainSight

Pulling all the way, because when you see collective lever rise when you pull the throttle, it's just more natural and logical thing. If you push, reverse the command and give it a try. To me, it's just more natural that way.

It's true for Vista. You don't need the "phantomMonitorFix", if you were using one, or setting one. Also, the affinity sets itself, ne need to Alt-Tab to task manager and setting more cores. As for the multi monitors, it's like programming. Once you know, how logic works, it becomes easer to set or correct things. And once they're set, you're done. You don't have to set everything up everytime you run the game, only once. It certany helps to have some programming skills, logic and patience, when dealing with this. I set my aspect ratio to 16:9 (main monitor), even though i'm running the 3200*1080 res. So just try both and you'll instantly see which one seems right.

You're late, i'm using that dll, since i found it on , one week ago :) Anyhoo, haedtracking is a must here and i'm glad that freetrack is still working.

Leave that "Virtual store" (lol) folder alone, you set things up ONLY in your instalation folder, that's it.

The "weapons system mode selector" only rotates to right, even when go-to-left. command is pressed. I tried with joystick and default keyboard mappings.

I was just in my deep multiplayer session and my sister comes bugging me and, you know, i'm like "yeah, yeah, whatever, i'm trying to hit some tanks here". The kicker is, that's what mom told me later, she's pregnant(that makes me an uncle, yay) and she's getting married in US! I was like:shocking: second later :doh:, and i instantly thought of you guys. Good thing she's not my girlfriend, what would be the consequences of that, i can't imagine :lol:.

Cockpit pics, please

you must change:["width"] = 1680 - to whatever higher resolution you had and ["resolution"] = "1680x1050"- with fixed width

yeah, you have to reset the resolution in options.lua, to the one you had for more monitors. Patch resets all graphical settings.

What about setting up yet another display, last in row, just for displaying radio comms. That way, comms don't appear on other monitors, like abris of shkval. Just extend the total width for some 400 pixels.

Yes, that fix is essential. Try to run ruprecht's version, with added height it's better for abris, but less frame-rate friendly. If you'll run abris screen with 900 width, try set the heigth 1170, not 1440. You end up with 5540*1170 resolution. Some middle ground there. But if you set abris to 1440*900, the image will be streched vertically. You have to choose between full screen image and correct aspect ratio. With that many monitors it's impossible for us to post 100% accurate solutions, you just have to do a lot of experimenting. There are a lot of combinations. One more thing. The communications menu will appear on abris display. The solution would be setting two secondary displays first, then three main displays. The other is set up another display, just for showing comms.

Is it me, or has no one mentioned camouflage paint?

It doesn't matter where you put it, just unpause the script when you run BS. If you're not running PMF, you also won't be able to see those two windows. First, try running the fix and see what happens.

I searched for more info, and it's very exciting. C variant has upgraded targeting pods, cockpit and other systems and this enables the A10 to deliver smart weapons. JDAM, woohoo! Watching in your MFD how the pod is beaming the target until it goes boom, priceless! It also features a datalink system, just like BS.

I hope it comes loaded with an active radar, not just RWR. Now i gotta use labels, i just can't find anything by staring out, until it's too late.

Not a problem: Viewports = { Center = { x = 1680; y = 0; width = 1680; height = 1050; viewDx = 0; viewDy = 0; aspect = 1.6; } } ABRIS = { x = 0; y = 0; width = 807; height = 1050; } Shkval = { x = 807; y = 0; width = 873; height = 646; } Don't forget to set the 3360 width in options.lua and use a MultiMonitorFix

Use the "axis tune" option and decrease sarutation.

AToT will work everytime. Just uncage shkval and slew it around. Helo must follow your moves everytime. You don't even have to flip master arm or laser standby. Timm, try the default cold startup, turn on shkval and lift off. Then press AToT and slew it around. It must work.

You set your view in the axis submenu of controls. Cant's miss it, it's the only greened line, right at the top. There, you set horizontal and vertical slews.

Why would you want F14, when there are only (super)hornets flying around. with F18, you get ALL F14 stuff plus AG missions, CAS and an ultra complex cockpit with three MFD's and a myriad of weapons, smart bombs, dumb bombs, missles,... All packed in DCS level of fidelity. Njami! F18 gets my voice any time. Or did i watch too much of Wings of Gold?

I don't know if this is a bug, but here's the problem. I map my keys with AutoHotKey. There, i map a certain joystick button to send out certain keyboard key. For example, button #12 is "zoom in slow". And here's the problem. If i map whatever key to zoom, it doesn't work, but in windows, it sends correct keyboard key (* by default). I also tried F4 key. If it's used for looking back it works on keyboard and on joystick, but for zoom, it works only on keyboard. It's same with abris. "Abris push" works with joystick mappings and keyboard, of course, but "up" and "down" commands don't. Again, only by pressing same keys on the keyboard works. So the problem lies in some commands. So far i found "zoom in slow", "zoom out slow" and abris up and down (7, 8 - default keys). But they all work, when pressing same key on the keyboard. Some other commands work without problem, for example "ground moving target", "abris push", "air target". Are there any differences between these two types of commands that are causing problems? Well, the problem was that those keys marked with "pressed" instead of "down" in Config\Input\Aircrafts\ka-50\keyboard\keyboard.lua need some sleep time between press and release. All cool now! Send {8 down} Sleep 5 Send {8 up} instead of just Send {8}

That shouldn't be a problem. You can have different resolutions on all monitors. So, if your three main monitors are 1280x1024, you keep your height at 1024 in options.lua. For the width, you just keep summing monitors together. Don't forget to use the MultiMonitorFix. Viewports = { Left = { x = 0; y = 0; width = 1280; height = 1024; viewDx = -1; viewDy = 0; aspect = 4/3; }, Center = { x = 1280; y = 0; width = 1280; height = 1024; viewDx = 0; viewDy = 0; aspect = 4/3; }, Right = { x = 2560; y = 0; width = 1280; height = 1024; viewDx = 1; viewDy = 0; aspect = 4/3; } Shkval = { x = 3840; y = 0; width = 800; height = 600; } ABRIS = { x = 4640; y = 0; width = 787; //the perfect aspect ratio for ABRIS is 1.3 height = 1024; } } So in options.lua you would set 5427*1024 The only problem is smaller ABRIS image. If you add extra height, image will extend below main monitors. That's how i would try to set the whole thing. One more thing. Does anybody know how to move the communication menu to the left? It now appears on the right monitor instead on main and it's annoying.

I got the boxed english one. I just hope YOU really get that money and not some greedy middleman.

I have mounted my wireless joypad next to the throttle unit and arranged weapon commands there. This setup gives me 18 more buttons and it's very useful in every sim. HOTAS is a must.

I'm using FreeTrack, with one LED and joypad's stick for zoom. I find that setup most simplified, but still able to look around